Facebook won't load?

Penguin_Otaku

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?

see317

Are you just getting the standard 404 error?
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.

Penguin_Otaku

Other sites work perfectly.

No 404 error just that it times out.

Can connect from my phone

WiseManTobes

Is your Facebook fully logged out on your phone when you try and load up on your comp? If you went for secure it's really touchy and might see that as someone else trying to "login"

Eat it You Nasty Pig.

this kind of thing is usually a DNS resolution issue; type ipconfig /flushdns into the command line and see if that fixes it

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

Essee

Eat it You Nasty Pig. wrote: »

this kind of thing is usually a DNS resolution issue; type ipconfig /flushdns into the command line and see if that fixes it

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

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?

AManFromEarth

I had an odd issue like this yesterday.

You're welcome, @Tube.

Tube

what? why have you called me here? you will pay dearly for this

oh right yeah thanks

Eat it You Nasty Pig.

Essee wrote: »

Eat it You Nasty Pig. wrote: »

this kind of thing is usually a DNS resolution issue; type ipconfig /flushdns into the command line and see if that fixes it

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

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?

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.

Orthanc

Eat it You Nasty Pig. wrote: »

Essee wrote: »

Eat it You Nasty Pig. wrote: »

this kind of thing is usually a DNS resolution issue; type ipconfig /flushdns into the command line and see if that fixes it

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

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?

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.

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.

Effef

if you are on a college campus their packet shaping or web filtering software might have something to do with it

bluecoat packetshaper does not like to deal with https connections

Penguin_Otaku

We're on our own wifi from Cox here. Haven't had issues until we moved here.

Not on a college network.

DNS flushing isn't doing it