d00p

das vorgehen bei dns einträgen ist by design aktuell so, dass der eintrag gelöscht und ein neuer angelegt werden muss.

most likely cache :) it's always cache

Security release 2.3.7 [Security] secured regex for Dns LOC entries validation CVE: CVE-2026-41237 More information: https://github.com/froxlor/froxlor/security/advisories/GHSA-j6fm-9rfm-j5hx [Security] remove invalid control characters in every dns content-field see above [Security] ensure given shell exists in Ftps.add/update CVE: CVE-2026-41235 More information: https://github.com/froxlor/froxlor/security/advisories/GHSA-gcv3-5v9q-fmhh [Security] ensure authorized_keys file for SshKeys is within the customers documentroot CVE: CVE-2026-41236 More information: https://github.com/froxlor/froxlor/security/advisories/GHSA-mq5v-pxpm-8jw2 [Security] ensure a given symlink is resolved and validated correctly in FileDir::makeCorrectFile() see above [Security] secure api-key generation by asking user for current password More information: https://github.com/froxlor/froxlor/security/advisories/GHSA-f9rx-7wf7-jr36 [Security] ensure ownership of email/emailsender in frontend when deleting emailserver More information: https://github.com/froxlor/froxlor/security/advisories/GHSA-mr9h-45p9-fg8h [Security] ensure given dbserver value for Mysqls.add() is within the list of allowed mysql-servers for the customer More information: https://github.com/froxlor/froxlor/security/advisories/GHSA-q4rm-m6xh-5pv7 [UI] add missing label for REBUILD_NSSUSERS task by @lukasbableck in https://github.com/froxlor/froxlor/pull/1402 [i18n] Add Slovak language (sk) by @martinbernat in https://github.com/froxlor/froxlor/pull/1404 The security-advisories will be published on 29th of May in order to give people enough time to update.

nice

it's currently only the last 1000 lines iirc, depending on the customer, these logs can get HUGE and froxlor won't be able to load them (or php timeouts etc.). Maybe we will think of a better solution for froxlor3, this is unlikely to change in 2.x

Ja okay, jetzt weiss ich was los is. Du hast ja nicht mal die neueste 0.10.x version, die letzte war die 0.10.38.3 und nur mit der kommst du auch in die 2er updates. Das wird jetzt etwas frickelig, aber du musst halt die "db-updates" für 0.10.25 -> 0.10.38.3 durchführen: ALTER TABLE panel_domains CHANGE `ssl_protocols` `ssl_protocols` varchar(255) NOT NULL DEFAULT ''; ALTER TABLE panel_domains CHANGE `ssl_cipher_list` `ssl_cipher_list` varchar(500) NOT NULL DEFAULT ''; ALTER TABLE panel_domains CHANGE `tlsv13_cipher_list` `tlsv13_cipher_list` varchar(500) NOT NULL DEFAULT ''; ALTER TABLE panel_domains ADD `description` varchar(255) NOT NULL DEFAULT '' AFTER `ssl_sessiontickets`; ALTER TABLE mail_virtual ADD `description` varchar(255) NOT NULL DEFAULT '' AFTER `iscatchall`; INSERT INTO `panel_settings` SET `settinggroup` = 'panel', `varname` = 'imprint_url', `value` = ''; INSERT INTO `panel_settings` SET `settinggroup` = 'panel', `varname` = 'terms_url', `value` = ''; INSERT INTO `panel_settings` SET `settinggroup` = 'panel', `varname` = 'privacy_url', `value` = ''; INSERT INTO `panel_settings` SET `settinggroup` = 'system', `varname` = 'domaindefaultalias', `value` = '0'; INSERT INTO `panel_settings` SET `settinggroup` = 'panel', `varname` = 'logo_image_header', `value` = ''; INSERT INTO `panel_settings` SET `settinggroup` = 'panel', `varname` = 'logo_image_login', `value` = ''; UPDATE `panel_settings` SET `value` = 'letsencrypt' WHERE `settinggroup` = 'system' AND `varname` = 'letsencryptca'; INSERT INTO `panel_settings` SET `settinggroup` = 'panel', `varname` = 'logo_overridetheme', `value` = '0'; INSERT INTO `panel_settings` SET `settinggroup` = 'panel', `varname` = 'logo_overridecustom', `value` = '0'; INSERT INTO `panel_settings` SET `settinggroup` = 'system', `varname` = 'createstdsubdom_default', `value` = '1'; DELETE FROM `panel_settings` WHERE `settinggroup` = 'panel' AND `varname` = 'no_robots'; INSERT INTO `panel_settings` SET `settinggroup` = 'system', `varname` = 'froxlorusergroup', `value` = ''; INSERT INTO `panel_settings` SET `settinggroup` = 'system', `varname` = 'froxlorusergroup_gid', `value` = ''; INSERT INTO `panel_settings` SET `settinggroup` = 'system', `varname` = 'powerdns_mode', `value` = 'Native'; INSERT INTO `panel_languages` SET `language` = 'Česká republika', `iso` = 'cs', `file` = 'lng/czech.lng.php'; INSERT INTO `panel_settings` SET `settinggroup` = 'system', `varname` = 'acmeshpath', `value` = '/root/.acme.sh/acme.sh'; UPDATE `panel_settings` SET `value` = '202112310' WHERE `settinggroup` = 'panel' AND `varname` = 'db_version'; UPDATE `panel_settings` SET `value` = '0.10.38.3' WHERE `settinggroup` = 'panel' AND `varname` = 'version'; (keine Garantie das ich grad auf die Schnell wirklich alles erwischt hab)

Da sollte garkein ajax.php eine Rolle spielen wenn du noch im Update-Prozess bist. Aktivere doch mal das File-Logging: (Mysql, manuell): UPDATE `panel_settings` SET `value` = '1' WHERE `settinggroup` = 'logger' AND `varname` = 'enabled'; UPDATE `panel_settings` SET `value` = 'syslog,file' WHERE `settinggroup` = 'logger' AND `varname` = 'logtypes'; UPDATE `panel_settings` SET `value` = '2' WHERE `settinggroup` = 'logger' AND `varname` = 'severity'; UPDATE `panel_settings` SET `value` = 'froxlor.log' WHERE `settinggroup` = 'logger' AND `varname` = 'logfile';die log 'froxlor.log' sollte dann im Ordner /logs/ auftauchen

ah okay, ja von 0.10.x ist aber auch wirklich...puh....also deine datenbank hat auf jedenfall noch den stand von 0.10.25 und deine dateien sind 2.3.5 - d.h. da ist noch genau kein Datenbank-Update gelaufen, weil ein 2.x featuer (gui_access) dich davon abhält. Am besten machst du nun Folgendes: 1) MySQL, manuell: ALTER TABLE `panel_admins` ADD `gui_access` tinyint(1) NOT NULL default '1'; ALTER TABLE `panel_customers` ADD `gui_access` tinyint(1) NOT NULL default '1';2) Damit das Update nicht versucht, die Felder anzulegen: 2.1) Öffne ./install/updates/froxlor/update_2.2.inc.php 2.2) Lösche diese vier Zeilen (Zeile 98-101 müsste das sein): Update::showUpdateStep("Enhancing admin and user table"); Database::query("ALTER TABLE `" . TABLE_PANEL_ADMINS . "` ADD `gui_access` tinyint(1) NOT NULL default '1';"); Database::query("ALTER TABLE `" . TABLE_PANEL_CUSTOMERS . "` ADD `gui_access` tinyint(1) NOT NULL default '1';"); Update::lastStepStatus(0);Dann probier das Update noch mal

irgendwas lässt dein froxlor glauben, dass die Dateien neuer sind als die (froxlor) Datenbank. Mit Sicherheit ist hier bei so einem massiven Versions-Sprung irgendwo was hängengeblieben. Was genau wird denn angezeigt, wenn du links im Menü auf "froxlor update" klickst, ggfls lässt sich hier einsehen wo er aufgehört hat und wo der Updater dann ggfls crashed

Currently not intended this way. Customers can see logs in the UI if allowed by the admin

DocRoots and settings in froxlor cannot change this behaviour. Your server listens to this IP and of course answers accordingly. You may add rewrite rules or similar to redirect to a domain if the request is not the domain itself, e.g. RewriteEngine On RewriteCond %{HTTP_HOST} !^panel\.example\.tld$ [NC] RewriteRule ^ https://panel.example.tld%{REQUEST_URI} [R=301,L]Alternatively, create a custom vhost file, e.g. 000-fallback.conf and do something like <VirtualHost *:80> ServerName panel.example.tld Redirect permanent / https://panel.example.tld/ </VirtualHost>depending on your needs

agreed

dont know any specialties about AlmaLinux...this usually is no issue at all. the check in lib/Froxlor/Install/Install.php is: // check whether we can read the userdata file if (!@touch(dirname(__DIR__, 2) . '/.~writecheck')) { // get possible owner $posixusername = posix_getpwuid(posix_getuid())['name']; $posixgroup = posix_getgrgid(posix_getgid())['name']; $this->criticals['wrong_ownership'] = ['user' => $posixusername, 'group' => $posixgroup]; } else { @unlink(dirname(__DIR__, 2) . '/.~writecheck'); }it should ensure the folder lib/ within the froxlor root-directory can create/write the userdata.inc.php file later on in the installation process

well check that user apache can also write to the root-folder of froxlor, or else you will see that error (it's a write-check using php's built-in touch() Also, I want to note that AlmaLinux is not officially supported and that there are no configuration-files for it, you will have to manually configure the services (adapt from supported distros)

no that would not be a critical error, please show a screenshot