Jump to content
Froxlor Forum

Sandro Wabner

Members
  • Posts

    4
  • Joined

  • Last visited

  • Days Won

    2

Sandro Wabner last won the day on December 11 2023

Sandro Wabner had the most liked content!

Sandro Wabner's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Conversation Starter
  • One Month Later
  • Week One Done

Recent Badges

2

Reputation

1

Community Answers

  1. sorry, that was the solution. Since I did some experiments with the apache conf with a new alias, the hostname was diffrent. I rolled it all back, and now it works! Thank you very much for your fast reply and sorry for the fact that I posted the question without thinking twice
  2. I've got the same problem, after updating to 2.1.0 the admin interface wasn't accessible anymore, showing this message: Domain not configured This domain requires configuration via the froxlor server management panel, as it is currently not assigned to any customer. Now i did an update to 2.1.1 and the situation didn't change. Still the same message, and everything I tried to do had no effect at all (i.eg. switching the document root directly into the froxlor directory) The point is, the vhost of the froxlor admin interface is manually configured. I don't want the admin interface to be depenmdent from a configuration I have to do inside the admin interface. The Installation that is causing touble is running on Debian 11. In parallel I've got a newer host, running on Debian 12, that is going to replace the Debian 11 installation, which is running fine with Froxlor 2.1.1. I tried to fiugre out what froxlor needs to work properly, but I didn't find any problem. The only thing that is visible is, that a request on index.php throws status 302 and redirects the request to /froxlor/notice.html 176.199.24.215 - <httpuser> [11/Dec/2023:09:19:17 +0100] "GET /froxlor/ HTTP/1.1" 302 3909 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36" 176.199.24.215 - <httpuser> [11/Dec/2023:09:19:17 +0100] "GET /froxlor/notice.html HTTP/1.1" 200 5545 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36" Any Ideas??? cheers Sandro
  3. sorry! I found it out by myself and I can't remove this post. - The templates are bound to the admin account that creates the email addresses. If a customer is managed by admin-A and admin-B creates an email address, the standard template is used, if admin-A has no custom templates created
  4. I've got two froxlor instance running. On one the custom templates are used during creation of new email addresses and on the other instance they are completly ignored and the default templates are used instead. I think I've set up both identically and I've been clicking around in the settings for quite a long time. The only diffrence between both instances is the fact that the one with the problem has more email addesses, more admins, etc. Every relevant setting is identically, Email creation and sending out the info mails works fine in both cases, etc. etc. The mail templates are available for all languages in the customer and admin accounts. I've even setup a template for an alternative emailaddress but it had no effect on the templates. Anyone have any ideas??
×
×
  • Create New...