Troubleshooting RouteGlass

Service Inactive Or HTTP 502

systemctl status routeglass --no-pager -l
journalctl -u routeglass -n 100 --no-pager
curl -v http://127.0.0.1:8080/
nginx -t
systemctl status nginx --no-pager

A failed localhost response points to the application or its service. If the backend works, inspect Nginx configuration and logs before restarting components.

BGP Temporarily Unavailable

The public interface intentionally hides detailed router errors. Inspect RouteGlass service logs privately. Check backend address/port, read-only permissions, CA trust for MikroTik, or SSH key and pinned host-key trust for Juniper/VyOS.

HTTP 429

The optional v1.4.3 rate limits separate web traffic (5 requests/second, burst 30) from diagnostic/BGP traffic (30 requests/minute, burst 10). Wait before retrying. Review legitimate traffic and proxy configuration before changing limits.

HTTPS Problems

Confirm the hostname resolves to the correct server and ports 80/443 are reachable. Inspect Nginx and Certbot logs. The v1.4.3 installer adds HSTS only after successful HTTPS provisioning.

Before Reinstallation

Back up /etc/routeglass/ securely if preserving credentials and configuration. Treat that backup as sensitive. Do not attach it to an ordinary support email.