Unable to login to virtualmin on port 10000 using IP

Unable to login to one Virtualmin server on port 10000 on ISP provided public IP from within my home network, although, I am able to log in to another Virtualmin server connected on the same ATT Modem with public IP from within home network. But all IPs are accessible on port 10000 from outside my home network though.

And on the same server in question, am able to login via SSH only sometimes!?

When checked today, Virtualmin check-config did not show any errors.

The error I get on IE Edge is

Hmm, we can't reach this page.

Try this

•Make sure you’ve got the right URL: https://IP:10000 Opera browser gives this error: The connection to IP was interrupted.
Status: 
Active

Comments

Howdy -- it sounds like you may be seeing a network issue of some kind.

It may be that the port isn't being forwarded, or some related issue is going on.

However, you may want to verify that Webmin is running and that a firewall isn't causing a problem.

What is the output of these two commands on the server you're experiencing those problems with:

netstat -an | grep :10000
iptables -L -n
bislinks's picture
Submitted by bislinks on Wed, 09/02/2015 - 22:04 Pro Licensee

[root@ns3 ~]# netstat -an | grep :10000 tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN udp 0 0 0.0.0.0:10000 0.0.0.0:* [root@ns3 ~]# iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:20 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:21 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:53 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:20000 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:10000 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:443 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:993 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:143 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:995 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:110 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:20 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:21 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:53 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:587 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:25 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:22 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT) target prot opt source destination REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT) target prot opt source destination [root@ns3 ~]#

Ah, it looks like the firewall may be blocking it.

Try disabling your firewall and seeing if you're then able access Virtualmin on port 10000.

bislinks's picture
Submitted by bislinks on Wed, 09/02/2015 - 22:18 Pro Licensee

Nope, even after disabling firewall completely.

How to disable it depends on how it was initially enabled.

However, it may be as simple as running this command:

/etc/init.d/iptables stop

bislinks's picture
Submitted by bislinks on Thu, 09/03/2015 - 08:12 Pro Licensee

Even after disabling Firewall, I am still unable to access port 10000 on browser....

bislinks's picture
Submitted by bislinks on Thu, 09/03/2015 - 08:24 Pro Licensee

Here is Firewall Page from the ATT Modem, in case it might help diagnose the problem....

bislinks's picture
Submitted by bislinks on Thu, 09/03/2015 - 08:35 Pro Licensee

Also, "packet filter" on the Modem is set to "off"

Just to be sure that the firewall is working as expected, what is the output of this command:

iptables -L -n

Also, does your setup require you to enable port forwarding from your modem/router to the server? If so, is that already setup?

bislinks's picture
Submitted by bislinks on Thu, 09/03/2015 - 14:48 Pro Licensee

[root@ns3 public_html]# iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination

Chain FORWARD (policy ACCEPT) target prot opt source destination

Chain OUTPUT (policy ACCEPT) target prot opt source destination [root@ns3 public_html]#

My Public IP Setup does not require port forwarding.

What is the output of this command on your server:

/sbin/ifconfig

bislinks's picture
Submitted by bislinks on Thu, 09/03/2015 - 14:56 Pro Licensee

[root@ns3 ~]# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:1A:4B:65:62:C7 inet addr:108.90.217.140 Bcast:108.90.217.143 Mask:255.255.255.248 inet6 addr: 2602:306:36fe:310:21a:4bff:fe65:62c7/64 Scope:Global inet6 addr: fe80::21a:4bff:fe65:62c7/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12720450 errors:0 dropped:0 overruns:0 frame:0 TX packets:10662982 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2078573381 (1.9 GiB) TX bytes:5616995586 (5.2 GiB) Interrupt:16

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:3879184 errors:0 dropped:0 overruns:0 frame:0 TX packets:3879184 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:850030371 (810.6 MiB) TX bytes:850030371 (810.6 MiB)

[root@ns3 ~]#

I seem to be able to connect to Virtualmin on that IP address.

That may mean that the problem you're seeing at the moment is on your desktop.

Do you have another PC you could try to connect from?

bislinks's picture
Submitted by bislinks on Thu, 09/03/2015 - 15:04 Pro Licensee

Tried from laptop wirelessly, no success

It could be a problem with your provider, at either end.

It's possible that the Internet provider where your PCs are is blocking outgoing port 10000.

It's also possible the provider for your server is blocking your PC's IP for some reason.

However, since it does work for both Joe and I (and we're using different ISP's at different locations), that means that Virtualmin is indeed working properly.

You may want to talk to your providers to see if they have any thoughts on what the problem there is.

bislinks's picture
Submitted by bislinks on Thu, 09/03/2015 - 15:55 Pro Licensee

Just finished chatting with ATT Tech. The solution was to enable "IP Passthrough" and leave the mode to its default, "DHCPS-Dynamic."

Thanks for your and Joe's help in solving this issue.