Closed Bug 825264 Opened 12 years ago Closed 11 years ago

Unable to connect to Facebook Messenger right now

Categories

(Firefox Graveyard :: SocialAPI: Providers, defect)

17 Branch
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: kleagkou, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20100101 Firefox/17.0 Iceweasel/17.0.1 Build ID: 20121201094343 Steps to reproduce: Nothing at all , I just open Iceweasel ( Debian Rebranded firefox) and I am loged on facebook Actual results: Iceweasel says notification error that cannnoct connect to facebook messenger Expected results: to show me the friends that are currently online
Severity: normal → major
Component: Untriaged → SocialAPI
There an issue on the Facebook side that is causing trouble at the moment, they're working on fixing it.
Component: SocialAPI → SocialAPI: Providers
Summary: Iceweael is unable to connect to Facebook Messenger right now → Unable to connect to Facebook Messenger right now
Status: UNCONFIRMED → NEW
Ever confirmed: true
I am experiencing the same issue on Firefox 17.0.1 in Linux. I'm logged in at Facebook but the Messenger indicates that it's not. I tried logging out and logging in, disable-enable Social API several times but nothing happened.
OS: Linux → All
Hardware: x86_64 → All
I can confirm this as well. Now I am less able to waste my life on that site. A quick fix would be nice. From either Mozilla or Facebook.
The same problem for me for the past few days. Removing/re-adding the Facebook integration and deleting cache/cookies makes no difference. I'm also getting the problem on my work PC, both Firefox 17.0.1. The home pc is Windows 8 64-Bit/Work: Windows 7 Pro SP1 32-Bit. (In reply to :Gavin Sharp (use gavin@gavinsharp.com for email) from comment #1) > There an issue on the Facebook side that is causing trouble at the moment, > they're working on fixing it. Can you post a link showing Facebook working on it please?
I'm not sure what kind of link you'd like me to paste - we're in direct contact with engineers there who are trying to address the problem. I don't have a recent update, but I know they're working on it.
Ah thanks. I didn't realise I was talking directly to the engineers/programmers. Good to hear, thanks.
It looks like it's fixed. I've been checking all night and it started working 1-2 hours ago. Hopefully Facebook have fixed it permanently.
It is woking fine for me with Firefox latest aurora
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
It's now working on Firefox 17.0.1 on Ubuntu 12.04 LTS.
Resolution: WORKSFORME → FIXED
This problem has re-occurred and has for the past few days :-(, since Firefox 18 was released.
It broke again yesterday on the latest beta. Deleted cookies and uninstalled the service. Still doesn't work.
This problem persists at least with the Aurora version I'm using (2013-08-05).
This issue is and always has been an issue on Facebook's end. Unfortunately there is not much we can do about that. I think this is going to be an issue off and on until Facebook puts more effort into ensuring up-time.
Is there a fix for this coming? It's still broken for me :-(
(In reply to alexmcc78 from comment #15) > Is there a fix for this coming? It's still broken for me :-( It's an issue on Facebook's end. I know they are aware of it but I don't know if/when they will fix it.
Thanks. It's normally fixed by now! I'm unsure how it's because of a Facebook uptime issue when it only seems to break when a new Firefox version is released. I rarely have problems until I upgrade.
We are currently working on error pages to make it clearer when the service is offline. This should hopefully alleviate this confusion.
Back to not working again.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
It's been 2 weeks now. I'm guessing Facebook/Mozilla aren't going to fix it this time? As a Firefox feature, it's in part Mozilla's responsibility to be contacting Facebook.
(In reply to alexmcc78 from comment #21) > It's been 2 weeks now. I'm guessing Facebook/Mozilla aren't going to fix it > this time? As a Firefox feature, it's in part Mozilla's responsibility to be > contacting Facebook. Facebook was made aware of this a while ago. Unfortunately there is nothing more we can do on our end.
Does this work for anyone now? In case it's a problem at my end (has happened before) or are Facebook simply not going to fix it now? It's been broken for weeks.
(In reply to alexmcc78 from comment #24) > Does this work for anyone now? I just tried and it still does not work on my end.
Thanks. I may uninstall it soon, if it's not working :-(. I've since installed the Facebook Messenger app for Windows. Which works fine but Facebook no longer offer for download (thankfully I have the executable). It's not half as useful though, the way the Facebook Messenger for Firefox works across tabs is so handy.
Mine just reconnected moments ago and it seems to be working again
(In reply to AJ Fite from comment #27) > Mine just reconnected moments ago and it seems to be working again I can't confirm on Firefox 26.0.
Is it still working for you? On Firefox 26.0 it's still no different for me. Facebook Chat still isn't connecting. I removed Facebook Messenger for Firefox, deleted all cookies related to Facebook, restarted and reinstalled Facebook Messenger for Firefox. No joy.
It was working for about 15 minutes right around when I posted that comment, then ceased functioning again. It was a glorious 15 minutes. Firefox 28.0a2 (Ubuntu PPA Version) on Ubuntu Trusty 14.04 64bit
I'd given up hope and remarkably it started working again for me a couple of days ago. It hasn't work since the 24th of November! The three notification buttons still don't work (it never loads friend request/message/notifications) but it's the Chat Sidebar I care about and finally it's working. For now!
This bug should be closed as the Facebook Messenger extension has been discontinued
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → WONTFIX
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.