Control panel does not open (port 2083 or 2087)

Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Still not working?

The panels run on their own ports: customers on 2083, administrators and resellers on 2087, webmail on 2096. If the page does not load at all, the cause is the address, the network between you and the server, or the panel's services on the server.

Symptoms

  • ERR_CONNECTION_TIMED_OUT, "This site can't be reached" or ERR_CONNECTION_REFUSED.
  • "Your connection is not private" when opening the panel.
  • "Something went wrong — An unexpected error occurred. It has been logged."

Causes

Most likely first:

  1. The address is wrong — missing port, http:// instead of https://, or the wrong server name.
  2. Your address is blocked at the server's firewall (failed logins or the Protection Shield).
  3. Your network blocks the port (office, school or hotel networks often allow only 80 and 443).
  4. The panel's web service is stopped on the server.
  5. Certificate warning: you open the panel by IP address, or the server's name has no certificate yet.

Fix

1. The address

Use https:// and the port, with the server name your host gave you:

  • Customers: https://server.example.com:2083
  • Administrators and resellers: https://server.example.com:2087

http:// on these ports is sent to https:// automatically.

2. Blocked address

If the panel, the websites and email all stop working from your network but work from mobile data, your address is blocked. See My IP is blocked.

3. Network blocks the port

Try another network (mobile data). If the panel works there, ask your network's administrator to allow ports 2083 and 2087, or use the panel from another network.

4. Panel service stopped (administrators)

Connect to the server with SSH as root and check the panel's web server and PHP:

systemctl status nginx php8.3-fpm
systemctl restart nginx php8.3-fpm

Also check that 2083 and 2087 are in Open TCP ports on the Firewall page (2087 always stays open). After an update, see Panel update failed.

5. Certificate warning

The panels, webmail and the mail server share one certificate for the server's name. Opening them by IP address (https://203.0.113.10:2087) always shows a warning. Use the server name instead. Administrators: if the name also shows a warning, make sure its A record points to the server and click Issue hostname certificate in Server Settings → Certificates.

"Something went wrong"

The page failed inside the panel and the error was logged (and reported, when error reports are on). Go back and try again. If it repeats, send your host the time and what you clicked.

Still not working?

If pages open but changes do not take effect, see Tasks stay queued. If the login page opens but you cannot sign in, see Cannot log in to the control panel.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.