[95all] Jabber connectivity issues? Workaround here.
Glen <glen@amsl.com> Sat, 02 April 2016 17:53 UTC
Return-Path: <glen@amsl.com>
X-Original-To: 95all@ietfa.amsl.com
Delivered-To: 95all@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B875A12D1E8; Sat, 2 Apr 2016 10:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.211
X-Spam-Level:
X-Spam-Status: No, score=-104.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ovyj4-8mppUu; Sat, 2 Apr 2016 10:53:16 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [IPv6:2001:1900:3001:11::28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1ADE912D197; Sat, 2 Apr 2016 10:53:16 -0700 (PDT)
Received: from mail.amsl.com (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTPS id A89D11E5D6D; Sat, 2 Apr 2016 10:52:12 -0700 (PDT)
Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com [209.85.220.180]) by c8a.amsl.com (Postfix) with ESMTPSA id 7758F1E5D67; Sat, 2 Apr 2016 10:52:12 -0700 (PDT)
Received: by mail-qk0-f180.google.com with SMTP id o6so49473825qkc.2; Sat, 02 Apr 2016 10:53:15 -0700 (PDT)
X-Gm-Message-State: AD7BkJLSq0hjaQ9WUlR7nr9Dzv9lqoytsUIX2+NTwdLD5hg84ZFdvqU17dLyvvJIj3qTZnZr7wzdRfaj0ay3xw==
X-Received: by 10.55.198.23 with SMTP id b23mr24869497qkj.27.1459619595059; Sat, 02 Apr 2016 10:53:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.34.56 with HTTP; Sat, 2 Apr 2016 10:52:55 -0700 (PDT)
From: Glen <glen@amsl.com>
Date: Sat, 02 Apr 2016 10:52:55 -0700
X-Gmail-Original-Message-ID: <CABL0ig5otDaG+6Ba3NmTLeR4u0C6VNk7D9duREZUe=x=H_mEvQ@mail.gmail.com>
Message-ID: <CABL0ig5otDaG+6Ba3NmTLeR4u0C6VNk7D9duREZUe=x=H_mEvQ@mail.gmail.com>
To: ietf-announce@ietf.org, 95all@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/95all/ZrmsH2mf_3zcdL5OUTlF30YkQuc>
Subject: [95all] Jabber connectivity issues? Workaround here.
X-BeenThere: 95all@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: glen@amsl.com
List-Id: "Mailing list of all 95 attendees for official communication." <95all.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/95all>, <mailto:95all-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/95all/>
List-Post: <mailto:95all@ietf.org>
List-Help: <mailto:95all-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/95all>, <mailto:95all-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Apr 2016 17:53:17 -0000
All - We are receiving some continued reports of Jabber connectivity issues for the IETF Jabber server. Last month we upgraded the server OS, which caused many people to experience connectivity issues for a day or two. We then upgraded the ejabberd server, and that appeared to have resolved those issue for most people. However, with the meeting starting up, and more people trying to connect, it seems that some people are still having trouble. As you might guess, debugging such things is very difficult. For our purposes, Jabber is a server-to-server connection, and we (almost) never have access to the remote server which is trying to connect to us. The problem is more frustrating because, as I have discovered, the states and maintenance levels of jabber servers globally varies widely. WIDELY. So debugging these types of problems is next to impossible. So, instead, I've taken the approach of trying to bracket what DOES work. If you are having trouble connecting to the IETF jabber server conference rooms, I have compiled a list of ten public, free, open, working Jabber servers, from difference locations around the world, and included that list below. I have personally just now successfully created an account on each one of these servers using XMPP only (some have XMPP captcha prompts which are easy to pass, some don't) and then successfully used that created account to connect to the IETF jabber server. Please consider using one of these servers to help ensure that you can connect to the IETF Jabber rooms. igniterealtime.org jabber.cz jabbim.com securejabber.me wusz.org xmpp.is xmpp.js xmpp.kz xmpp.pro xmppcomm.com I apologize that some of you are still having problems, and that the nature of XMPP makes this difficult to debug... but I hope this list of (currently) working Jabber servers helps you connect successfully to the IETF meeting jabber rooms. I've never had so many jabber accounts in my life. Glen Glen Barney IT Director AMS (IETF Secretariat)