Going Live - Troubleshooting
If all steps above have been followed and the site still does not resolve (after waiting for the DNS update to propagate), here are a few simple self-help steps to take before contacting support.
On the command line with OS X or Linux (or using the Linux subsystem for Windows) type
The response should be something like:
www.example.com is an alias for main-t2xxqeifuhpzg.eu.platform.sh. main-t2xxqeifuhpzg.eu.platform.sh has address 18.104.22.168
- If it isn’t, either you have not configured correctly your DNS server, or the DNS configuration did not propagate yet. As a first step you can try and remove your local DNS cache.
- You can also try to set your DNS server to the Google public DNS server (22.214.171.124/126.96.36.199) to see if the issue is with the DNS server you are using.
- Try to run
ping www.example.com(with you own domain name). If the result is different from what you got from the
host www.example.com, you might want to verify your
/etc/hostsfile (or its windows equivalent), you might have left there an entry from testing.
On the command line with OS X or Linux (or using the Linux subsystem for Windows),
curl -I -v https://example.com (again using your own domain):
The response should be long. Look for error messages. They are usually explicit enough. Often the problem will be with a mismatch between the certificate and the domain name.
On the command line type
platform logs app and see there are no clear anomalies there.
Do the same with
platform logs error
We are here to help. Please include as much detail as possible (we will be able to provide quicker help).