Problem connecting to archipel UI

[silenceti]

HI,

I've installed ejabberd and archipel in centos 7, but when I try the login, i've the following error:

WebSocket connection to 'ws://archipel.local.domain:5280/xmpp' failed: Error during WebSocket handshake: Unexpected response code: 404

What can I do?

[root@archipel bin]# ./ejabberdctl status The node ejabberd@localhost is started with status: started ejabberd 15.04 is running in that node

Thanks.

[CyrilPeponnet]

Use the ejabberd yaml configuration file provided in the wiki.

On Jun 22, 2015, at 7:54 AM, silenceti notifications@github.com wrote:

HI,

I've installed ejabberd and archipel in centos 7, but when I try the login, i've the following error:

WebSocket connection to 'ws://archipel.local.domain:5280/xmpp' failed: Error during WebSocket handshake: Unexpected response code: 404

What can I do?

[root@archipel bin]# ./ejabberdctl status The node ejabberd@localhost is started with status: started ejabberd 15.04 is running in that node

Thanks.

— Reply to this email directly or view it on GitHub.

[silenceti]

I've used...this is my ejabberd.yml:

http://pastebin.com/itju3d1T

[CyrilPeponnet]

Can you reach archipel.local.domain:5280/ from your browser?

[CyrilPeponnet]

And use the yaml as provided

[silenceti]

404 Not Found

I guess this is the problem?

[CyrilPeponnet]

Yep, make sure your fqdn xmpp server is reachable from the machine displaying the UI (in the browser).

On Jun 22, 2015, at 8:28 AM, silenceti notifications@github.com wrote:

404 Not Found

I guess this is the problem?

— Reply to this email directly or view it on GitHub https://github.com/ArchipelProject/Archipel/issues/1141#issuecomment-114154224.

[silenceti]

Well, the port is listenning: tcp 0 0 0.0.0.0:5280 0.0.0.0:* LISTEN 2120/beam.smp

And i can get to the Archipel ... so I guess is reachable, right?

[silenceti]

if I go here: http://archipel.local.domain:5280/http-bind , I get:

ejabberd mod_http_bind

An implementation of XMPP over BOSH (XEP-0206)

This web page is only informative. To use HTTP-Bind you need a Jabber/XMPP client that supports it.

[CyrilPeponnet]

Try with https://www.websocket.org/echo.html https://www.websocket.org/echo.html

If it can’t connect, you must have an issue with your ejabberd configuration.

I just tried works fine for me.

On Jun 22, 2015, at 8:47 AM, silenceti notifications@github.com wrote:

Reopened #1141 https://github.com/ArchipelProject/Archipel/issues/1141.

— Reply to this email directly or view it on GitHub https://github.com/ArchipelProject/Archipel/issues/1141#event-336854750.

[silenceti]

This browser supports WebSocket.

hum...Going to check ejabberd config

[CyrilPeponnet]

Did you do the test ?

You should get connected.

[silenceti]

Mixed Content: The page at 'https://www.websocket.org/echo.html' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://archipel.local.domain:5280/xmpp?encoding=text'. This request has been blocked; this endpoint must be available over WSS.

[silenceti]

ERROR: The ejabberd node 'ejabberd@localhost' is already running.

this is normal? Doesn't supposed to be ejabberd@local.domain ?

[silenceti]

i've copy the file from here: https://github.com/ArchipelProject/Archipel/wiki/Ejabberd:-Configuration and it seems to be working :)

thanks CyrilPeponnet for your help!

[itguy51]

I hate to re-visit this issue, but I have run into the same troubles with a websocket connection 404ing, however, I am using the configuration file provided by the setup instructions. I attempted a WebSocket echo test, and it was unable to connect. I am able to log into the WebUI of ejabberd.