Ejabberd: ERR_EMPTY_RESPONSE instead of admin panel

Created on 26 Jun 2016  路  4Comments  路  Source: processone/ejabberd

What version of ejabberd are you using?

ejabberd 16.01

What operating system (version) are you using?

Ubuntu 16.04

How did you install ejabberd (source, package, distribution)?

package
(apt-get install ejabberd)

What did not work as expected?

admin panel mywebsite.com:5280/admin sends ERR_EMPTY_RESPONSE

Are there error messages in the log?

crash.log and error.log are empty

ejabberd.log - have only infos, no error/warnings

...
2016-06-26 06:41:51.579 [info] <0.489.0>@ejabberd_listener:listen_tcp:189 Reusing listening port for {5222,{0,0,0,0,0,0,0,0},tcp}
2016-06-26 06:41:51.579 [info] <0.490.0>@ejabberd_listener:listen_tcp:189 Reusing listening port for {5269,{0,0,0,0,0,0,0,0},tcp}
2016-06-26 06:41:51.579 [info] <0.492.0>@ejabberd_listener:listen_tcp:189 Reusing listening port for {5280,{0,0,0,0,0,0,0,0},tcp}
2016-06-26 06:41:51.579 [info] <0.37.0>@ejabberd_app:start:76 ejabberd 16.01 is started in the node ejabberd@ubuntu
2016-06-26 06:41:51.579 [info] <0.7.0> Application ejabberd started on node ejabberd@ubuntu
...

What was the unexpected behavior?

ERR_EMPTY_RESPONSE on mywebsite.com:5280/admin

What was the expected result?

Admin panel on mywebsite.com:5280/admin

Most helpful comment

@mremond great thanks and sorry for my inattention.

I was connecting through http, when in config:

tls: true

So when i connected through https everything start working fine.

All 4 comments

What does the log show in debug mode ? Are you actually seeing that your browser is connecting to ejabberd ?

@mremond great thanks and sorry for my inattention.

I was connecting through http, when in config:

tls: true

So when i connected through https everything start working fine.

@mremond great thanks and sorry for my inattention.

I was connecting through http, when in config:

tls: true

So when i connected through https everything start working fine.

Useful information.

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings