Troubleshooting

General information About logs Worker diagnostics in 9.2 Errors that occur when starting Roxy-WI services Errors that occur when updating Roxy-WI Internal server error Error when downloading metadata during installation Roxy-WI key error

General information

On this page, you can find information about resolving known errors. However, if you need further assistance, please don't hesitate to create a new issue on GitHub.

Roxy-WI is constantly developing, and as a result, bugs may occur. You are very welcome to report any bug on GitHub!

Logs

If you encounter an error, you should first refer to the logs. Start with Admin area → Internal logs; managed-service logs and worker-host logs have separate sources.

Select the relevant log source and use Refresh, Find or Live. For request details, open WAF logs and select the audit source. For more detailed information, refer to the Roxy-WI logs and the error log as well.

Worker diagnostics in 9.2

Click the worker status on Overview or Admin area → Tools. Inspect the current instance's heartbeat and task errors, expand parallel processes or process history, and follow the reported recovery guidance. See the diagnostic reference.

A stale heartbeat is not proof of a stopped process: check the worker host, RabbitMQ and Service Events. Historical errors belong to the last report. Metrics graphs can remain available after a registered worker stops; check timestamps before treating them as current samples.

Localized error pages in 9.2 hide unexpected exception details. For a failed web action, inspect Internal logs and the relevant process logs using the time of the request.

Errors that occur when starting Roxy-WI services

For a package-managed worker, check its actual unit and journal on the worker host. For example:

systemctl status roxy-wi-checker
journalctl -u roxy-wi-checker -n 100 --no-pager

For containers, inspect the worker's container logs or Kubernetes pod events. Use the Checker and Metrics guides for their own configuration. Manage Web, Scheduler, Service Events and Operations using the application role reference. Starting a legacy script or installing a worker on the Web host does not repair a remote deployment.

Errors that occur when updating Roxy-WI

If you encounter any errors while updating Roxy-WI through the web interface, try updating it via the command line:

                                For YUM:
                                yum clean all
                                yum update roxy-wi
                                
                                For APT:
                                apt-get clean
                                apt-get update
                                apt-get install roxy-wi

Internal server error during the first start or after update

If you see an Internal Server Error when launching Roxy-WI for the first time, open the Apache error log; it is likely that some modules are missing. If that is the case, install the required modules from GitHub.

Or after installation you see Internal Server Error, look at the Apache error log. If you see:

                                FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/roxy-wi/keys/roxy-wi-key'

Do next:

                                ssh-keygen -t rsa -b 4096 -m pem -f /var/lib/roxy-wi/keys/roxy-wi-key -C "Roxy-WI JWT KEY. DO NOT DELETE IT!" -P ""
                                chown apache_user:apache_user -R /var/lib/roxy-wi/
                                systemctl reload apache_service

There could be a problem with the OpenSSL version:

                                OpenSSL version mismatch. Built against 30000010, you have 30500050

Try to update OpenSSH server, and recreate ssh key again.

Error when downloading metadata in course of installation

During the installation of Roxy-WI, you may encounter the following error:

                                Errors during downloading metadata for repository 'roxy-wi':
                                - Status code: 404 for https://login:password@repo.roxy-wi.org/$ostype8/repodata/repomd.xml (IP: 172.67.172.199)
                                
                                Error: Failed to download metadata for repo 'roxy-wi': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried

To resolve this issue, open the /etc/yum.repos.d/roxy-wi.repo file and replace $ostype with el in the line that begins with $baseurl.

Roxy-WI key error

After the installation of Roxy-WI, you may encounter the following error:

                                FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/roxy-wi/keys/roxy-wi-key'

To resolve the issue, run the SSH key generator:

                                ssh-keygen -t rsa -b 4096 -m pem -f /var/lib/roxy-wi/keys/roxy-wi-key -C "Roxy-WI JWT KEY. DO NOT DELETE IT!" -P ""
                                chown apache_user:apache_user -R /var/lib/roxy-wi/
                                systemctl reload apache_service