After dist-upgrading to Debian 12 Bookworm, Webmin version 2.101 is not starting anymore.
Error messages:
Jaap@chanchala:~$ sudo webmin -v
**2.101**
jaap@chanchala:~$ sudo systemctl stop webmin
jaap@chanchala:~$ sudo systemctl restart webmin
Job for webmin.service failed because the control process exited with error code.
See "systemctl status webmin.service" and "journalctl -xeu webmin.service" for details.
jaap@chanchala:~$ sudo systemctl status webmin
● webmin.service - Webmin server daemon
Loaded: loaded (/lib/systemd/system/webmin.service; disabled; preset: enabled)
Active: activating (start) since Sun 2023-08-13 16:45:34 UTC; 2s ago
Cntrl PID: 3894 (miniserv.pl)
Tasks: 1 (limit: 1108)
Memory: 9.4M
CPU: 130ms
CGroup: /system.slice/webmin.service
└─3894 /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf
Aug 13 16:45:34 chanchala systemd[1]: Stopped webmin.service - Webmin server daemon.
Aug 13 16:45:34 chanchala systemd[1]: Starting webmin.service - Webmin server daemon...
Aug 13 16:45:34 chanchala perl[3894]: pam_unix(webmin:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root
jaap@chanchala:~$ sudo journalctl -xeu webmin.service
░░ the configured Restart= setting for the unit.
Aug 13 16:46:09 chanchala systemd[1]: Stopped webmin.service - Webmin server daemon.
░░ Subject: A stop job for unit webmin.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ A stop job for unit webmin.service has finished.
░░ The job identifier is 16322 and the job result is done.
Aug 13 16:46:09 chanchala systemd[1]: Starting webmin.service - Webmin server daemon...
░░ Subject: A start job for unit webmin.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ A start job for unit webmin.service has begun execution.
░░ The job identifier is 16322.
Aug 13 16:46:10 chanchala perl[3958]: pam_unix(webmin:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= user=root
Aug 13 16:46:12 chanchala webmin[3958]: Webmin starting
Aug 13 16:46:12 chanchala miniserv.pl[3958]: Undefined address for Socket::pack_sockaddr_in at /usr/share/webmin/miniserv.pl line 497.
Aug 13 16:46:12 chanchala systemd[1]: webmin.service: Control process exited, code=exited, status=29/n/a
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ An ExecStart= process belonging to unit webmin.service has exited.
░░ The process' exit code is 'exited' and its exit status is 29.
Aug 13 16:46:12 chanchala systemd[1]: webmin.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ The unit webmin.service has entered the 'failed' state with result 'exit-code'.
Aug 13 16:46:12 chanchala systemd[1]: Failed to start webmin.service - Webmin server daemon.
░░ Subject: A start job for unit webmin.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ A start job for unit webmin.service has finished with a failure.
░░ The job identifier is 16322 and the job result is failed.
jaap@chanchala:~$
Deleting the empty file /var/webmin/blocked does not help. It gets recreated.
Can you post your /etc/webmin/miniserv.conf file?
Is the IP address 10.203.122.2 still active on your system? From the error, it looks like it might not be ..
Seems like that IP is on a different system? Try just removing that
bind=line fromminiserv.confand then starting Webmin.> 10.203.122.1 dev tun122 proto kernel scope link src 10.203.122.2IP 10.203.112.2 is local on tun122.
On other systems this runs good.
When I remove 10.203.122.2 from bind= webmin runs. But then I can only log in via the restricted proxy webserver. It is important to have the possibilty to log in via the vpn.
Last edit: Jaap van Wingerde 2023-08-16
Strange: on an other server in webmin.conf bind=127.0.0.1, restricted access via proxy webserver ánd access via vpn 10.203.111.2 is possible.
On an other server bind=10.203.133.2 works. The only access is via VPN.
Wait did you edit that
bindline manually? Because it only supports a single IP address currently..ah
That said, we could support multiple bind addresses if this would be a useful feature?
I think that is very useful. By the way, I do not understand why a bind to 127.0.0.1 makes it possible to contact on a vpn-port.
Actually, you can configure Webmin to listen on multiple IP addresses at Webmin -> Webmin Configuration -> Ports and Addresses.