Wispbyte Subdomain Returns Cloudflare Error 520 Despite Being Active

Since the app responds directly on its allocated port, Express is probably fine. A 520 through the subdomain points more toward the beta proxy route or origin handling than an app level HTTPS setup. 1. In Subdomains , check that the subdomain is linked to this server and its primary port is . 2. Remove and recreate the subdomain, then test again. 3. If it still returns 520, report it in the Wispbyte Discord with the subdomain and the time you tested; include the direct IP and subdomain results. See the Subdomains guide.

its timing out

If the direct URL still responds but the subdomain times out, the app is reachable; the remaining issue is likely the beta route or its target port. You don’t need to configure HTTPS in Express for the subdomain. Check that is the server’s primary port, then try as well. What exact Cloudflare error code do you get, and does HTTP time out too? That will help distinguish a routing timeout from the earlier 520.

Additional update: My ISP, Spectrum, is also blocking through Security Shield and displaying a "Suspicious Site Blocked" warning. The direct server health endpoint still works: Could this be related to the subdomain's SSL configuration or domain reputation?

Spectrum’s “Suspicious Site Blocked” warning is more likely an ISP/domain reputation filter than an SSL setting in Express. Your direct HTTP health check confirms the app responds, but it doesn’t verify the subdomain’s proxy route; an Active entry doesn’t guarantee that route is working. 1. Test on mobile data or another network. Don’t bypass Spectrum’s warning if you’re unsure the site is safe. 2. If it works elsewhere, ask Spectrum to review the block. If it fails elsewhere too, report the subdomain and test times in the Wispbyte Discord; include the exact Cloudflare error. Since it’s still unresolved, a Wispbyte staff member will need to check the beta route. Subdomains guide.

Further update – Intermittent connectivity The subdomain has randomly started working again in my main browser, and it also works over mobile data. However, it previously returned: Cloudflare Error 520 Chrome ERR SSL PROTOCOL ERROR Spectrum Security Shield "Suspicious Site Blocked" The direct IP health endpoint consistently responds successfully. I don't want to use this for a staff dashboard if connectivity is unreliable. Could Wispbyte staff investigate the SubdomainsBeta proxy, TLS handshake, and routing for my server? Node: FREE EU RO 10 Server ID: 1bed2033 Subdomain: hcstaff.wisp.uno Port: 15643

Okay, sometimes subdomains go down its not always 100% sadly. Thats what i learnt!

It's working, and as CJL said, sometimes subdomains go down