This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot bind port 80 to address error

Hello, hope you are well.

I am trying to publish a small web server in a perimeter network on port 80, but when switch on the virtual web server, I get the error stating:

"The TCP port '80' is already in use by the HTTP/S proxy listening port."

While this is true as the UTM has been changed from 8080 to port 80 as the proxy server port number, but why would this port be bound to an external interface IP Address.

How can I free up this port from the external side.

Thanks in advance

Dave

This thread was automatically locked due to age.

0 sachingurung over 8 years ago

EDIT

Thanks

Sachin Gurung
Team Lead | Sophos Technical Support
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 TrotterD over 8 years ago in reply to sachingurung

Hi Sachin, hope you are well.

Thanks for your reply, but I suspect you meant it for another community member topic.

Regards,

Dave
Cancel
Vote Up 0 Vote Down

Cancel
0 sachingurung over 8 years ago in reply to TrotterD

Hi,

Apologies, I meant that for a different thread.

Ideally, this should not happen, can you check if you have any other configurations which bind the interface?

Thanks

Sachin Gurung
Team Lead | Sophos Technical Support
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 TrotterD over 8 years ago in reply to sachingurung

Hi Sachin, no need to apologies.

I am pretty sure the interface is not used for anything else as the server is not live yet and I am currently in the build process. I have just assigned the IP Addresses to the external NICs and nothing has been published to them as yet. If I change my web filter proxy port from 80 back to 8080 then I can publish my web server on port 80.

So it looks like the Web Protection component it binding port 80 to the external cards even though I am only allowing internal networks access to the web protection filter.

Regards,

Dave
Cancel
Vote Up 0 Vote Down

Cancel