Home

web interface times out.

Submitted by johnsamuel on Sat, 2007-07-21 20:26

Hi all

Wondering if anyone can help.

I've downloaded linux installer from the process one site and have installed this on Centos VPS account. I've been through the install process via command line.

I am able to start and stop and restart ejabberd service without any errors via a shh. I'm even able execute the "ejabberdctl" command but cannot actually access the webadmin interface. I've tried a few combinations.

http://example.com:5280/admin
http://ipaddress:5280/admin

I tried telneting to these ports but it doesn't respond. Any ideas what I can try next?

John

Check what does your

Submitted by mfoss on Sun, 2007-07-22 08:13.

Check what does your ejabberd.cfg say. If it has something like this:

{hosts, ["example.org"]}.

{listen, [
  ...
  {5280, ejabberd_http,    [http_poll, web_admin]},
  ...
]
}.

Then the URL of the admin is: http://example.org:5280/admin/

Maybe you can't access the page because the port 5280 is blocked by a firewall in your server machine. Try to access this page with a browser in the own server machine (if the server does not have graphics, you can use text browsers like lynx, links or w3m).

»

Fixed

Submitted by johnsamuel on Sun, 2007-07-22 08:32.

Jabber newbie

Thanks Badlop for the response. You are right I emailed the hosting company yesterday guessing on a hunch they were blocking the port. I got a response that they were was infact blocking this port.

I changed the port for an open one and I can access the admin console now. Its a work around, but I'm not if I'm creating a rod for my own back.

I haven't been able to register any users yet so I'm gonna assume other ports for XMPP coms are being blocked too. Would the hosting company have any justification in blocking these ports or am I going to have create more work arounds?

regards

John

»

Try using SSH Tunneling

Submitted by mfoss on Mon, 2007-07-23 08:19.
johnsamuel wrote:

I changed the port for an open one and I can access the admin console now. Its a work around, but I'm not if I'm creating a rod for my own back.

Another solution is to put it back in the old port, and use SSH Tunneling to access that port from your home computer. For example, if your server machine is machine1, and your home machine is machine2, and the port you want to access is 5280, and you are in machine2 with a web browser:

  1. Execute in machine2:
    ssh machine1 -L 5280:machine1:5280
  2. This SSH connection does not only allow you to execute commands in machine1, it also created a tunnel, let's see how to traverse that tunnel.
  3. In machine2, open in your web browser this page: http://localhost:5280/admin
  4. If everything works ok, SSH will send this request to machine1, ejabberd will serve it, SSH will send back the response, and your browser will show it to you. Note that to login in the webinterface you need to put the Jabber account and password of an existing Jabber account with admin privileges.
johnsamuel wrote:

I'm gonna assume other ports for XMPP coms are being blocked too. Would the hosting company have any justification in blocking these ports or am I going to have create more work arounds?

The hosters probably block for security reasons all the ports that you don't explicitly request to be open.

A Jabber server requires port 5222 for client connections and 5269 for server connections, they are standard, and defined in XMPP RFCs. If your hoster allows you to install servers, they probably will open those two ports if you request it.

All the other ports used by ejabberd (5280, 5223,...) aren't standard nowadays, and there is no need to open them to Internet. Using SSH Tunneling, you can access 5280 without opening it to Internet.

»
Syndicate content

User login