Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 1 subscriber
  • Views 8345 views
  • Users 0 members are here
Options
Suggested
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

The TCP port '8080' is already in use by the u2dcache->port configuration

CRServers
I want to use "Webserver Protection" on a server that has the website on port 8080 (I cannot change this).

But when I try to configure "Real" and "Virtual" webservers to use port 8080, the system come back with:
"The TCP port '8080' is already in use by the u2dcache->port configuration."

I have gone to Up2Date configuration and have changed the port there from 8080 to something else, but still, it comes back with the same message.

How can I fix this so I can use port 8080 for Webserver Protection?

Thanks,

Rodrigo


This thread was automatically locked due to age.
Parents
  • 0
    Hi Rodrigo, and welcome to the User BB!

    Try port 80 on the Virtual Server with 8080 on the Real Server.

    Any luck?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    Hi Rodrigo, and welcome to the User BB!

    Try port 80 on the Virtual Server with 8080 on the Real Server.

    Any luck?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    Hi Bob,
    Thanks for your greeting.


    Try port 80 on the Virtual Server with 8080 on the Real Server.

    It works! I don't understand why, but it does [;)]
    Thanks


    you should change it to "web protection" -> "web filtering" ->  "advanced"

    Hi oldeda,
    I just have the "Network Protection" and the "WebServer Protection" subscriptions enabled in our UTM.

    Regards to both.

    Rodrigo
  • 0 in reply to CRServers
    Hi Bob,

    I just have the "Network Protection" and the "WebServer Protection" subscriptions enabled in our UTM.

    Regards to both.

    Rodrigo


    for any other port problem you can change it under Definitions & Users
    there is no problem what subscriptions do you have
  • 0 in reply to BAlfson
    Hi Rodrigo, and welcome to the User BB!

    Try port 80 on the Virtual Server with 8080 on the Real Server.

    Any luck?

    Cheers - Bob


    In addition to this: If you need port 8080 for the Virtual Server you can use the following command on the console, which should free up port 8080: 
    cc set up2date parent_proxy_port 8081

    (unsupported, but AFAIK harmless [:)] )
  • 0 in reply to ulmi
    In addition to this: If you need port 8080 for the Virtual Server you can use the following command on the console, which should free up port 8080: 
    cc set up2date parent_proxy_port 8081

    (unsupported, but AFAIK harmless [[:)]] )


    Good to know, going in my file [[:)]]

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Sophos Platinum Partner

    --------------------------------------

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

Unfiltered HTML