| Description | This article describes the port conflict issue when the same port number 8080 is used for Explicit Web Proxy HTTP incoming port and HTTP Administrative Access port. |
| Scope | FortiGate. |
| Solution |
If Explicit Web Proxy is enabled even if not fully set up yet, port 8080 is by default automatically added in the configuration as the Explicit Web Proxy HTTP incoming port.
An error saying 'Administration settings failed to save : Entry is used.' will show up if port 8080 is attempted to be used as the HTTP Administrative Access port.
However, there will be cases where the HTTP port for Administrative Access is changed from default port 80 to port 8080 (since '8080' is easy to remember) before enabling the Explicit Web Proxy.
If this happens, a Port Conflict error will pop up saying 'HTTP Port (8080) is being used by system.global'.
The solution for this issue is to use different port numbers for the Explicit Web Proxy HTTP incoming port and HTTP administrative access port.
config web-proxy explicit set http-incoming-port 8080 end
config system global set admin-port XXXX <----- Where XXXX is any usable and vacant port number. end
Note: The easier adjustment will be to change the HTTP administrative access port since this port number is already customized. |
