Connection Error From Notification Server Loading Error Pidgin
years ago Closed 7 years ago #9905 closed defect (cantfix) MSN: Connection error from Notification server: Unable to connect Reported by: lstanyer Owned by: khc Milestone: Component: MSN Version: 2.5.8 Keywords: Unable connect Cc: mooseman Description (last modified by lstanyer) Two different computers running Ubuntu 9.04. Both with the same problem. Pidgin 2.5.8 MSN account exhibiting this message: Connection error from Notification server: Unable to connect. MSN is working on a computer with XP via Live Messenger. Yahoo OK under Pidgin. Oldest first Newest first Threaded Comments only Change History (9) comment:1 Changed 7 years ago by lstanyer Description modified (diff) comment:2 in reply to: ↑ description Changed 7 years ago by spedersen Replying to lstanyer: Two different computers running Ubuntu 9.04. Both with the same problem. Pidgin 2.5.8 MSN account exhibiting this message: Connection error from Notification server: Unable to connect. MSN is working on a computer with XP via Live Messenger. Yahoo OK under Pidgin. Same on Windows Vista Business SP1, a connection error occurs: (06:43:12) proxy: Connecting to messenger.hotmail.com:1863. (06:43:12) proxy: Error connecting to messenger.hotmail.com:1863 (Connection timed out.). (06:43:12) proxy: Connection attempt failed: Connection timed out. (06:43:12) msn: Connection error: Connection timed out. (06:43:12) msn: Connection error from Notification server (messenger.hotmail.com): Unable to connect comment:3 Changed 7 years ago by Meetshield We have two different computers both running 2.5.8 here that are unable to connect to MSN. Yahoo and Gmail are working fine. MSN messenger on the same machine connects to the service fine, but Pidgin says "connection error from notification server: Unable to connect" Some update from the developers on this would be useful. comment:4 Changed 7 years ago by khc this means that you cannot connect to that domain, are you behind some firewall that requires you to use a proxy? co
months ago Closed 9 months ago #16489 closed defect (duplicate) MSN connection problem Reported by: scottbrod Owned by: QuLogic Milestone: Component: MSN Version: 2.10.11 Keywords: Cc: novasource, McCabre1 Description For the last few days I can't use my Hotmail account with MSN. I keep getting : Connection error from Notification server: Connection refused. I just tried with the msn messenger and trillian and they both work fine from my PC. Any suggestions on how to resolve this I have 2.10.11 I am running on a WIN7 machine, and this has work for a long time until a few days ago. My settings are standard Server is : messenger.hotmail.com Port is 1863 Http https://developer.pidgin.im/ticket/9905 Method is unchecked the next three checkboxes are all checked Proxy is use global proxy Settings Oldest first Newest first Threaded Comments only Change History (18) comment:1 Changed 22 months ago by QuLogic Status changed from new to pending You need to turn on the HTTP Method. http://ismsndeadyet.com/ comment:2 Changed 22 months ago by scottbrod Status changed from pending to new That worked, but I have never https://developer.pidgin.im/ticket/16489 needed that before, what changed? comment:3 Changed 22 months ago by Robby Did you visit the page QuLogic linked to? comment:4 Changed 22 months ago by scottbrod Thanks, The HTTP method worked and thanks to QuLogic for the input comment:5 Changed 22 months ago by novasource This need to be set by default for MSN or added to the UI's error message. comment:6 Changed 22 months ago by scottbrod changing to the http method worked for a while, I am not getting the same issue with the HTTP options checked... any suggestions? Trillian and Messenger are working fine comment:7 Changed 22 months ago by snelson I'm having the same issue too. Going to http://ismsndeadyet.com/ suggests picking a random IP to connect to but I've tried a handful and it's the same thing. Is MSN support going to be completely dead for Pidgin? comment:8 Changed 22 months ago by McCabre1 The current issue with Pigdin and MSN should be surrounding the fact that Microsoft has disabled HTTP Method and now requires HTTPS Method (TLS on 443). From my understanding and research of the problem pigdin simply should be required to be told to connect securely when the (http method
dugan Member From: Canada Registered: 2006-05-10 Posts: 8 Website Unable to connect to Windows Live Strange problem on my fully upgraded Arch system. Seems I'm able to connect to every website except https://bbs.archlinux.org/viewtopic.php?id=105884 Windows Live.I can load live.com and see the login form. Attempting to https://ubuntuforums.org/archive/index.php/t-885507.html submit the form (in Chrome) results in a timeout, followed by the error message:"Error 101 (net::ERR_CONNECTION_RESET): Unknown error."I can log into to the live.com website from other computers in my house, so there's nothing wrong with my ISP.Attempting to connect to msn in pidgin results in a long wait, followed by: connection error "Connection error from Notification server: reading error".Here are the relevant sections from my pidgin -d output:(00:34:46) util: Writing file /home/dugan/.purple/prefs.xml (00:35:23) soap: read: Connection reset by peer (00:35:23) soap: Received secure request. (00:35:28) msn: servconn 000 read error, len: 0, errno: 11, error: Resource temporarily unavailable (00:35:28) msn: Connection error from Notification server (64.4.61.86): Reading error (00:35:28) connection: Connection error on 0x19aca00 (reason: 0 connection error from description: Connection error from Notification server: Reading error) (00:35:28) account: Disconnecting account [REDACTED] (0x1535640) (00:35:28) connection: Disconnecting connection 0x19aca00 (00:35:28) msn: destroy the OIM 0x19b01a0 (00:35:28) msn: destroy httpconn (0x19b0e90) (00:35:28) connection: Destroying connection 0x19aca00 (00:35:34) util: Writing file accounts.xml to directory /home/dugan/.purpleMy Pidgin msn connection settings are all at defaults: server: messenger.hotmail.com; port: 1863; use HTTP method: no; http method server: gateway.messenger.hotmail.com; Proxy type: Use Global Proxy Settings.On my Slackware box, in the same room of my house, Pidgin has the exact same settings and has no trouble connecting to msn.This problem has persisted at least since yesterday (when I noticed it).What's going on?BTW, I should mention that I had successfully used pidgin on Arch Linux just a week ago, with a 2.6.33.7 kernel and a TL-WN321G wifi dongle. Here is photographic proof. Now I have a 2.6.35-ARCH kernel and a TP-Link TL-WN722N, and live.com is not working. Last edited by dugan (2010-10-02 08:00:17) Offline #2 2010-10-21 03:41:47 bsdson.tw Member From: Taiwan Registered: 2005-05-06 Posts: 161 Re: Unable to connect to Windows Live I have the same issue.can not connect to MSN since last upgrade on yesterday.have
2008, 11:30 AMHi there. I've recently come back to Ubuntu and installed 8.04. However, I cannot connect to MSN on any client I have tried; aMSN, Kopete, Mercury nor Pidgin. I have no software firewall and I just have a basic Netgear router. This problem has been occurring for over a week and so I do not think it is a problem with the MSN servers. The errors I'm getting refer to not being able to connect to messenger.hotmail.com:1863 I can connect to webmessenger.msn.com and I'm at a loss of what to do to fix this problem. The Pidgin error log is as follows: Pidgin Debug Log : Sun 10 Aug 2008 11:29:32 BST (11:29:21) account: Connecting to account james@*********.net (11:29:21) connection: Connecting. gc = 0x8670f50 (11:29:21) msn: new httpconn (0x8672af0) (11:29:21) dns: DNS query for 'messenger.hotmail.com' queued (11:29:21) util: requested to fetch (http://192.168.0.1:49153/gateway.xml), full=1, user_agent=((null)), http11=1 (11:29:21) dns: DNS query for '192.168.0.1' queued (11:29:21) Session Management: Received first save_yourself (11:29:21) dns: Created new DNS child 10903, there are now 1 children. (11:29:21) dns: Successfully sent DNS request to child 10903 (11:29:21) Session Management: Received save_complete (11:29:21) dns: Created new DNS child 10904, there are now 2 children. (11:29:21) dns: Successfully sent DNS request to child 10904 (11:29:21) dns: Got response for '192.168.0.1' (11:29:21) dnsquery: IP resolved for 192.168.0.1 (11:29:21) proxy: Attempting connection to 192.168.0.1 (11:29:21) proxy: Connecting to 192.168.0.1:49153 with no proxy (11:29:21) proxy: Connection in progress (11:29:21) proxy: Connected to 192.168.0.1:49153. (11:29:21) util: Request: 'GET /gateway.xml HTTP/1.1 Connection: close Host: 192.168.0.1:49153 ' (11:29:21) docklet: embedded (11:29:21) prefs: /pidgin/blist/width changed, scheduling save. (11:29:21) prefs: /pidgin/blist/height changed, scheduling save. (11:29:21) util: Response headers: 'HTTP/1.1 200 OK CONTENT-LENGTH: 3124 CONTENT-TYPE: text/xml DATE: Sun, 10 Aug 2008 10:29:24 GMT LAST-MODIFIED: Sat, 01 Jan 2000 00:00:31 GMT SERVER: Linux/2.6.8.1, UPnP/1.0, Intel SDK for UPnP devices /1.2 CONNECTION: close ' (11:29:21) util: parsed 3124 (11:29:21) prefs: /pidgin/blist/width changed, scheduling save. (11:29:21) prefs: /pidgin/blist/height changed, scheduling save. (11:29:21) util: requested to fetch (http://192.168.0.1:49152/up