Subdomain is Active but Website Cannot Be Reached
Posted by slna in general.
Replies
The subdomain routes to your server’s primary port , so adding can cause the timeout. Since the site works at your server IP and port, try: 1. Open without . 2. If it still doesn’t load, check that the subdomain is linked to the right server and that its primary port matches your app’s listening port. If you changed the primary port, recreate the subdomain. More details: https://wispbyte.com/kb/subdomains
Hello. I followed your instructions and checked everything: My server is running correctly. The primary port is 12840. My Python application listens on port 12840. The website works through the direct IP address on some devices and networks. However, the subdomain still returns a connection timeout, even when using the port. Some users also cannot access the website through the direct IP. Could you please check if there is any issue with subdomain routing or external access to my server's port? Thank you.
Because the direct IP also fails for some users, this may not be only a subdomain routing issue. First check that your Python app binds to (not ) and uses port . 1. Test without a port ; the subdomain uses the primary port. 2. From the same device/network, compare that with . If the IP works but the subdomain times out, delete and recreate the subdomain, then test again. 3. If it still fails, post the node name, support tag, and which of those two URLs works from the same network. Since subdomains are in beta, persistent routing problems may need a person to investigate. https://wispbyte.com/kb/subdomains
Hello again. I deleted and recreated my subdomain, but the problem is still there. When I open dragonrealm.wispbyte.app, Cloudflare shows error 504 (Gateway Time out). The browser and Cloudflare are working, but the host is showing an error. My server is running, the primary port is 12840, and the website works through the direct IP address on some devices. Could a support staff member please investigate the subdomain routing or server connectivity issue? Server ID: 2de57a1c Node: FREE EU RO 14 Thank you.
A Cloudflare 504 after recreating the subdomain points to a routing or origin connectivity issue, especially since the direct IP works for some users. Your server is online and there’s no matching outage posted, so a person will need to investigate the subdomain path. Please contact the Wispbyte community team on Discord and include the node name, your server’s support tag (shown in the Console side panel), and that the app listens on . For setup details, see Subdomains.