You set up the redirect and changed the DNS entries, but it isn't working yet! Here are some troubleshooting tips.
DNS is changed but it's still not redirecting!
Sometimes browsers cache the old result of the domain quite long. It's best to check the redirect domain via the following other ways:
- Try it in another browser
- Try it in an incognito window
- Try it via the command line
- Check it via our tester: https://redirect.pizza/tester
Still not working via any of the options above? Give it some extra time before it's working on your browser as well. Want to make sure? Add a random query string behind your source to force-check it locally.
For instance, if your redirect is example.com, try it with "https://example.com?v=2"
Did the DNS fully propagate?
You changed the DNS with your DNS/domain provider, and retried the DNS checker in redirect.pizza and it went green! You checked it right away in your browser, but it's not working yet.
It's important to give the DNS change some time to propagate. This can take up to 24 hours. You can:
- See how far along it is with something like whatsmydns.net
- Ping the domain on your own machine (ping example.com). Here some more info.
Redirect works but shows a certificate error?
redirect.pizza automatically provisions SSL certificates for your domains. Certificates are issued shortly after your DNS points to our servers. If you see a certificate warning, wait a few minutes and try again.
Still not working?
Still not working after a few hours and tried the steps above? Our redirect troubleshooting guide covers additional scenarios including SSL errors, redirect loops, and DNS propagation issues. If that doesn't solve it, contact support via the chat or send us an email on support@redirect.pizza. We are happy to help.
