Connection refused: example.com:10000

Kutakizukari · December 3, 2014, 8:37pm

I installed on Ubuntu 14.04 LTS and set a root password using “/usr/{share,libexec}/webmin/changepass.pl /etc/webmin root XYZ” because of using keys.

I go to http://example.com:10000 it says “Connection refused: example.com:10000”

The FQDN I used was ns1.example.com. If I try ns1.example.com:10000 is says “Your request for http://ns1.example.com:10000/ could not be fulfilled, because the domain name ns1.example.com could not be resolved.”

hostname -f returns “ns1.example.com”.

Eric · December 3, 2014, 9:24pm

Howdy,

Hmm, is it possible that Webmin isn’t running?

You may want to try running this command to restart it:

/etc/init.d/webmin restart

Are you able to access it after that?

-Eric

Kutakizukari · December 4, 2014, 3:52am

I just tried “/etc/init.d/webmin restart” but get the same error.

Eric · December 4, 2014, 4:29am

Howdy,

Hmm, do you perhaps have a firewall running on your server that’s blocking incoming connections?

You can view the firewall rules with the following command:

iptables -L -n

Kutakizukari · December 5, 2014, 1:22am

iptables -L -n

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
fail2ban-ssh  tcp  --  0.0.0.0/0            0.0.0.0/0            multiport dport                                                                                                                               s 22
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

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain fail2ban-ssh (1 references)
target     prot opt source               destination
RETURN     all  --  0.0.0.0/0            0.0.0.0/0

Eric · December 5, 2014, 1:26am

Hmm, the firewall rules there look like they may be blocking a lot of stuff.

Could you try disabling your firewall, and then attempt accessing Virtualmin again?

-Eric

Kutakizukari · December 5, 2014, 3:19am

Did “ufw disable”, still same message.

Eric · December 5, 2014, 6:32am

How does the “iptables -L -n” look now? When the firewall is disabled, all the rules there should be gone.

-Eric

Kutakizukari · December 6, 2014, 2:28am


Chain INPUT (policy ACCEPT)
target     prot opt source               destination
fail2ban-ssh  tcp  --  0.0.0.0/0            0.0.0.0/0            multiport dports 22
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
ufw-before-logging-input  all  --  0.0.0.0/0            0.0.0.0/0
ufw-before-input  all  --  0.0.0.0/0            0.0.0.0/0
ufw-after-input  all  --  0.0.0.0/0            0.0.0.0/0
ufw-after-logging-input  all  --  0.0.0.0/0            0.0.0.0/0
ufw-reject-input  all  --  0.0.0.0/0            0.0.0.0/0
ufw-track-input  all  --  0.0.0.0/0            0.0.0.0/0
Chain FORWARD (policy ACCEPT)

target     prot opt source               destination

ufw-before-logging-forward  all  –  0.0.0.0/0            0.0.0.0/0

ufw-before-forward  all  –  0.0.0.0/0            0.0.0.0/0

ufw-after-forward  all  –  0.0.0.0/0            0.0.0.0/0

ufw-after-logging-forward  all  –  0.0.0.0/0            0.0.0.0/0

ufw-reject-forward  all  –  0.0.0.0/0            0.0.0.0/0

ufw-track-forward  all  –  0.0.0.0/0            0.0.0.0/0
Chain OUTPUT (policy ACCEPT)

target     prot opt source               destination

ufw-before-logging-output  all  –  0.0.0.0/0            0.0.0.0/0

ufw-before-output  all  –  0.0.0.0/0            0.0.0.0/0

ufw-after-output  all  –  0.0.0.0/0            0.0.0.0/0

ufw-after-logging-output  all  –  0.0.0.0/0            0.0.0.0/0

ufw-reject-output  all  –  0.0.0.0/0            0.0.0.0/0

ufw-track-output  all  –  0.0.0.0/0            0.0.0.0/0
Chain fail2ban-ssh (1 references)

target     prot opt source               destination

RETURN     all  –  0.0.0.0/0            0.0.0.0/0
Chain ufw-after-forward (1 references)

target     prot opt source               destination
Chain ufw-after-input (1 references)

target     prot opt source               destination
Chain ufw-after-logging-forward (1 references)

target     prot opt source               destination
Chain ufw-after-logging-input (1 references)

target     prot opt source               destination
Chain ufw-after-logging-output (1 references)

target     prot opt source               destination
Chain ufw-after-output (1 references)

target     prot opt source               destination
Chain ufw-before-forward (1 references)

target     prot opt source               destination
Chain ufw-before-input (1 references)

target     prot opt source               destination
Chain ufw-before-logging-forward (1 references)

target     prot opt source               destination
Chain ufw-before-logging-input (1 references)

target     prot opt source               destination
Chain ufw-before-logging-output (1 references)

target     prot opt source               destination
Chain ufw-before-output (1 references)

target     prot opt source               destination
Chain ufw-reject-forward (1 references)

target     prot opt source               destination
Chain ufw-reject-input (1 references)

target     prot opt source               destination
Chain ufw-reject-output (1 references)

target     prot opt source               destination
Chain ufw-track-forward (1 references)

target     prot opt source               destination
Chain ufw-track-input (1 references)

target     prot opt source               destination
Chain ufw-track-output (1 references)

target     prot opt source               destination

Eric · December 6, 2014, 5:55am

Ah, you have more firewall rules setup now than you did earlier

You’d want to completely disable your firewall, along with any apps that create firewall rules.

When running “iptables -L -n”, you shouldn’t see any firewall rules.

-Eric

Kutakizukari · December 6, 2014, 8:21pm

They were there before, I didn’t see the line break the first time.

Running service iptables stop produces iptables: unrecognized service.
Running ufw disable followed by ufw status shows that it is inactive but get the same results. What command should I run to completely disable the firewall?

Eric · December 8, 2014, 4:12pm

Howdy,

Hmm, I’m not too familiar with using ufw, though reviewing the manpage, it does appear that running “ufw disable” as you did above is indeed supposed to disable the firewall, and also prevent it from starting on bootup.

You’re saying though that after running that, all those firewall rules are still active?

I see that there is a “ufw reset” option, which is supposed to take it back to the installed defaults, though based on what I read in the manpage the previous option you tried should have done the trick, in theory

-Eric

Sri · January 3, 2020, 6:30am

I face this issue occasionally.

I would do a reboot and could login but the session would break after a short time.

Today I discovered one issue that could be doing this. Webmin update was available!
So, I logged in via SSH and did the update.

And, the issue was resolved!

Earlier too, without me knowing about this, the issue was resolving because I would occasionally do a system update in SSH session. The issue would not recur until next webmin update availability.

Perhaps, webmin should update automatically.