Website Access
Troubleshooting website access
This page separates two situations: a client cannot open an external website, or the OOS management page cannot be opened. Record the full URL, error message, time, and affected device before troubleshooting.
Website Shows 404: Check the URL and Page First
404 Not Found means a website server responded but could not find the requested page. This is usually not a reason to change OOS network settings.
- Check the full URL for typos, extra characters, or an incorrect path.
- Open the same website's home page or another page to see whether the problem is limited to one URL.
- If only one page returns 404, ask the website administrator whether it was moved or removed. Do not change WAN or DNS just because of a 404.
Website Name Cannot Be Resolved: Check DNS
If the error says the server cannot be found or the hostname cannot be resolved, rather than showing 404, inspect DNS settings. DNS translates website names into IP addresses; Ping checks whether a target responds. Test IP connectivity and access by website name separately to help locate the problem.
- Go to
Networking > WAN > Multiple WAN. - Click the edit icon in the active WAN interface's Action column. Compare DNS settings with those supplied by the network administrator or service provider. Do not copy screenshot values.
- Correct DNS only if you have confirmed that the settings are wrong, then test website-name access again.


OOS Cannot Be Accessed Directly, and the Controller Does Not Show Device Information
This section applies when OOS remains accessible through the Controller’s Jump to device function. The Controller centrally manages devices; Jump to device opens a device page from that system.
Another application using port 80 is one possible cause. HTTP is how a browser communicates with a website, and port numbers distinguish services. If you confirm that an application and the OOS management page use the same port, choose one adjustment:
- Change the application’s settings so that it does not share the OOS port; or
- Go to
General > Deviceand change the HTTP port under Local Access Configuration. Some manual screenshots label the tab Host; follow the labels for your version.

Record the new port and keep an available management route before changing it. Reopen OOS using a URL that includes the new port (http://<device-address>:<new-port>), then check whether the Controller displays device information again. If Jump to device also fails, provide the symptoms to the administrator or support team for troubleshooting.