Webmin not opeing

SYSTEM INFORMATION
OS type and version Ubuntu 20
Webmin version 2.001
i am not able to open webmin on 10000 port , but usermin is working on 20000
even server is listing on 10000 port , no any error log as well

Thanks in advance

What does following command return?

service webmin status

webmin.service - Webmin server daemon
Loaded: loaded (/lib/systemd/system/webmin.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2023-03-04 16:36:51 IST; 5h 10min ago
Process: 6287 ExecStart=/usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf (code=exited, status=0/SUCCESS)
Process: 31545 ExecReload=/usr/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Main PID: 6302 (perl)
Tasks: 2 (limit: 4609)
Memory: 1.6G
CGroup: /system.slice/webmin.service
├─6302 /usr/bin/perl /usr/share/webmin/miniserv.pl --nofork /etc/webmin/miniserv.conf
└─9190 gpg-agent --homedir /root/.gnupg --use-standard-socket --daemon

Mar 04 21:47:29 webt1.nehainfonet.com su[33846]: pam_unix(su:session): session closed for user dashboard
Mar 04 21:47:29 webt1.nehainfonet.com su[33870]: (to api) root on none
Mar 04 21:47:29 webt1.nehainfonet.com su[33870]: pam_unix(su:session): session opened for user api by (uid=0)
Mar 04 21:47:30 webt1.nehainfonet.com su[33870]: pam_unix(su:session): session closed for user api
Mar 04 21:47:30 webt1.nehainfonet.com su[33880]: (to email) root on none
Mar 04 21:47:30 webt1.nehainfonet.com su[33880]: pam_unix(su:session): session opened for user email by (uid=0)
Mar 04 21:47:30 webt1.nehainfonet.com su[33880]: pam_unix(su:session): session closed for user email
Mar 04 21:47:31 webt1.nehainfonet.com su[33895]: (to rsinfra) root on none
Mar 04 21:47:31 webt1.nehainfonet.com su[33895]: pam_unix(su:session): session opened for user rsinfra by (uid=0)
Mar 04 21:47:31 webt1.nehainfonet.com su[33895]: pam_unix(su:session): session closed for user rsinfra

Okay, webmin is running. But port 10000 is closed for public traffic.

  • Check if webmin is configure to run on a different port than 10000

  • Check if your firewall is blocking port 10000

  • Check if your VPS provider has a firewall

Try restarting webmin with following command,
service webmin restart

i suspect firewall is blocking port 10000
can you please help me to find out
From VPS side all ports are opened

Try,

ufw status verbose

dhiraj@webt1:~$ ufw status verbose

Command ‘ufw’ not found, but can be installed with:

sudo snap install ufw # version 0.36.2, or
sudo apt install ufw # version 0.36-6ubuntu1

See ‘snap info ufw’ for additional versions.

dhiraj@webt1:~$ sudo firewall-cmd --state
running
dhiraj@webt1:~$

sudo firewall-cmd --list-all
public
target: default
icmp-block-inversion: no
interfaces:
sources:
services: dhcpv6-client dns dns-over-tls ftp http https imap imaps mdns pop3 pop3s smtp smtp-submission smtps ssh
ports: 20/tcp 2222/tcp 10000-10100/tcp 20000/tcp 10000/tcp
protocols:
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:

Try stopping firewalld temporarily. And see if you can access Webmin. Port 10000 is repeated here.

stopped firewalld temporarily, but no luck
even i am not able to tlenet 10000 port from outside
i can telnet on 10000 port locally

Run ‘sudo netstat -ntlp’ and see if it’s listening at all. (If it says no such command found you need to intall the net tools with ‘sudo apt install net-tools’)

sudo netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:10023 0.0.0.0:* LISTEN 1089/postgrey --pid
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1012/mysqld
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 1971/master
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 818/dovecot
tcp 0 0 127.0.0.1:783 0.0.0.0:* LISTEN 1192/perl
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 818/dovecot
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 6302/perl
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 1971/master
tcp 0 0 103.159.152.126:53 0.0.0.0:* LISTEN 792/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 792/named
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 782/systemd-resolve
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 892/sshd: /usr/sbin
tcp 0 0 127.0.0.1:11000 0.0.0.0:* LISTEN 1429/lookup-domain-
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 1971/master
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 792/named
tcp 0 0 0.0.0.0:20000 0.0.0.0:* LISTEN 1020/perl
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 818/dovecot
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 818/dovecot
tcp6 0 0 :::587 :::* LISTEN 1971/master
tcp6 0 0 :::2222 :::* LISTEN 996/proftpd: (accep
tcp6 0 0 :::110 :::* LISTEN 818/dovecot
tcp6 0 0 ::1:783 :::* LISTEN 1192/perl
tcp6 0 0 :::143 :::* LISTEN 818/dovecot
tcp6 0 0 :::10000 :::* LISTEN 6302/perl
tcp6 0 0 :::80 :::* LISTEN 1058/apache2
tcp6 0 0 :::465 :::* LISTEN 1971/master
tcp6 0 0 :::21 :::* LISTEN 996/proftpd: (accep
tcp6 0 0 fe80::2871:34ff:fece:53 :::* LISTEN 792/named
tcp6 0 0 ::1:53 :::* LISTEN 792/named
tcp6 0 0 :::22 :::* LISTEN 892/sshd: /usr/sbin
tcp6 0 0 :::25 :::* LISTEN 1971/master
tcp6 0 0 :::443 :::* LISTEN 1058/apache2
tcp6 0 0 :::993 :::* LISTEN 818/dovecot
tcp6 0 0 :::995 :::* LISTEN 818/dovecot
dhiraj@webt1:~$

Are you hosted someplace with a firewall?

Are you hosting yourself or somewhere else?

You’re setup is using IPv6 and some providers don’t support it.

Notice your port 20000 is on regular TCP? It works.

So that’s the issue - I’m betting your provider doesn’t support IPv6 and that’s why it’s not working.

try this to check open ports

His port is open. It clearly shows that in his report he ran right before you posted. It’s even highlighted.

But his port 10000 that doesn’t work is on IPv6 while his 20000 port that works is on regular TCP. That’s the problem.

i see
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 6302/perl
is that not webmin listing on ipv4 ?

As usual, you miss the point.

He doesn’t have port 20000 listed on IPv6 and it works just fine. He only has that listed on 10000. That’s why 10000 isn’t working - there’s a conflict there for some reason that needs to get sorted.


10000 is working on ipv4 and v6 as well
i am thinking to change port and test

Again, that’s my entire point. You have port 10000 on IPv4 and IPv6 and it’s not working properly.

On the other hand, you have port 20000 on IPv4 only and it works.

I would disable IPv6 and see if port 10000 starts working. If it does work with IPv6 disabled, then you know that’s the issue.