I've setup froxlor based on a well functioning LAMP stack enabled SSL witch certbot/letsenrypt.
Manual vhosts setup followed by certbot SSL procedure works well.
mariadb & phpmyadmin access all fine.
froxlor setup with tarball approach worked well.
Also certificate creation through froxlor works well ( double checked with php /var/www/froxlor/scripts/froxlor_master_cronjob.php --letsencrypt --debug ).
So far all fine with the exception that domains assigned in froxlor are falling back to the default.
Forum researches pointed me to the following possible root cases, which I've verfied and can be excluded in my case:
- Missing IPv6 entry: Not the case, my provider doesn't provide yet IPv6 addresses, only IPv4
- DNS issues: Can be excluded all fine with DNS, the same domain was already used earlier in the past for another server with same LAMP-Stack/certbot-lets
setup with same public IP.
apache error.log tells me:
"No matching SSL virtual host for servername my-domain.com found (using default/first virtual host)"
also, 'certbot certificates' shows only the initial SSL domains created at the time with certbot, not the ones coming from froxlor
From this post I got the hint, first to assign a new domain without SSL and later on apply the SSL flag.
Didn't help in my case.
This brings me to the question:
Would it be better to not use certbot nor for server preparation as well as afterwards on the running froxlor server?
Any other recommendations to solve or further debug the issue?
Question
Thomas Oettli
I've setup froxlor based on a well functioning LAMP stack enabled SSL witch certbot/letsenrypt.
Manual vhosts setup followed by certbot SSL procedure works well.
mariadb & phpmyadmin access all fine.
froxlor setup with tarball approach worked well.
Also certificate creation through froxlor works well ( double checked with php /var/www/froxlor/scripts/froxlor_master_cronjob.php --letsencrypt --debug ).
So far all fine with the exception that domains assigned in froxlor are falling back to the default.
Forum researches pointed me to the following possible root cases, which I've verfied and can be excluded in my case:
- Missing IPv6 entry: Not the case, my provider doesn't provide yet IPv6 addresses, only IPv4
- DNS issues: Can be excluded all fine with DNS, the same domain was already used earlier in the past for another server with same LAMP-Stack/certbot-lets
setup with same public IP.
apache error.log tells me:
"No matching SSL virtual host for servername my-domain.com found (using default/first virtual host)"
also, 'certbot certificates' shows only the initial SSL domains created at the time with certbot, not the ones coming from froxlor
From this post I got the hint, first to assign a new domain without SSL and later on apply the SSL flag.
Didn't help in my case.
This brings me to the question:
Would it be better to not use certbot nor for server preparation as well as afterwards on the running froxlor server?
Any other recommendations to solve or further debug the issue?
Many thanks for any hint!
Thomas
5 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now