Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have webmin running on centos on port 307, I can access it locally and I verified it by trying wget localhost:307

However, I cannot it access it remotely, I have even tried to disable the firewall by running /etc/init.d/iptables stop (I am a newbie and as far as I understood iptables represent the firewall), still I cannot access the webmin interface remotely (through the browser).

I receive the following message: "Oops! Google Chrome could not connect to xxx.xxx.xxx.xxx"

How can I trace the cause of this problem any better? How can I see what is exactly blocking the connection to xxx.xxx.xxx.xxx:307 ?

Your help is very much appreciated

Update:

1- Google Chrome just says "Oops! Google Chrome could not connect to xxx.xxx.xxx.xxx:307 with no error code.

2- netstat -ntlp | grep 307 returns the following

tcp 0 0 0.0.0.0:307 0.0.0.0:* LISTEN 27541/perl

3- tcptroute showed that xxx.xxx.xxx.xxx [closed]

4- Please see below a link for the result of iptables -nvL (couldn't attach)

http://i49.tinypic.com/346l53n.png

Thanks!

share|improve this question
1  
Look at the page Chrome presented. At the bottom is an error message with a code. Paste it here. –  Michael Hampton Sep 12 '12 at 22:41

2 Answers 2

  • Check with netstat -ntlp | grep 307 that webmin is listening on the external interface as well (not only on localhost).
  • Check with tcptraceroute -n SERVER 307 to find out if something en route blocks the connection (replace SERVER with the FQDN or IP address of your server).
  • Check your iptables rules with iptables -nvL.
share|improve this answer
    
I have updated my question with answers to your questions. –  perpetual_dream Sep 13 '12 at 16:28
    
Is xxx.xxx.xxx.xxx the external address of the host running webmin? Your filter table has only ACCEPT rules, so that shouldn't be a problem, but check the nat and mangle tables as well (iptables -t nat -nvL and iptables -t mangle -nvL), to make sure that there's nothing fancy happening there. –  Ansgar Wiechers Sep 13 '12 at 17:25
    
this i50.tinypic.com/6sv248.png contains the results of the commands. I don't think that there is anything fancy going on there... what else could it be? –  perpetual_dream Sep 14 '12 at 4:48
    
By the end, this proved to be a result of a hardware firewall. –  perpetual_dream Sep 16 '12 at 19:41

Chrome is a bit funny with IP addresses in the address bar. Try it with the full URL specified, i.e. http://198.51.100.95:307/

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.