I have changed my DNS provider for my tech business right now. I set up the DNS, and it is working fine. However whenever I try to turn on proxy I get a 503 error on the browser and 503(1001) on built-in speed test. What might be the issue, it happened to same site with two different hosting providers. Only happening to this domain name weirdly.
Domain is skalcollective.com
Cheers,
Berk.
Related
I keep having this error when I try to access my website that is hosted on aws and using cloudflare CDN.
But the surprising thing is that it is loading correctly on another person's phone.
What can be the issue and how can I resolve it?
Cloudflare error
This error specified a connection error between Cloudflare and your Origin server.
There are a couple ways this could be occurring on your device but not another's -
If you recently added Cloudflare, the DNS may still be resolving to your Origin server (for the person who it is working for). You can check this by doing a ping on their device to your domain, and seeing if it resolves to your Origin IP. Or you can check the response headers for any with CF- prefix (which means it is likely routing through Cloudflare).
Another possibility is that your Origin server is blocking some Cloudflare servers but not others. For instance when you request the site, it may be routing through Cloudflare 'Server A', while when the other person requests your site, it is routing through 'Server B'. If 'Server A' requests are failing / being blocked, this would explain the behavior you are seeing. You can check your Origin server's access logs to see if this is occurring. If it is a blocking situation, you'll want to ensure all Cloudflare's IP are whitelisted - https://www.cloudflare.com/ips/
More troubleshooting information from the Cloudflare forums - https://community.cloudflare.com/t/community-tip-fixing-error-522-connection-timed-out/42325
So I have a rails multi-tenant project running on Heroku where we identify what to serve based on the domain you access from. These domains are added to the app's heroku domains and the cname records provided by Heroku for www.domain.com are added to the domain's DNS and we also add a permanant redirect rule for domain.com/* -> www.domain.com/$1 so that people can access without a www.
This all works perfectly fine on Chrome/Firefox, but on Safari and IOS devices we've been getting reports and were able to reproduce that the websites simply timeout.
I have tried to monitor traffic with wireshark, I can see the GET HTTP request going out but nothing comes back.
I have tried to access the app directly using the appname.herokuapp.com URL, it works perfectly fine in that case.
I have tried accessing with a VPN (Cloudflare WARP), the issue is not present in this case. However I tried manually setting the DNS to Cloudflare's and that did not fix the issue. I have also tried 3 different ISPs and that was also not the issue.
So to sum up, the issue happens if:
You're accessing using a domain that POINTS TO a CNAME record (xxx.herokudns.com) that POINTS TO the app.
You're not using a VPN/Cloudflare WARP.
You're on Safari.
I have found a reference for this issue here but this dates back to 2015. I also have doubts that this Safari update could be relevant.
Has anyone been through this previously or can provide insights on to how I can further debug this?
I'm having some problems configuring the DNS settings for my custom domain to work correctly on Heroku.
I have set the DNS records as follows:
Host Type Points to
example.com WR www.example.com
www.example.com CNAME example.herokuapp.com
www.example.com.au CNAME example.herokuapp.com
However, the 'www.example.com' domain sometimes fails to load on my computer, as well as my client's phone. It seems rare for this domain to fail (it works fine on everyone else's computers that I've asked), but the fact that it doesn't work on mine and my client's computers is a problem.
However, the '.com.au' domain (and the heroku one) always works. Why is this?
Is there anything wrong with the configuration above? I followed the 'custom domain names' article on heroku to reach this configuration (I don't have much experience with DNS, unfortunately). The DNS provider I am using does not support ANAME or ALIAS so I went with the above config instead.
Thanks. Any help in getting the '.com' domain working on every device would be appreciated.
I'm not really sure, it may be a lot of things, DNS caching and other stuff.
But if you don't have a lot of DNS records, I suggest you use a heroku add-on like PointDNS (https://addons.heroku.com/pointdns) as it supports ALIAS.
I have a Joomla 2.5 site set up but when I try to access the domain I get an intermittent error on the screen just saying "Not found". It sometimes happends when visiting with www, sometimes with http:// and sometimes with http://www.
Here is the error: http://imgur.com/7f6ak
I have done a thorough look into the domain and all the DNS and records are working as expected and resolving correctly all around the world making me think it must be a Joomla error of some kind.
I have also tried to enter the sites domain into the $live_url in the configuration file but it stil happends.
Any help or ideas greatly appreciated
In short, it's sometimes not finding your site, so not knowing if you host the site or you use a service...
We occasionally experience this if we haven't copied the site across all the servers on our load balancer - Perhaps checking if all your servers have the site, or if your host has load balancing and it didn't get propogated properly. Also be sure the apache or htaccess settings are the same to account for the www or not.
Either you installed Joomla to another directory or the DNS still haven't resolved. Try to ping your site to see which IP it's responding to.
I have set up a subdomain abc.mysite.com to point a specific IP on another server. I did this by creating the following A records:
abc 300 in A xx.xxx.xx.xx and www.abc 300 in A xx.xxx.xx.xx
My host confirms that this was done correctly, however (3 days later) the domain still resolves intermittently. That is, sometimes it resolves to the correct IP and I see the correct page and other times I see a 404 error or a default website page from cpanel.
My host suggests that it is a caching issue and if I perform a flushdns and clear my browser cache, this fixes the problem. But i am puzzled as to why it reoccurs.
Could there by something on the other server triggering it? Or is it just a matter of waiting a little longer for propagation?
Forgive me if the problem isn't clear. This stuff is not my forte.
A 404 error indicates an error on the webservers side - not on the DNS level. That means, that if you see a 404 error or the cPanel default site, DNS is working fine but the web server does not respond.
http://en.wikipedia.org/wiki/HTTP_404#Overview
Check the web server logs and/or speak to your provider about the issue.
What was the TTL before you made your changes? I've seen 86,400 seconds (one day) and 604,800 (one week) as common choices in the past. (The important number is what the TTL was set to before you made your change, as that dictates how long stale data is held in DNS caches.)