https://docs.froxlor.org/latest/admin-guide/php-versions-and-configuration/#_2-php-fpm-versions

Thanks

I'll need a working apache for that :)

Regards,

Dudi

rm /etc/apache2/sites-enabled/*froxlor*
systemctl restart apache2
# open http://your-ip-address/froxlor in your browser

This worked.

Lemme reconfigure.

Thanks,

Dudi

After froxlor created the new conf files apache2 does not start with the same unable to bind :443 error.

Must go to a customer, I'll update when I'm back.

Regards,

Dudi

Then you either have to many or no Listen statement at all...grep "Listen" /etc/apache2/

root@stoli:/var/www/html/froxlor# grep "Listen" /etc/apache2/*

/etc/apache2/ports.conf:Listen 80

/etc/apache2/ports.conf: Listen 443

/etc/apache2/ports.conf: Listen 443

I remove the rest of "grep: /etc/apache2/sites-available: Is a directory"

Dudi

then maybe run grep -r "Listen" /etc/apache2/ to check ALL files...

root@stoli:/var/www/html/froxlor# grep -r "Listen" /etc/apache2/

/etc/apache2/sites-enabled/10_froxlor_ipandport_193.186.2.3.80.conf:Listen 193.186.2.3:80

/etc/apache2/sites-enabled/10_froxlor_ipandport_193.186.2.3.443.conf:Listen 193.186.2.3:443

/etc/apache2/ports.conf:Listen 80

/etc/apache2/ports.conf: Listen 443

/etc/apache2/ports.conf: Listen 443

root@stoli:/var/www/html/froxlor#

Regards,

Dudi

there you go, you've enabled "Listen Statement: Yes" in froxlor -> ips and ports and have a global Listen on these ports in the ports.conf (maybe disabled on the old server?)

I'll try when I'm back and update.

The old server is still up, I'll verify config there.

Thanks & regards,

Dudi

Solved.

There was a duplicate on :80 as well.

Thank you again very very much.

Regards,

Dudi

Hi,

One last thing remains.

The domains certs are fine, but the froxlor host cert was created when the host had a different hostname.

I have a LE cert for the host at /root/.acme.sh

I set the cert path & key path in IP & ports for the :443 record, also set it in System/Settings/SSL settings but this is ignored.

The :443 conf file still points to the bad cert at /etc/ssl/froxlor-custom/. Even if I set the cert in the conf file, the cron job reverts it to the old setting.

What is the best way to fix this?

TIA & regards,

Dudi

I deleted the host cert files in /etc/ssl/froxlor-custom/ - they were recreated with the correct hostname in the cert filename, but openssl shows that the cert was made for a different CN

I went to every possible config in the GUI, the old hostname does appear anywhere.

Regards,

Dudi

but the froxlor host cert was created when the host had a different hostname.

thought you've migrated the old system to a new one....obviously a lot more has changed...disable let's encrypt for the froxlor-vhost, run the cron (`froxlor-cli froxlor:cron -fd`), re-enable Let's encrypt for the froxlor-vhost and again, run cron twice

I did migrate. this is the migrated server. Some of the issues were due to a new IP and hostname for the new server.

I'll do what you suggested and update.

Thanks for your time & patience.

Regards,

Dudi

I did it.

Disable SSL for the host, run cron, enable SSL for the host and run cron twice.

The file timestamp is current for all certs, but:

root@stoli:~# openssl x509 -noout -text -in /etc/ssl/froxlor-custom/stoli.kolcore.com.crt

Certificate:

Data:

Version: 3 (0x2)

Serial Number:

05:6f:11:a8:ff:b3:47:ca:5b:49:84:3e:8f:dc:23:2d:07:46

Signature Algorithm: ecdsa-with-SHA384

Issuer: C = US, O = Let's Encrypt, CN = E8

Validity

Not Before: Sep 10 14:22:27 2025 GMT

Not After : Dec 9 14:22:26 2025 GMT

Subject: CN = h99.kolcore.com

CN is for h99.kolcore.com - my guess is that its hidden in the DB somewhere.

Regards,

Dudi

check the "froxlor aliases" setting maybe...other than that, no idea.

Nothing in aliases.

This makes me nuts.

I'll search the DB, what table is most likely to have it?

Regards

Dudi

well, maybe just check in "SSL Certificates" and check the domain it was issued for (and possible SAN list) etc.

Nothing found in froxlor DB for the old hostname or its IP.

I'll wipe and install clean tomorrow, I can't risk odd problems that can't be resolved.

Thanks for the efforts & regards,

Dudi