Closed chrschn closed 10 months ago
1) Domain not configured:
Dont use a customer-domain for froxlor or use an alias, that's not how it is intended. It will use the wrong permissions. See also https://forum.froxlor.org/index.php?/topic/20176-froxlor-21-domain-not-configured/
2) letsencrypt and sql error
That most likey happened during the update, best way to avoid this would be to stop the cron temporarily during an update
Thanks for the super fast response!
- Domain not configured:
Dont use a customer-domain for froxlor or use an alias, that's not how it is intended. It will use the wrong permissions. See also https://forum.froxlor.org/index.php?/topic/20176-froxlor-21-domain-not-configured/
Alright, here is how I recovered my system:
randomhostname.my-hoster.com
my-domain.de
from the customer domainsmy-domain.de
in the Froxlor VirtualHost settingsNow I can access Froxlor again at my-domain.de/froxlor/
, but I lost the possibility to manage email addresses for that domain in Froxlor. Is there a way to do that?
BTW, step 4 took me a moment to figure out. I had expected an option to customize the vhost settings in the Froxlor VirtualHost settings panel, but there is none. Maybe just a hint in that panel where to find the vhost settings would be nice.
2. **letsencrypt and sql error**
That most likey happened during the update, best way to avoid this would be to stop the cron temporarily during an update
That's what I thought as well.
Now I can access Froxlor again at my-domain.de/froxlor/, but I lost the possibility to manage email addresses for that domain in Froxlor. Is there a way to do that?
Well you didnt have to remove "my-domain.de" from the customer. You could've just used "froxlor.my-domain.de" for froxlor itself...(or any other non-existing subdomain)
Well you didnt have to remove "my-domain.de" from the customer. You could've just used "froxlor.my-domain.de" for froxlor itself...(or any other non-existing subdomain)
Oh, so you're suggesting to add the domain to a customer, create a subdomain, then using that for the Froxlor vhost? That kinda sounds pretty much like using a customer domain for Froxlor, but with extra steps. ;-)
eh no, i just said that it is possible to use a subdomain of a domain to have the possibility to use said domain as customer (and hence for emails, website. etc.). No one forces you to use a main-domain like "my-domain.tld" as froxlor systemhostname....you are free to use any valid fqdn
Got it. Thank you for your help!
Since Froxlor was upgraded on my Debian bullseye server from version 2.0.24-1 to 2.1.0-1 and meanwhile 2.1.1-1, the admin interface of Froxlor is not accessible anymore. I'm getting redirected to the
Domain not configured
page. The redirect happens when I openmy-domain.de/froxlor/
. I can accessmy-domain.de
just fine.My setup is as follows.
my-domain.de
is configured in Froxlor and assigned to a customer. For that domain, I configured an Alias for Apache in the Froxlor domain settings:I verified that the domain has a proper customer ID set using the CLI:
I read the v2.1 release notes and migration guide, but they didn't cover the issue I'm seeing.
System information
Logfiles There is no additional information in the Apache logs.
Additional Context One thing thing I obsoerved, which may or may not be related to this issue: When Froxlor was initially upgraded from 2.0.24-1 to 2.1.0-1, the
letsencrypt
cron job failed once, see stack trace below. I don't know if that was just a transient error during the upgrade or if it points to different issue.