Resolving the Apache HTTP 404 issue

Resolving the Apache HTTP 404 issue

Resolving the Apache HTTP 404 Issue

When connecting to the Web Client, if the HTTP Status 404 error displays, refer to the listing below to resolve the issue.

  • Ensure that the URL is using the correct IP Address and Hostname.

  • Ensure that you have obtained a valid license for the product. The <productName>.lic file is located at /opt/CSI/PureWeb/Server/conf. FOr information on how to obtain a license, refer to the ResolutionMD Server Deployment and Administration Guide.

If the URL is correct and you have a valid license, restart the PureWeb service by following the steps below.

  1. SSH to the server with a user that has root permissions.

  2. Execute: service pureweb restart.

If you have restarted the service and the error still displays, there may be a conflict between the server and the internal/external network. For example, the wrong IP or Hostname. To verify follow the steps below.

  1. From the computer itself, ping the server Hostname or internal IP.

  2. From another computer, ping the server Hostname or external IP.

  3. Telnet into the server Hostname or IP on port 22.

If you are using a mobile device and have implemented URL integration, ensure that you are using the correct protocal in the URL. The correct protocal is resmds, not https.

Confirm that the firewall has port 8080 or 8443 open by following the steps below.

  1. SSH to the server with a user that has root permissions.

  2. Execute: service iptables status.

  3. Disable iptables.

  4. If this resolves the issue, edit the firewall rules as needed.