I kept as many settings as possible to be in default.
Things that are not in default settings are: install rclone, change apache server templates to enable http2, wordpress htaccess to apache conf, and php-fpm pool mode to ondemand.
How to fix localhost to be able to resolve, well, localhost on wordpress? I don’t know how to replicate. I have to fix it ASAP, but what can I do to catch the culprit when it happen again? What log should be monitored, or created to be able to find how to replicate this issue?
doing ping localhost on the VPS shows it’s ipv6 printed from ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 123.123.123.123 netmask 255.255.255.0 broadcast 111.111.111.111
inet6 foo:7c54 prefixlen 64 scopeid 0x0<global> //this address is shown up when running ping localhost
inet6 foo:7c54 prefixlen 64 scopeid 0x20<link>
ether foo:54 txqueuelen 1000 (Ethernet)
Hi, firstly do you know the rules of the posting here? What os you run, what version of PHP, mariadb , Apache or nginx or fry pan it’s?
I don’t see anything like that on your initial pos, so do not expect someone to just guessing… people will usually considered this as spam at least me for sure.
It’s not properly setup for production server… hostname, as usual, but who knows his settings and os, not possible to help as commands are different even for Alma or Ubuntu… if he is not bothering to tell, it’s fine
I would like to apologize for being a bit harsh, but now it’s a bit more clear what the issue can be. I would go with Pete aka tnp… I know him more then decade and since I’m Linux guy (Debian) he is robust Unix man (centos rhel etc) and since Alma is very very close to centos my best bet would be his expertise. Obviously think twice when reading forums and make cut once
all matches. Just after some moments after creating virtual server (hours, days, weeks, random) those with define( 'DB_HOST', 'localhost' ); have “error establishing database connection” error.
I have tried to restart all services, reboot server, this issue is not reproduced.
@technicalw I can help you remote, what time would be suitable for you? I can slot you only in Friday,zoom or teams and TeamViewer here as I do not know you I would navigate you over the phone call. Also this iso off free support here and there to just make you going with virtual min
The problem is not reproduced yet since my session with @tpnsolutions 9 days ago, we both still didn’t able to identify the root problem. I hope that the problem is gone, but I can’t risk live site with define( 'DB_HOST', 'localhost' ); in that server.
All dummy virtual server, as subdomains, are still running well.
Ilia, on Virtualmin staff, had initially recommended that I change “localhost” to “127.0.0.1” in the WordPress site’s wp-config.php file. I did that and the “jailed” sites affected worked fine.
I don’t pretend to know why or how this fixed it.
Most importantly, Ilia also said the Virtualmin fix to this would be forthcoming.
This is my initial solution and it works. However, install scripts and most wordpress default configuration define db_host as localhost so that is another task for every wordpress install.
Be aware that I have curl problem too when it is jailed, and I cannot use any WP SMTP plugin to use gmail SMTP.
In the end, I disable every jails. But your configuration might differ with mine.
Thanks for the update. As of the time of this writing I have placed several more test websites on the Debian 10 box running Virtualmin 7.1 following this order:
create the SSL site on the domain
enable the jail
run the WordPress script
Each is using “localhost” and appear to be operating without error.
I’m just unable to enable the jail on a site that run the WordPress script on prior to enabling the jail.
