Thread Info
  • Locked Locked
  • Replies 6 replies
  • Subscribers 4 subscribers
  • Views 8891 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

Minor bug - Web Server Protection not checking the proxy port

Mateusz Bender

Hi,

I've noticed a while back that the Web Server Protection would notify the user if the IP + port they were trying to use was already used by another service (for example, the user portal).

Today I've hit a small snag trying to enable a server on port 8080. It seemed fine from the UI, but the page wouldn't work. It was only later that I realized that the 8080 is likely in use by the transparent proxy.

Not a huge issue, of course, but it would be nice if the UI was consistent and could report when a IP + port is in use in all cases.

BTW: why can't I have the user portal running on the 443 port along with other virtual web servers? I mean - it all works by host-name, so there shouldn't be an issue. :/



This thread was automatically locked due to age.
Parents

  • I get a warning when Web protection is enabled in transparent mode and I try to configure WAF on port 8080:

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

    User portal and WAF are provided by two separate Apaches (for security reasons), that's why port sharing isn't possible.

Reply

  • I get a warning when Web protection is enabled in transparent mode and I try to configure WAF on port 8080:

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

    User portal and WAF are provided by two separate Apaches (for security reasons), that's why port sharing isn't possible.

Children
Unfiltered HTML