Vitor Ferreira's picture
Vitor Ferreira - Fri, 2023/04/21 - 21:03

Hi,

I am using proxmox 7.3-3 with bullseye11 debian with portainer and can't get webmin to work (https://XXX.XXX.XXX.XXX:12321). 

Log:

Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform
Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: Compiled with OpenSSL 1.1.1k  25 Mar 2021
Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: Running  with OpenSSL 1.1.1n  15 Mar 2022
Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI>
Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: Reading configuration from file /etc/stunnel/webmin.conf
Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: UTF-8 byte order mark not detected
Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: FIPS mode disabled
Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: Configuration successful
Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: Binding service [webmin] to :::12321: Address already in use (98)
Apr 21 17:55:35 FrigateLxc stunnel[3513]: LOG5[ui]: Switched to chroot directory: /var/lib/stunnel4/
Apr 21 17:55:35 FrigateLxc stunnel[3515]: LOG3[main]: Cannot create pid file /webmin.pid
Apr 21 17:55:35 FrigateLxc stunnel[3515]: LOG3[main]: create: Permission denied (13)
Apr 21 17:55:35 FrigateLxc systemd[1]: stunnel4@webmin.service: Can't open PID file /var/lib/stunnel4/webmin.pid yet?) afte>
Apr 21 17:56:01 FrigateLxc cron[112]: (*system*) WRONG FILE OWNER (/etc/crontab)
Apr 21 17:56:01 FrigateLxc cron[112]: (*system*e2scrub_all) WRONG FILE OWNER (/etc/cron.d/e2scrub_all)
Apr 21 17:56:01 FrigateLxc cron[112]: (*system*cron-apt) WRONG FILE OWNER (/etc/cron.d/cron-apt)

Can anyone help?

Thanks,

Vítor

Forum: 
Support
Tags: 
webmin
Jeremy Davis's picture

Jeremy Davis - Wed, 2023/05/03 - 06:54

On face value, it looks like a simple permissions issue writing the webmin.pid file and I was going to explain how to change the ownership. But looking a little closer, it looks like there are also permission issue for cron-apt too. That suggests that things are pretty seriously messed up. My guess is that there is an issue with the user mapping.

Could you please clarify exactly how you set this up? You note that it's running on Proxmox and from the output you've shared, I assume in an LXC container. But you also mention Portainer, which AFAIK is a Docker management tool and I'm not completely clear how that is relevant? Please also share your container config (e.g. is it nested? is it unprivileged?) and whether this is freshly launched and exhibited this issue from the start, or whether it was working then broke.

Add new comment