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 have recently hosted my site which intends to use wildcard subdomains in its general use. A user would go to account.website.com to access their part of the site. The site is a rails app hosted on heroku and domain is through 123-reg. DNS is set up as per heroku - * , cname , wildcard.app.heroku...
At first i thought 123-reg couldnt handle wildcard routing and i would have to change dns provider as whenever i go to account.website.com it will send me to www.account.website.com which is extremely irritating, but then i found that this does not happen on my windows machine, only on my dev machine (macbook pro). In both cases i am using Chrome. Firefox works as desired, only chrome is messing up.
Any insight into why this is happening would be fantastic.
Thanks
Obviously i immediately solve it after asking and look like a fool - Apparently the cache remembers the redirect from when i assume i hadnt yet set up dns correctly. If you get the same problem, clear browser cache
I have bought my domain from one domain registrar and set domain forwarding to where my website is hosted. Now I have setup my website on amazon cloud and did all changes as described and changed DNS changes from my domain registrar.
Everything works good from IE and even from inbuilt browser of Eclipse. But Firefox is still taking to the site where site was hosted earlier.
what is the reason and how to resolve? I have cleared the cache related to website.
Perhaps these links may be of help:
Firefox invalidate dns cache
http://en.kioskea.net/faq/555-disabling-the-dns-cache-in-mozilla-firefox
I am learning JMeterProxy using WAMP and opencart web app.I did a recording using HTTP Proxy Server. I configured firefox and recording went smoothly. But if i am using IE, nothing seems to be recorded. I added a tree view listener in HTTP Proxy to log the recording, nothing is logged in it when i am using IE.
Some observations:
when i stop recording and if i try to access the local site using FF, it is not accessible, but in case of IE i could open the site.
If i browse an external site, recording is working.
I am accessing my site as http://localhost:81/opencart/index.php, since 80 port is used by IIS
My question is.
How would i trouble shoot this kind of scenario.
What changes i should i make in IE proxy settings.
I solved this problem, Here is the solution, as per JMeter documentation
If JMeter does not record browser URLs such as http://localhost/ or
"http://127.0.0.1/", try using the non-loopback hostname or IP address,
e.g. http://myhost/ or "http://192.168.0.2/"
So providing the host name in place of loop back address solved the problem
I have some pages on my local machine, accessed via localhost, that are horribly slow to open/load using IE8, but very fast using Firefox, Opera, Chrome and Safari.
They used to load really quickly using IE7.
I produced a cut down page to test - to see what was causing the problem - and seriously, the most simple page possible causes it! I.e:
<html>
<head></head>
<body>
Hello!
</body>
</html>
Takes about 15 seconds to open on localhost in IE8, and is instant on all other browsers! Why? What can I do to resolve this?
By the way, tried this on a Web server, connecting via a URL via IE8, and it was basically instant when opened via IE8 via the Web/Web server!
I have Windows Update enabled, so should have the latest of everything.
Note: I only noticed this after my internet connection changed, which was about 2 weeks after IE8 was installed. Possibly that is coincidence, it MAY have started with the install of IE8, I am actually not sure. It is definitely happening now though.
The URL I am using is: http://localhost/fb/starttest.htm
Help!
Try the following:
1- Navigate to C:\Windows\System32\drivers\etc
2- Open the file hosts using any text editor
3- Add this line to the end of the file
127.0.0.1 localhost
4- Before you save this file, you need to make sure that any program that access the internet (browsers etc.) is closed - Save the file and test it
Under Tools -> Internet Options -> Connections -> LAN Settings, is the box "Automatically detect proxy servers" checked?
If so, that does a DNS request to wpad.(domain search suffix) to discover proxy servers via their Auto Discovery Protocol.
If nothing responds, the query will have to timeout before it gives up.
I also had this exact same problem recently - 'localhost' taking 15 seconds to load, but 127.0.0.1 loading instantly.
However, I have now fully solved my problem, so I write here in the hope that it will help someone.
My problem coincided with the purchase of a D-Link DIR-655 wireless router, so after trying many of the kindly offered 'fixes' on this forum, I turned back to my router settings in search of an answer.
I eventually discovered a setting on the SETUP - NETWORK SETTINGS page. The 'Enable DNS Relay' box was checked, so I read about it, and it apparently allows the router to lookup DNS addresses from the ISP's server. This is obviously not desired for a 'local' address on my own PC, and so I tried unticking it.... and HEY PRESTO, IT WORKED!!!
I hope this work for some of you, too!
All the best,
Rob
I have exactly the same problem as you do, except I'm using IE7 (IE takes about 16 seconds to load localhost, while Firefox and Google Chrome loads it in an instant).
I don't have the autodiscovery for proxy checked either.
I also tried starting IE without add-ons (From Accessories->System Tools) and it didn't make a difference.
I found out that using 127.0.0.1 instead of localhost greatly improved the speed (like 2 seconds instead of 16 seconds!). However, I edited hosts file and I left only the line
127.0.0.1 localhost
and this didn't fix the problem. Need to dig some further.
Regards,
Nicolae