Jump to content
Froxlor Forum

Tealk

Members
  • Posts

    188
  • Joined

  • Last visited

Posts posted by Tealk

  1. Hi,

    wo ich heute auf Froxlor zugreifen wollte ist mir augefallen das das Zertifikat ausgelaufen ist, komischerweise kann dies nicht erneuert werden, und ich verstehe nicht so ganz warum.

    php /var/www/froxlor//scripts/froxlor_master_cronjob.php --letsencrypt --debug
    [information] Updating Let's Encrypt certificates
    [information] Creating certificate for DOMAIN
    [information] Checking for LetsEncrypt client upgrades before renewing certificates:
    [Mo 9. Sep 15:44:09 CEST 2019] Installing from online archive.
    [Mo 9. Sep 15:44:09 CEST 2019] Downloading https://github.com/Neilpang/acme.sh/archive/master.tar.gz
    [Mo 9. Sep 15:44:10 CEST 2019] Extracting master.tar.gz
    [Mo 9. Sep 15:44:10 CEST 2019] Installing to /root/.acme.sh
    [Mo 9. Sep 15:44:10 CEST 2019] Installed to /root/.acme.sh/acme.sh
    [Mo 9. Sep 15:44:10 CEST 2019] Good, bash is found, so change the shebang to use bash as preferred.
    [Mo 9. Sep 15:44:11 CEST 2019] OK
    [Mo 9. Sep 15:44:11 CEST 2019] Install success!
    [Mo 9. Sep 15:44:11 CEST 2019] Upgrade success!
    [error] Could not get Let's Encrypt certificate for DOMAIN:
    [Mo 9. Sep 15:44:11 CEST 2019] Renew: 'DOMAIN'
    [Mo 9. Sep 15:44:11 CEST 2019] 'DOMAIN' is not a issued domain, skip.
    [information] Let's Encrypt certificates have been updated
    [notice] Checking system's last guid

     

  2. Hi,

    ich wollte heute mal Apache Block Bad Bots installieren, leider habe ich das problem das ich nicht weiß wie ich das in Froxlor kann.

    Ich müsste nämlich folgendes in die vHost bringen:

    <Directory "/var/www/html">
      AllowOverride All
      Options FollowSymLinks
      Include custom.d/globalblacklist.conf
    </Directory>

    Das hätte ich über die Webserver-Einstellungen und dem Punkt Standard vHost-Einstellungen probiert.

    Leider ist dann das Directory doppelt in der vHost. Hab ich da irgend eine andere Möglichkeit?

  3. Hi,

    ich bekomme bei folgenden Seiten die unten stehende Fehlermeldung.

    Ressourcenverbrauch
    Einstellungen
    Configs neu schreiben
    PHPinfo()
    Datenbankprüfung
     

    -------------------------------------------------------------
    1045 SQLSTATE[HY000] [1045] Access denied for user 'root'@'127.0.0.1' (using password: YES)
    
    File: lib/Froxlor/Database/Database.php:323
    
    Trace:
    #0 lib/Froxlor/Database/Database.php(323): PDO->__construct('mysql:dbname=fr...', 'root', 'DB_ROOT_PWD', Array)
    #1 lib/Froxlor/Database/Database.php(164): Froxlor\Database\Database::getDB()
    #2 admin_settings.php(28): Froxlor\Database\Database::needSqlData()
    #3 {main}

    Ich nutze

    0.10.0-rc2 (DB: 201904250)

    PHP-Version:7.3.8-1+0~20190807.43+debian10~1.gbp7731bf

    MySQL-Server-Version:5.5.5-10.3.16-MariaDB-1:10.3.16+maria~stretch

  4. Seit dem Update auf Debian 10 habe ich ab und an mal folgende Zeile in der Log, kann es ein Problem vom Update bzw Froxlor sein?

    [Wed Aug 07 11:02:45.041232 2019] [proxy_fcgi:error] [pid 4714:tid 140246930089728] (70007)The timeout specified has expired: [client 212.211.192.4:45421] AH01075: Error dispatching request to : (reading input brigade), referer: https://anzahcraft.de/admin.php?add-ons/
    [Wed Aug 07 11:46:09.687361 2019] [proxy:error] [pid 21740:tid 139845682669312] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/lib/apache2/fastcgi/4-anzah-anzahcraft.de-php-fpm.socket (*) failed

     

  5. With the following file:

    /etc/cron.d/froxlor

    # automatically generated cron-configuration by froxlor
    # do not manually edit this file as it will be re-generated periodically.
    PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
    #
    */5 * * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --tasks 1> /dev/null
    0 0 * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --traffic 1> /dev/null
    5 0 * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --usage_report 1> /dev/null
    0 */6 * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --mailboxsize 1> /dev/null
    */5 * * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --letsencrypt 1> /dev/null
    10 0 * * * root /usr/bin/nice -n 5 /usr/bin/php7.2 -q /var/www/froxlor//scripts/froxlor_master_cronjob.php --backup 1> /dev/null

     

  6. I raised froxlor to 0.10 before the Debian update. Renamed the old folder and restored the config file.
    Since then I haven't changed anything in the settings.
    After the Debian Update I have removed old cipher and noticed that the cron doesn't work anymore.
    When I make the file "froxlor_master_cronjob.php" executable it runs as usual again.

    I had installed Froxlor before as a package, that was uninstalled during the update of Debian.

  7. I just upgraded my main system to buster and an error occurred with "bind".
    In the "named.conf.local" the include of Froxlor was included twice.

    //
    // Do any local configuration here
    //
    
    // Consider adding the 1918 zones here, if they are not used in your
    // organization
    //include "/etc/bind/zones.rfc1918";
    
    include "/etc/bind/froxlor_bind.conf";
    include "/etc/bind/froxlor_bind.conf";

     

×
×
  • Create New...