d00p

...

Eh ja das hilft dir garnicht, denn der Cronjob macht ohne Parameter mal genau nix - einfach mal als root folgendes ausführen, dann repariert sich das von allein: php /var/www/froxlor/scripts/froxlor_master_cronjob.php --force --debug

Kannst du doch Recht einfach selbst prüfen: # du -sh /var/customers/webs/[Kunde] und # du -sh /var/customers/mail/[Kunde]

Then you already read what you can check and what Info ist required in Order to Help...

Das ist faktisch fast immer so, da du für nen anstandigen DNS server ein ganz anderes Setup machen würdest. Redundant, mind. zwei Server, in unterschiedliches IP-Netzen, etc. etc. etc. - und am allerwenigsten auf der kiste wo du die websites der kunden laufen lässt. Ebenso registrieren die meisten user ihre Domains bei einem Anbieter der DNS DIenste gleich mitanbietet, bzw. man dort Einträge etc. verwalten kann. Es ist in Froxlor rudimentär enthalten, damit das "Hosting"-System theoretisch alle benötigten Dienste inkludiert...

1 man tag...du hast ne vorstellung...aber hey, vllt schaust du dir mal die 0.10.0 branch auf github an, da gibts ne API Ist halt testing

Thread is 4 years old!!! Please do not reheat such old Threads

Sorry, there's no such (up-to-date) thing. Basically it's this: 1) activate SSL and (optionally) Let's Encrypt in the Settings 2) Go through configuration templates for the webserver after the settings have been adjust (enable mod_ssl, create global alias for acme-challenge, etc.) 3) add an IP address that has the ssl-flag enabled 4) edit a domain, select a ssl-enabled IP address and optionally enable usage of Let's Encrypt (you can skip step 5 if you use let's encrypt) 5) in case you have another certificate from an external source (key, certificate and maybe chain) switch to the customer of the domain, go to domain list, click on the LOCK icon to enter the certificate data The rest is done by froxlor's cronjob, you might need to wait for a maximum of 3 cron-runs (about 15 mins total)

yes

You can safely use the Auto-Update

0.10 is a separate branch and is far from releasing...there will be 0.9.x packages of course

Be patient or use the autoupdate feature or the tarball

No, web-filemanager are dangerous. Customers should just use FTP

Any file-manager is independent, froxlor has nothing to do with that.

I won't make it any faster when you post it here....

froxlor does not allow that you select a path like /proc (for security reasons). Disallowed are: /dev (except urandom), /proc, /etc, /sys and of course / Current solutuion: deactivate openbasedir for that domain

Sorry but this tutorial is nothing like the official way to install froxlor, it uses non-standard directories and weird settings to achieve things froxlor can handle itself by configuring it right...try https://github.com/Froxlor/Froxlor/wiki

Warum denn immer gleich neu aufsetzen? Wie umständlich. Irgendwohin hat froxlor doch wohl pool-configs erstellt. Kopier sie doch einfach an die richtige Stelle und starte php-fpm neu...ende

Und was steht in deinen Froxlor Settings? Welche php-version nutzt du da denn? Oder beide? Die Fehlermeldung sagt jedenfalls, dass phpfpm 7.1 nicht startet, weil keine config im pool-config ordner liegt, also hat froxlor dort keine erstellt, ergo, überprüfe deine Einstellungen

Dein Pfad zu den fpm Pool Configs ist nicht korrekt, prüfe deine fpm Einstellungen

The announcement and the Wiki will be updated.

Dear Froxlor Community, many great new features have found their way into our latest release. Here are the biggest innovations: Debian 9.x (Stretch) Support We finally added configuration templates for the current stable release of the Debian Linux Distribution. Important for all PHP-FPM users, you need to use mod_proxy/mod_proxy_fcgi as there is no libapache2-mod-fastcgi anymore. Multiple PHP-FPM installations Users with more than one PHP Version installed on their system were forced to use FCGID until now if they wanted to assign different versions of PHP to different customers or domains. This can now also be done for PHP-FPM. Some of the settings have moved from the global settings to a new section in the admin PHP menu called PHP-FPM version. Here you can add all the PHP-versions you have installed on your system with their corresponding config-path, restart-command, etc. In PHP-Configurations you can then choose the desired PHP-FPM version from a select-box. Settings Import / Export When installing Froxlor on multiple systems with equal settings, you can now export your settings from one intallation and import them to another. System-Hostname, default IP addresses and a few more variables that are either system specific or filled by the installation process anyway are being omitted. This feature will be "older version" compatible in later versions, meaning you will be able to import settings from 0.9.39 into newer versions of Froxlor. Please note that this new feature requires the PHP-json extension to be installed and loaded. Let customers choose PHP configuration When adding a new or editing an existing customer, the admin/reseller can now select from all available PHP configurations which of them are usable for the customer. If none is selected, the one the admin used when adding the domain is used. When the customer adds a new or edits an existing (sub)domain he can choose between the assigned PHP configurations (especially helpful if you have PHP configurations for different PHP-versions). Other PHP-FPM related changes Three minor changes/additions for PHP-FPM users: You can now specify paths which will be added to the PATH environment variable in each PHP-FPM pool. There was no such entry until now. If the setting is left empty, no env[PATH] entry will be generated You can now specify values for the security.limit_extensions setting on a per PHP-FPM version basis. You can now enable '-pass-header Authorization' for each PHP configuration so authorization headers are being passed from the webserver to PHP-FPM Testing implementation of Let's Encrypts ACME v2 As announced earlier by Let's Encrypt (see https://community.letsencrypt.org/t/staging-endpoint-for-acme-v2/49605 ) the new api version will be live as of 27th of februrary and is already available for testing (staging api). You can select the ACME v2 standard in the settings if you want to test it using the staging api. Sadly, wildcard-certificates, which is one of the biggest innovations in ACME v2, will only work using the dns-reg challenge (validation via DNS record) so this won't be an option for 99% of you (also, we did not implement the dns-reg challenge, only http-reg). It would be awesome if this is going to be changed. Note: You will still be able to (and probably should) use the ACME v1 API, especially if you have any productive certificates obtained already. Minor installation changes When checking the webserver and apache is found, we now assume that apache-2.4 is used instead of 2.2 MySQL STRICT-MODE issues Some newer distributions ar enabling the so-called STRICT-MODE for the DBMS by default, which Froxlor could not deal with on installation (e.g. some tables would not be created). These issues should be resolved now. *UPDATE* 0.9.39.1: fix possible invalid php-fpm-socket filename for dummy-socket fix selected phpfpm daemon when editing php-configuration fix updating wrong column when deleting a fpm configuration get rid of the need for allow_url_fopen only let admin select php-configs that the customer is allowed to use to avoid unwanted php-config changes when customer edits domain 0.9.39.2: add script to automatically configure services from shell without the need of copy/paste from the interface 0.9.39.3: add new hosting-plans feature add domain flag to avoid generation of nginx try_files directive in webroot which is not suitable for some applications 0.9.39.4: fixed add/edit domain due to misuse of Settings-class 0.9.39.5: fixed display of imap/pop3 flag when editing hosting plans You can see all changes on Github at https://github.com/Froxlor/Froxlor/compare/0.9.38.8...0.9.39.5 Download: 0.9.39.5 Note: Gentoo-ebuild and Debian packages will be released shortly as always. Visit http://www.froxlor.org or join our IRC channel #froxlor on irc.freenode.net. Thank you, d00p

Just use the "Auto-Update" from within the Panel

Geht schon wieder, sorry, ich spiel da ganz gern mal dran rum

manuell was löschen ist schonmal ein falscher ansatz die Frage verstehe ich nicht...du als admin entscheidest doch was du nutzen möchtest. fcgid/php-fpm hat den simplen aber schönen vorteil, dass die php prozesse unter dem kunden-benutzer ausgeführt werden (security++) phpmyadmin würd ich via archiv entweder unterhalb eines kunden (dich selbst, wenn du dich da auch angelegt hast) oder in den froxlor ordner installieren. Wenn du das auch per apt und paket machen willst UND fcgid/php-fpm nutzt kommst du sonst um einen manuellen vhost nicht herum. Bei "FTP" weiss ich nicht was du meinst, es sei denn du meinst WebFTP - davon rate ich so oder so in jedem fall ab... Webmail -> siehe phpmyadmin; bei roundcube kannst du mit dieser config (https://github.com/Froxlor/Froxlor/tree/extras/roundcube_plugins/password) das "passwort ändern" in roundcube realisieren Offizielle Howtos oder so gibt es dazu nicht