“The WebSocket handshake failed” when using the cPanel Terminal
If you open cPanel → Terminal and see “Error: The WebSocket handshake failed”, don’t panic – this is a common issue and it’s usually caused by the way you’re accessing cPanel (proxy/VPN/service subdomain), not because your account is “broken”. This guide explains what the error means and the fastest ways to fix it on Hosticko.
Why This Error Happens
The cPanel Terminal runs in your browser and uses a WebSocket connection to the server. If that WebSocket connection is blocked, rewritten, or routed through a proxy that doesn’t support it properly, the connection “handshake” fails and Terminal can’t open.
The most common trigger is logging into cPanel through a proxy sub-domain like https://cpanel.yourdomain.com (especially if it’s behind Cloudflare or another reverse proxy). In those cases, Terminal may fail even though the rest of cPanel loads normally.
Fix 1: Use the Correct cPanel URL (Most Effective)
If you’re seeing WebSocket handshake failed, the #1 fix is to access cPanel using a direct URL that bypasses proxy routing.
Try these login methods (in order)
- Direct IP + port 2083 (best test)
https://YOUR_SERVER_IP:2083 - Domain + /cpanel path
https://yourdomain.com/cpanel - Service subdomain (only if it’s NOT proxied)
https://cpanel.yourdomain.com
Why IP:2083 works: It connects straight to cPanel’s service port and avoids proxy/CDN layers that may block WebSockets. This is exactly the recommended approach in the referenced guide for resolving this issue.
Fix 2: Disable VPN / Proxy (Quick Check)
VPNs, corporate proxies, “secure browsing” tools, and even some ISP-level filtering can block or rewrite WebSocket requests. If you’re using any of the following, temporarily disable them and try again:
- VPN (Nord, Express, corporate VPN, etc.)
- Browser proxy extensions
- Cloudflare WARP
- Company network filtering (try mobile hotspot as a test)
This is a very common root cause mentioned in real-world troubleshooting threads for the same cPanel Terminal error.
Fix 3: If You Use Cloudflare, Turn Off Proxy for cPanel
If your cPanel access is routed through Cloudflare (orange cloud enabled), WebSockets may fail for service endpoints. The safe approach is:
- Set the DNS record for
cpanel(or the hostname you use) to DNS only (grey cloud). - Then access cPanel again and open Terminal.
Note: You generally don’t want cPanel/WHM service ports sitting behind a CDN proxy anyway, keep it direct for reliability.
Fix 4: Clear Browser Cache / Try Another Browser
Sometimes a cached redirect, corrupted cookies, or an extension can interfere with the Terminal UI.
- Try incognito/private window
- Try another browser (Chrome → Firefox/Edge)
- Clear site data for your cPanel hostname (cookies + cache)
- Disable ad blockers / security extensions for the cPanel URL
Fix 5: Confirm Your cPanel Hostname SSL Is Valid (Advanced)
If your cPanel service hostname doesn’t have a valid SSL certificate, some browsers/proxies may block the WebSocket upgrade request. If you consistently get the error only on a hostname but not on IP:2083, it’s a strong hint the hostname path is the problem (DNS/SSL/proxy).
If you’re not sure what your correct hostname should be on Hosticko, open a support ticket and we’ll point you to the correct access URL.
How to Confirm It’s Fixed
After applying the fixes above:
- Login again using IP:2083 or /cpanel
- Go to cPanel → Terminal
- Terminal should load without the “WebSocket handshake failed” message
Common Questions
Does this mean my hosting account has a problem?
Usually no. In most cases, the issue is caused by how you are accessing cPanel (proxy/VPN/service hostname). Once you switch to the correct URL, it works normally.
Can I keep using cpanel.yourdomain.com?
You can, but only if it’s not behind a proxy and it’s correctly configured. For the most reliable access (especially for Terminal), the direct service URL (https://IP:2083) is the safest choice.
I tried everything and it still fails, what next?
Open a ticket. If needed, our team will check service-side causes (for example, environment-specific Terminal issues on certain server stacks) and guide you to the correct access method.
Need Help?
If you’re still getting WebSocket handshake failed after trying IP:2083 and disabling VPN/proxy, submit a ticket and share:
- The URL you used to access cPanel (domain, cpanel subdomain, or IP)
- Whether Cloudflare/proxy is enabled
- Your browser name/version
- A screenshot of the error
Submit a support ticket: https://client.hosticko.com/submitticket.php