Below you will find the recommendations for error identification and the description of the possible ways of resolving the most common errors.
If you encounter an error, you should refer to the logs first. It is necessary to define the possible cause and the circumstances of the error. All logs are stored in the Internal logs section. Begin with the logs of the service in which the error has been detected. For more detailed information refer to the logs of Roxy-WI and to the error log as well.
If you cannot log in and see the "Cannot update message" message in the right upper corner of the page, you must have a problem with the database owner. This error occurs if the database was created manually and the correct owner was not changed. To resolve it, set the correct database owner: apache (in CentOS) or www-date (in Debian and Ubuntu).
When you cannot install HAProxy, Nginx, or Keepalived) and no error is displayed in the logs, try to run
the installation via the web interface and perform the following command in your terminal:
ps ax|grep bash
In the output you should see the line containing the name of the script "installation_serviceName.sh".
Copy it and perform the following commands:
If you cannot start a service and find no corresponding messages in the logs, try to check its state first:
systemctl status roxy-wi-service_name
For more information you may also refer to the system logs: /var/logs/message (in CentOS) and /var/log/syslog (in Ubuntu)
If referring to the logs does not help, try to run the service manually:
If any errors occur when updating Roxy-WI via the web interface, try to update it via the command line:
If you see the Internal server error when launching Roxy-WI for the first time, go to the /var/www/haproxy-wi/app directory and check whether the execution of all *.py files is allowed.