"Server is offline" error
This error means our nodes cannot reach your backend. We are happy to help, but most cases come down to one of the checks below, so start here.
Checklist
1. Check Proxy Protocol
Make sure Proxy Protocol is turned on in the panel and that your backend has all the config options from the Proxy Protocol guide. Both sides have to match, or connections fail.
2. Check the backend IP and port
Re-check that the backend IP and port in the panel are the ones your server actually uses.
On a Linux server, ss -tulpn lists the ports your machine is listening on, so you can confirm the port is open.
3. Check your firewall
If you have set up a firewall, make sure it still allows all NeoProtect IPs to reach your server port. These commands show your current Linux firewall rules:
ufw statusiptables -Siptables -t raw -S
4. Check for interfering plugins
Remove any leftover plugins from a previous protection provider. Also check whether an anti-bot plugin is blocking or rate-limiting our connections, which some BungeeCord forks do.
5. Check your host's own protection
Some hosts run their own DDoS protection that can block our traffic. Because all your traffic arrives from a small set of NeoProtect IPs, their systems may flag it as suspicious. If your host does this, ask them to allow our IPs.