| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Debian 12 |
| Webmin version | 2.101 |
| Virtualmin version | 7.8.2 |
| Related packages | Roundcube 1.6.2 |
On a completely fresh install, after installing the roundcube script, I get an error 503 service unavailable page when trying to access it.
/var/log/virtualmin/error_log shows the following:
[Wed Oct 11 06:13:29.742393 2023] [ssl:warn] [pid 36360:tid 139935042680704] AH01906: example.com:443:0 server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Wed Oct 11 06:15:03.205472 2023] [proxy:error] [pid 45732:tid 139935030425280] (13)Permission denied: AH02454: FCGI: attempt to connect to Unix domain socket /var/php-fpm/169701919041392.sock (*:80) failed
[Wed Oct 11 06:15:03.205525 2023] [proxy_fcgi:error] [pid 45732:tid 139935030425280] [remote 99.229.125.139:65238] AH01079: failed to make connection to backend: httpd-UDS, referer: https://www.example.com:10000/
Any help would be greatly appreciated. Thanks
EDIT: It seems as though it’s PHP, in general… I have an identical install that worked fine on a different server. I need to investigate why /var/php-fpm/169701919041392.sock is inaccesible
EDIT 2: Ok, I figured out that this is a bug with Virtualmin, here is how you can replicate the issue: When you add a new server, create a servername that is nine digits - so 123456789.xyz for example. This breaks something on an intrinsic level for some reason.
When I removed the digit only virtual server and replaced it with a new server named “example.xyz”, the socket file in /var/php-fpm/ showed the proper GID in file properties (1002/example), whereas before it was showing as “UNKNOWN”.
Maybe I ought to post this in the bug tracker?
EDIT 3: And just an additional note on a workaround: When you create a new virtual server, under “administration username”, change it from ‘automatic’ to ‘custom username’ and pick something safe like ‘website’. Next expand the "Advanced options’ section and change “Group for domain users” from ‘Automatic’ to ‘Custom group name’ and pick something safe like ‘website’ again. This is confirmed working and my domain is up and running again.