How do I open port 9090?

I apologise if this has already been asked and answered before - I searched the forum for ages and I couldn’t find what I need to do.

Basically I have installed openfire on my server and it says it’s running. However, when I go to http:server:9090 the page times out. I checked with my hosting company and apparently port 9090 is closed.

My hosting company is not what you’d call very helpful. All they have told me is:

Port 9090 is closed, you will be able to open it yourself
For help opening / closing ports on your CentOS server.. http://wiki.centos.org/HowTos/Network/IPTables

I read it and I really don’t understand. I tried a few things and none of them worked.

I have SSH and root access.

Can someone tell me what I need to do to open port 9090 (and any others I need to open) because I really want to set up a chat service for members of my site.

Thanks in advance.

Chris

you need to access the server with either root access or ssh with root privileges and enter this command: iptables -A INPUT -p tcp --dport 9090 -j ACCEPT

Except 9090 you should open at least 5222 - 5223 TCP for your clients connection. Port 7777/TCP (file proxy) is also worth considering.

CentOS has also an TUI for configuring firewall:

system-config-securitylevel-tui

(TUI = TextUserInterface)

That’s what I found on the web too, but it’s not doing anything, as far as I can tell.

I put it in and it gives no response, just goes to the next line. And the http://server:9090 page still times out.

Does it need anything else? Server reboot after the change or anything like that?

It should just go to a new blank line. This means the command was successful. You may need to reboot the server to make the changes active. while you are adding ports though add the others mentioned by the others in this thread.

you could also try this command: service iptables restart

That will restart the firewall.

I tried service iptables restart and rebooting the server and I still cannot get to that page without a timeout error.

Is there a way to check if iptables has actually been updated?

I thought it might be in /etc/sysconfig/iptables - but nothing about 9090 has been added to there.

At this point I would go back to your hosting company. They need to provide you with the support you are paying for.

Thanks but they’re pretty useless there andI’d need to book an appointment with an engineer at $360 per hour, and the first appointment they have is next week. So I’d rather keep trying myself. Does anyone else know what I could try?

Do you have tried that TUI ?

I tried it - I got the interface up. I just wasn’t sure what to change in the settings there. Are there instructions somewhere?

at your command prompt type

iptables -L

What is the result?

also do you have any means of direct chat? It would be easier.

Chain INPUT (policy DROP)
target prot opt source destination
ACCEPT all – anywhere anywhere
ACCEPT all – anywhere anywhere state RELATED,ESTAB LISHED
ACCEPT tcp – anywhere anywhere tcp dpt:ssh state N EW
ACCEPT tcp – anywhere anywhere tcp dpt:http state NEW
ACCEPT tcp – anywhere anywhere tcp dpt:https state NEW
ACCEPT udp – anywhere anywhere udp dpt:domain stat e NEW
ACCEPT tcp – anywhere anywhere tcp dpt:domain stat e NEW
ACCEPT udp – anywhere anywhere udp dpt:tftp state NEW
ACCEPT tcp – anywhere anywhere tcp dpt:tftp state NEW
ACCEPT tcp – anywhere anywhere tcp dpt:smtp state NEW
ACCEPT tcp – anywhere anywhere tcp dpt:pop3 state NEW
ACCEPT udp – anywhere anywhere udp dpt:ntp state N EW
ACCEPT tcp – anywhere anywhere tcp dpt:ftp-data st ate NEW
ACCEPT tcp – anywhere anywhere tcp dpt:ftp state N EW
ACCEPT tcp – anywhere anywhere tcp dpt:mysql state NEW
ACCEPT udp – anywhere anywhere udp dpt:mysql state NEW
ACCEPT tcp – anywhere anywhere tcp dpt:personal-ag ent state NEW
ACCEPT tcp – anywhere anywhere tcp dpt:teradataord bms state NEW
ACCEPT tcp – anywhere anywhere tcp dpt:etlservicem gr state NEW
DROP all – anywhere anywhere

Chain FORWARD (policy DROP)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
ACCEPT all – anywhere anywhere
ACCEPT all – anywhere anywhere state NEW,RELATED,E STABLISHED

Chain RH-Firewall-1-INPUT (0 references)
target prot opt source destination
[root@localhost ~]#

Does that make any sense to you?!