If your subdomain is timing out or not loading, the cause is usually DNS propagation, missing files in the subdomain directory, or an SSL certificate that hasn't been issued yet. This guide walks through each cause and how to fix it.
Most Common Cause
If you just created the subdomain, wait 1-2 hours for DNS propagation. Check propagation status at whatsmydns.net by looking up the subdomain A record.
01. DNS Propagation
When you create a subdomain in cPanel, a DNS record is added automatically. Subdomains use the same nameservers as your main domain, so they typically propagate within a few minutes to a couple of hours. Use whatsmydns.net to check if the subdomain A record is resolving to your server IP.
If the A record is not showing, the DNS hasn't propagated yet. Wait a couple of hours and check again. If it still hasn't appeared after 24 hours, verify that your main domain's nameservers are set correctly:
ns1.ultranameservers.com
ns2.ultranameservers.com
ns3.ultranameservers.comFor more on DNS propagation, see our DNS Propagation guide.
02. Missing or Incorrect Files
When you create a subdomain in cPanel, it creates a directory for that subdomain's files. Make sure you have uploaded files to the correct directory.
- Check the directory path - go to cPanel > Subdomains (or Domains in newer cPanel). Note the "Document Root" for the subdomain (e.g.,
public_html/blog) - Upload files there - use FTP or cPanel File Manager to place your files in that exact directory
- Check for index file - the directory needs an
index.html,index.php, or similar default file
03. SSL Certificate
If the subdomain loads on http:// but not https://, the SSL certificate may not have been issued yet. AutoSSL (Let's Encrypt) automatically covers subdomains, but it may take a few hours after creation.
Check the status in cPanel > SSL/TLS Status. If the subdomain shows as "DCV Pending" or has no certificate, click "Run AutoSSL" to trigger a new certificate request. If your site has an .htaccess rule forcing HTTPS, the subdomain will fail to load until the certificate is in place.
04. Browser Cache and Local DNS
Your computer may have cached a failed DNS lookup from before the subdomain was created. Try:
- Different device - try from your phone on cellular data
- Incognito window - bypasses browser cache
- Flush DNS - on Windows:
ipconfig /flushdns, on Mac:sudo dscacheutil -flushcache
If you use Cloudflare, make sure the subdomain has an A record in your Cloudflare DNS pointing to the correct server IP.
Subdomain Still Not Working?
If you've checked all of the above and the subdomain still doesn't load, open a ticket with the subdomain name and we'll investigate.
Open a Support TicketQuick Recap
- Wait for DNS - subdomains typically propagate in 1-2 hours
- Check the directory - verify files are in the correct subdomain folder
- Check SSL - AutoSSL may need time, run it from SSL/TLS Status
- Clear cache - flush DNS and try incognito
- Open a ticket - if none of the above fixes it
Last updated March 2026 · Browse all Troubleshooting articles
