All Activity

DAAAAANKEEEE!!!!!

Einstellungen -> Froxlor Vhost Einstellungen -> Let's Encrypt: nein dann: bin/froxlor-cli froxlor:cron -fd und dann das ganze nur mit Let's Encrypt : ja

Wie genau?

let's encrypt deaktivieren, cron laufen lassen, wieder aktivieren, cron laufen lassen

Das hat geklappt. Danke. Ich war blind. Für die Froxlorverwaltungsseite .... wie kann ich erzwingen, dass das SSL-Zertifikat neu erzeugt wird? der FQDN ist ja anders ...

dann lösch doch einfach alle froxlor-generierten vhosts in /etc/apache2/sites-enabled/*froxlor* - und rufe http://{ip}/froxlor auf ...

Leider wurde die Maschine direkt im neuen Netzwerk verbaut, und hat jetzt die neue IP und den neuen Namen. Ich komme dann nicht mehr über https://FQDN an froxlor dran ...

Wieso sollte die froxlor-webui nicht funktionieren? FQDN würd ich vor dem Umzug in den einstellungen schon ändern, dann die DB und lib/userdata.inc.php migrieren auf den neuen und danach bin/froxlor-cli froxlor:switch-server-ip (siehe https://docs.froxlor.org/latest/admin-guide/cli-scripts/#switch-server-ip) und anschließen einmal die configs neugenerieren: bin/froxlor-cli froxlor:cron -fd und durch biste

Hallo, ein Server muss nun umziehen in ein anderes RZ und dabei äbdert sich der FQDN und die IP. Wie das in Froxlor machen? Die alte Froxlorverwaltungsseite geht ja dann nicht mehr. Irgendwelche VHOSTs ändern? Tipp wäre super. BG V

Thanks for your answer! its Great!

Froxlor uses almost nothing. You should rather check for Webserver, Database, etc. Requirements - froxlor in that regard is the least of the "problems"

What is the minimum system requirement to run froxlor. i.e. RAM, CPU, Space?

Wow! it's good to hear me. Thanks ok, it means Froxlor supports arm processors. Am I right? But If architecture is not matter, then why other players says that they are not supporting arm [processors] based instances? This is not so important to reply if really Froxlor supported and tested with arm processors. is anyone who had tested this on arm processors?

Well if a Webserver, Database and php is running on it then yes. It's such a bunch of php files, architecture has not really anything to do with it

Is ARM Processor Supported by Froxlor?

That's already in 2.2-dev...current main-branch.

I have set up SPF and DKIM for the domains provided by Froxlor, that works pretty straight forward except for the opendkim thing, but I got it working. Now I am wondering if it is possible to add a DNS record for DMARC to each domain that is maintained automatically, this would be a TXT record with _dmarc TXT "fixed string" or a domain-by-domain entry when using a different feedback address for different domains for domains that are manually maintained that works by adding it manually, but a generic rule for all domains would be helpful

I tried with opendkim now, that should work until the regular support is available. I wrote a perl script to convert the dkim-keys.conf to the dkim-signtable and dkim-keytable files for opendkim, that works fine as long as no new domains are added, then the script would have to be rerun In case anybody is interested, the file is attached conv_dkim.pl

You may also switch the update channel to nightly to test/try it now in the current testing version

Wait for v2.2 in the summer, we'll integrate rspamd with a better dkim implementation. The current one is very old and not easy to use (and not without DNS enabled)

I am currently trying to activate dkim mails on a system that uses debian 11 and I am failing to find a package that provides dkim-filter I guess that is originally provided by sendmail, but I am coming up blank with any package that is in the debian repositories. Most guides about dkim for debian suggest using opendkim but I assume that does not fit the config files generated by Froxlor

Well then you indeed have too many redirects....check a potential .htaccess file or the target page. A redirect is VERY basic, it just tells the client to go to the other page. Most likely the other page redirects back or does a reedirect to itself. You can find out by using `curl` on the shell and inspect the headers (Location: http://TARGET) and then follow these targets and you will see that there is a redirect back to where it came from at some point

I'm experiencing the same issue. I've attempted to redirect a domain to another domain within Froxlor by inserting the URL in the "path" label, but it's not working as expected. Instead, I'm encountering an error stating "too many redirects." Has anyone else encountered this problem and found a solution?

Thank you very much for the quick response. No problem. I can wait for a fix. No need to hassle.

There is indeed a bug with this, missing csrf-tokens in some ajax-requests, I will have to make a bugfix release for that (or you would have to build the assets yourself with npm etc. if you want, let me know). Most like on friday this week then