#501 In-band registration not working

Reporter google@tastytea.de
Owner MattJ
Created
Updated
Stars ★ (1)  
Tags
  • Status-New
  • Priority-Medium
  • Type-Defect
  1. google@tastytea.de on

    *What steps will reproduce the problem?* 1. Try to register an account via in-band registration 3. It doesn't work 2. Pidgin: No Error, telepathy: Network error I'm using prosody 0.9.8 on Debian jessie.

    Attachments
  2. google@tastytea.de on

    I can register users via prosodyctl

  3. MattJ on

    Hi, thanks for the report. The Prosody log doesn't appear to show the client trying to register an account. Could you use Pidgin (make sure to tick 'Register new account on the server'), and paste its log from Help->Debug when you try to register? Empathy/Telepathy are not very useful for debugging, as "Network error" is generally all it says when something goes wrong.

    Changes
    • owner MattJ
  4. google@tastytea.de on

    (19:07:36) account: Registering account test123@cryptoparty-celle.de/here (19:07:36) connection: Registering. gc = 0x3403e80 (19:07:36) dnssrv: querying SRV record for cryptoparty-celle.de: _xmpp-client._tcp.cryptoparty-celle.de (19:07:36) dnssrv: found 1 SRV entries (19:07:36) dnsquery: Performing DNS lookup for cryptoparty-celle.de (19:07:36) dns: Successfully sent DNS request to child 1788 (19:07:36) dns: Got response for 'cryptoparty-celle.de' (19:07:36) dnsquery: IP resolved for cryptoparty-celle.de (19:07:36) proxy: Attempting connection to 2001:4ba0:cafe:c1e::acab (19:07:36) proxy: Connecting to cryptoparty-celle.de:5222 with no proxy (19:07:36) proxy: Connection in progress (19:07:36) proxy: Connecting to cryptoparty-celle.de:5222. (19:07:36) proxy: Connected to cryptoparty-celle.de:5222. (19:07:36) jabber: Sending (test123@cryptoparty-celle.de/here): <?xml version='1.0' ?> (19:07:36) jabber: Sending (test123@cryptoparty-celle.de/here): <stream:stream to='cryptoparty-celle.de' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'> (19:07:36) jabber: Recv (311): <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' version='1.0' from='cryptoparty-celle.de' id='5ae9408d-cc5f-49f9-9cf0-f859780c64fe' xml:lang='en' xmlns='jabber:client'><stream:features><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'><required/></starttls></stream:features> (19:07:36) jabber: Sending (test123@cryptoparty-celle.de/here): <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/> (19:07:36) jabber: Recv (50): <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/> (19:07:36) nss: SSL version 3.3 using 256-bit AES with 160-bit SHA1 MAC Server Auth: 2048-bit RSA, Key Exchange: 384-bit ECDHE, Compression: NULL Cipher Suite Name: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (19:07:36) nss: subject=CN=cryptoparty-celle.de issuer=E=support@cacert.org,CN=CA Cert Signing Authority,OU=http://www.cacert.org,O=Root CA (19:07:36) nss: subject=E=support@cacert.org,CN=CA Cert Signing Authority,OU=http://www.cacert.org,O=Root CA issuer=E=support@cacert.org,CN=CA Cert Signing Authority,OU=http://www.cacert.org,O=Root CA (19:07:36) certificate/x509/tls_cached: Starting verify for cryptoparty-celle.de (19:07:36) certificate/x509/tls_cached: Checking for cached cert... (19:07:36) certificate/x509/tls_cached: ...Found cached cert (19:07:36) nss/x509: Loading certificate from /home/tastytea/.purple/certificates/x509/tls_peers/cryptoparty-celle.de (19:07:36) certificate/x509/tls_cached: Peer cert matched cached (19:07:36) nss/x509: Exporting certificate to /home/tastytea/.purple/certificates/x509/tls_peers/cryptoparty-celle.de (19:07:36) util: Writing file /home/tastytea/.purple/certificates/x509/tls_peers/cryptoparty-celle.de (19:07:36) nss: Trusting CN=cryptoparty-celle.de (19:07:36) certificate: Successfully verified certificate for cryptoparty-celle.de (19:07:36) jabber: Sending (ssl) (test123@cryptoparty-celle.de/here): <stream:stream to='cryptoparty-celle.de' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'> (19:07:36) jabber: Recv (ssl)(367): <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' version='1.0' from='cryptoparty-celle.de' id='47a0b352-5c45-425f-9d35-7a0adaefb36f' xml:lang='en' xmlns='jabber:client'><stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>SCRAM-SHA-1</mechanism><mechanism>PLAIN</mechanism></mechanisms></stream:features> (19:07:36) jabber: Sending (ssl) (test123@cryptoparty-celle.de/here): <iq type='get' id='purplef9f428c1'><query xmlns='jabber:iq:register'/></iq> (19:07:36) jabber: Recv (ssl)(137): <iq id='purplef9f428c1' type='error'><error type='cancel'><service-unavailable xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq> (19:07:36) jabber: Unhandled IQ with id purplef9f428c1 (19:07:36) util: Writing file prefs.xml to directory /home/tastytea/.purple (19:07:36) util: Writing file /home/tastytea/.purple/prefs.xml (19:07:41) util: Writing file accounts.xml to directory /home/tastytea/.purple (19:07:41) util: Writing file /home/tastytea/.purple/accounts.xml (19:07:41) util: Writing file blist.xml to directory /home/tastytea/.purple (19:07:41) util: Writing file /home/tastytea/.purple/blist.xml I forgot to mention that in-band registration worked before. It may be that it stopped working after the last upgrade from wheezy stable to packages.prosody.im jessie

  5. google@tastytea.de on

    Any Ideas?

  6. Zash on

    I would have guessed that this was due to allow_registration = false or mod_register not being loaded. Especially since registration did not appear in the stream features.

New comment