d00p
-
Posts
10303 -
Joined
-
Last visited
-
Days Won
43
Posts posted by d00p
-
-
-
Einfach Mal Manuell mit --force --debug den Cron laufen lassen und Schauen ob alles ok ist....hab hier bei fast 100 Installation absolut keine Probleme
-
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
-
let's encrypt deaktivieren, cron laufen lassen, wieder aktivieren, cron laufen lassen
-
dann lösch doch einfach alle froxlor-generierten vhosts in /etc/apache2/sites-enabled/*froxlor* - und rufe http://{ip}/froxlor auf ...
-
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 -fdund durch biste
-
Froxlor uses almost nothing. You should rather check for Webserver, Database, etc. Requirements - froxlor in that regard is the least of the "problems"
-
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
-
That's already in 2.2-dev...current main-branch.
-
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)
-
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
-
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
-
Oh yeah there seems to be an issue with a ajax-request to for this option, need a bit more time for that
-
Just now, ocitsupport said:
Can you say why "Separate logfiles" is not permanently set?
This is a per domain setting and should be stored permanently of course. Let me run some checks and get back to you
-
try the following patch:
diff --git a/lib/Froxlor/Cron/Http/Apache.php b/lib/Froxlor/Cron/Http/Apache.php index f3fe3f6b..609f9164 100644 --- a/lib/Froxlor/Cron/Http/Apache.php +++ b/lib/Froxlor/Cron/Http/Apache.php @@ -823,6 +823,7 @@ class Apache extends HttpConfigBase $modrew_red = ' [R=' . $code . ';L,NE]'; } + $vhost_content .= $this->getLogfiles($domain); // redirect everything, not only root-directory, #541 $vhost_content .= ' <IfModule mod_rewrite.c>' . "\n"; $vhost_content .= ' RewriteEngine On' . "\n";
-
Yup, just checked, there are no log-directives generated when the domain is a redirect
-
check the vhost, is there a "AccessLog" directive being generated? if yes, does the log file exist and do entries get logged on visit?
-
Aktuell handlet das froxlor nicht, denn Let's Encrypt auch in postfix/dovecot zu nutzen ist natürlich möglich, aber admin-Entscheidung - da hat froxlor keine Finger drin. Ändert sich mit 2.2, siehe https://github.com/froxlor/Froxlor/issues/1186
-
Are you using the latest v2.1.7? there was a fix: https://github.com/Froxlor/Froxlor/commit/537b274b4c50b6d5a28c140d48e955466173b7dc
-
Du hast dem Kunden ein Kontingent von 5000 MB für disk/webspace zugewiesen....wenn es voll ist, macht der FTP dicht
-
Dann probier doch z.B. mal was mozilla vorgibt/empfiehlt: https://ssl-config.mozilla.org/#server=postfix&version=3.4.8&config=intermediate&openssl=1.1.1k&guideline=5.7
Ich meine immer noch das das ein Problem beim "fremden" smtp ist
-
Sieht doch alles fein aus, sogar TLSv1.3, da würde ich ja fast behaupten, dass vllt die zwei server die nichts mehr an dich senden können ggfls veraltet sind oder falsch konfiguriert. Offenbar haben die ja eine änderung, wenn deine logs da trotz anonymisierung irgendwie stimmen: IPMAIL1.FremderMailserver <> IPMAIL2.FremderMailserver
Aber zeig doch bitte hierfür auch mal deine postfix config in bezug auf TLS (alles bitte), also z.b.:
### TLS settings ### ## TLS for outgoing mails from the server to another server smtp_tls_security_level = may smtp_tls_note_starttls_offer = yes ## TLS for email client smtpd_tls_security_level = may smtpd_tls_key_file = /root/.acme.sh/domain/domain.key smtpd_tls_cert_file = /root/.acme.sh/domain/fullchain.cer smtpd_tls_CAfile = /root/.acme.sh/domain/ca.cer smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtp_use_tls = yes smtpd_use_tls = yes smtpd_tls_session_cache_timeout = 3600s tls_random_source = dev:/dev/urandom smtpd_tls_mandatory_ciphers = high smtpd_tls_mandatory_exclude_ciphers = aNULL, MD5
-
Probier doch einfach alle? 25, 587, 465...
Bind9 / DNS Default zonefile template for custom DNS "default" entrys
in General Discussion
Posted
Thread from 2022....also, it will be in 2.2 (current git main branch)