powered by Jive Software

Inband registration HTTP 500

use the code at https://github.com/fritzy/SleekXMPP/blob/develop/examples/register_account.py to and run “python register_account.py -d” within the same machine running the Openfire 3.8.1 to perform inband registration. However, I get HTTP 500 error. The following is the error message:

Username: foo

Password:

DEBUG Loaded Plugin: RFC 6120: Stream Feature: STARTTLS

DEBUG Loaded Plugin: RFC 6120: Stream Feature: Resource Binding

DEBUG Loaded Plugin: RFC 3920: Stream Feature: Start Session

DEBUG Loaded Plugin: RFC 6121: Stream Feature: Roster Versioning

DEBUG Loaded Plugin: RFC 6121: Stream Feature: Subscription Pre-Approval

DEBUG Loaded Plugin: RFC 6120: Stream Feature: SASL

DEBUG Connecting to 127.0.0.1:5222

DEBUG ==== TRANSITION disconnected -> connected

DEBUG Starting HANDLER THREAD

DEBUG Loading event runner

DEBUG SEND (IMMED): <stream:stream to=‘foo’ xmlns:stream=’

http://etherx.jabber.org/streams’ xmlns=‘jabber:client’ xml:lang=‘en’

version=‘1.0’>

DEBUG RECV: <stream:stream version=“1.0” from=“mymachine” id=“d6e842a5”

xml:lang=“en”>

DEBUG RECV: <stream:features

xmlns="http://etherx.jabber.org/streams"><starttls

xmlns=“urn:ietf:params:xml:ns:xmpp-tls” /><mechanisms

xmlns=“urn:ietf:params:xml:ns:xmpp-sasl”>DIGEST-MD5PLAINANONYMOUSCRAM-MD5</mech a nism><compression

xmlns="zlibhttp://jabber.org/features/compress">zlib<aut h

xmlns=“http://jabber.org/features/iq-auth” /><register xmlns="

http://jabber.org/features/iq-register" /></stream:features>

DEBUG SEND (IMMED):

DEBUG RECV:

DEBUG Starting TLS

INFO Negotiating TLS

INFO Using SSL version: 3

DEBUG CERT: -----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----

WARNING Could not find pyasn1 and pyasn1_modules. SSL certificate COULD

NOT BE VERIFIED.

DEBUG SEND (IMMED): <stream:stream to=‘foo’ xmlns:stream=’

http://etherx.jabber.org/streams’ xmlns=‘jabber:client’ xml:lang=‘en’

version=‘1.0’>

DEBUG RECV: <stream:stream version=“1.0” from=“mymachine” id=“d6e842a5”

xml:lang=“en”>

DEBUG RECV: <stream:features

xmlns="http://etherx.jabber.org/streams"><mechanisms

xmlns=“urn:ietf:params:xml:ns:xmpp-sasl”>DIGEST-MD5PLAINANONYMOUSCRAM-MD5</mech a nism><compression

xmlns="zlibhttp://jabber.org/features/compress">zlib<aut h

xmlns=“http://jabber.org/features/iq-auth” /><register xmlns="

http://jabber.org/features/iq-register" /></stream:features>

DEBUG SEND (IMMED): <iq type=“set”

id=“948a4570-b5cb-440f-a06f-e2e43cb973f0-1”><query

xmlns=“jabber:iq:register”>bar

DEBUG SEND (IMMED): <auth xmlns=“urn:ietf:params:xml:ns:xmpp-sasl”

mechanism=“ANONYMOUS”>QW5vbnltb3VzLCBTdWVsdGE=

DEBUG RECV: <iq to=“mymachine/d6e842a5” type=“error”

id=“948a4570-b5cb-440f-a06f-e2e43cb973f0-1”><query

xmlns=“jabber:iq:register”>bar<error

code=“500” type=“wait”><internal-server-error

xmlns=“urn:ietf:params:xml:ns:xmpp-stanzas” />

ERROR internal-server-error

DEBUG SEND (IMMED): </stream:stream>

INFO Waiting for </stream:stream> from server

DEBUG Waiting for 3 threads to exit.

DEBUG Stopped event runner thread. 2 threads remain.

DEBUG Quitting Scheduler thread

DEBUG Stopped scheduler thread. 1 threads remain.

DEBUG Stopped send thread. 0 threads remain.

DEBUG ==== TRANSITION connected -> disconnected

ERROR Error reading from XML stream.

Done

It says the server response HTTP 500 error. Is there anything I need to

configure at Openfire? I have enabled inband account registration via

Server->Server Settings->Registration & Login->Inband Account

Registration->Enabled.

Is there anything in the Openfire logs from the time you tried the registration?

Where can I find the logs?

In the ‘logs’ directory within your Openfire installation directory.

It seems there is nothing related to the registration in the logs.

In stdoutt.log, there is only one line “Server halted”.

In stdoutt.log, there are two lines:

Admin console listening at:

http://mymachine:9090

https://mymachine:9091

What should I do to get the inband registration related logs?

If there was an error/exception, I’d expect it in error.log (or warn.log). You could enable debug logging and look in debug.log after you rerun the registration.

Do you mean to enable the Debug log via Server-> Server Manager -> Logs -> Log Viewer -> Debug -> Debug Log -> Enabled in the admin console?

I enable it and perform inband registration again. However, I still do not see the related logs.