The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Facebook won't load?
Penguin_Otaku
Registered User regular
Registered User regular
So I've been having issues connecting to Facebook and I think it's been since I chose the option to make my connection a secure one with Facebook.
I've tried Chrome, Firefox and Safari and it's doing the same thing on all of them.
Earlier I deleted my cache, restarted and it worked for a little bit. Then it tried to load updates and eventually just shit itself and won't reconnect again.
Thoughts?
I've tried Chrome, Firefox and Safari and it's doing the same thing on all of them.
Earlier I deleted my cache, restarted and it worked for a little bit. Then it tried to load updates and eventually just shit itself and won't reconnect again.
Thoughts?
Penguin_Otaku on
0
Posts
Are you able to connect to other websites on your machine? (You could be posting this from a phone or a tablet, or a microwave for all I know)
Are you able to connect to your facebook from other machines?
That you where able to connect after deleting your cache for a while makes it sound like you may have some malware on your system that's dicking around with you. If you haven't already, I'd suggest running a full scan with your anti-malware of choice.
No 404 error just that it times out.
Can connect from my phone
did something about making your connection with facebook 'secure' (not sure what this means) involve editing your hosts file? That could also cause a problem, but it's generally something that you'd know if you did
that's why we call it the struggle, you're supposed to sweat
I think when you enable the option to make your connection secure on Facebook, it just means you're always using an HTTPS url as opposed to an HTTP one. Not sure what the problem might be here, but yeah, flushing your DNS never hurts. Maybe check your proxy settings in your browsers?
You're welcome, @Tube.
oh right yeah thanks
oh, duh
yeah probably what's happening is that either your hosts file or dns cache has facebook set to a certain ip, which is different from the ip used by their ssl site. Solution is to purge both of those things.
that's why we call it the struggle, you're supposed to sweat
This does sound like a DNS issues, but it's unlikely that the public IP got HTTPS is different from HTTP. DNS resolution is not aware of protocol only the symbolic name. So if you just get sent to https://somehost vs http://somehost you will by definition get the same DNS resolution. It's only if you get sent to another subdomain that you'd get a different resolution. But in that case caching the wrong resolution wouldn't really apply as it would be the resolution for a different symbolic name.
bluecoat packetshaper does not like to deal with https connections
Not on a college network.
DNS flushing isn't doing it