When you update, there is always a backup done, so deleting ispconfig vhost is not really big deal, you can always restore from backup. Your...
Then make a copy/copies of it and use the copy for your trial. Nobody says it will. May be, but you can fix it first, if you want. Just remove...
You know you can simply remove your ispconfig.vhost and let force update recreate it correctly right? While doing that, make sure you do not have...
If you migrate, just migrate normally, make sure all things working just fine as it is before. From there, make copy(ies) to test conversion to...
Try deleting you apps.vhost and force update ISPConfig for it to be reconfigured with the default that came with it.
I think you can follow https://blog.schaal-24.de/ispconfig/ispconfig-apache-durch-nginx-ersetzen/?lang=en as general method to convert but do not...
This answer was partially mentioned in that thread but jk_init thereafter makes it complete.
If you continue with the current one, yes, as @remkoh confirmed. However, if you redo the vm for MX server, with --no-web option, then Port 80 is...
To be certain, what is your command of installing MX server? Did you follow this guide:...
This should be true, if I remember correctly, when webserver exist, the default is to use webserver to obtain LE certs, and only when it does not...
You should not need to keep it open in MX server even for LE, at least that was how I coded it in the early integration with ISPConfig. Then, the...
They are still valid, and ISPConfig force update only forcing ISPConfig update, not forcing LE certs update / renewal.
Other than what already mentioned, I am not sure, so sorry, but I am very keen and please to learn that Debian 13 nginx 1.26.3, apache2 2.4.65 and...
The script is fine, and should 1st check the version in PMA repo and compare to local, if it's the same latest, abort, otherwise, update. The...
If it's just another Deb12 vm, just go for it. You've got nothing to loose to copy to it right?
Separate names with a comma.
