Here on this page you can find some information about resolving known errors. But don’t hesitate to create a new issue on GitHub if you need any help.
If you encounter an error, you should refer to the logs first. All logs are stored in the Admin area-Internal logs section.
If you cannot log in and see the "Cannot update message" message in the right upper corner of the login page, you might have a problem with the database owner. This error occurs if the database was created manually and the owner was not changed. Set the correct database owner to resolve it: 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:
If you cannot start a service and find no corresponding messages in the logs, try to check its state first:
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.
During the installation via Ansible you may encounter the following error:
This a known Ansible bug. To resolve it update Ansible to version 2.9.8 or newer.
You may also receive the following error message during the installation via Ansible:
This is a known bug of the NGINX official repository. It might be resolved soon. Now the only possible solution is to update Ansible at least to version 2.12.
On some Ubuntu installation could be:
It would appear because there is no needed package. Install it:
In the course of installation of Roxy-WI you may encounter the following error:
In order to resolve this problem, open the /etc/yum.repo.d/roxy-wi.repo file and replace $ostype with el in the line, which begins with $baseurl.