Jump to content
Froxlor Forum
  • 0

[Let's Encrypt] No registration exists matching provided key


Question

Hello,

I'm trying to use lets encrypt with froxlor. I always get an error when froxlor tried to generate the certificate.

Feb 18 19:05:03 ger2 Froxlor: [ Action cronjob] [error] Could not get Let's Encrypt certificate for test.gamerboy59.blue: No challenges received for test.gamerboy59.blue. Whole response: {"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}
From what I figured out till now this might be because of a wrong email. I didn't find anything about email stuff in the csr part of the lescript yet but I found a site discussing the error: https://www.svennd.be/lets-encrypt-on-any-linux-distro/ (one of the last parts).

 

I already tried deleting the domain and customer and set it up again but no success. Maybe you can have a look in it though it's still beta and developed anyway.

 

Regards.

Link to post
Share on other sites

19 answers to this question

Recommended Posts

  • 0

Was hat denn LetsEncrypt mit FROXLOR zu tun? Ich habe z.B. ne Debian8 Kiste auf der läuft FROXLOR out of the Box, dort habe ich auch letsencrypt von git ohne Eingriff in die Webserverkonfiguration erfolgreich testen können. Beides für sich geht also, sogar auf einer Kiste.

 

Hat FROXLOR jetzt LetsEncrypt-Support eingebaut, den ich übersehe und der streikt?

 

Aber mal ehrlich, will man wirklich aller n Monate zur Zertifizierungsstelle Wackeln und Zertifikate erneuern?

Link to post
Share on other sites
  • 0

Hello,

 

Because I'm interessted in Let's Encrypt and want to support Froxlor I upgraded my system to 0.9.35-rc1 to check the BETA state of Let's Encrypt. The result was not good.

After some houres of testing I had the same error message like in the first message.

 

Froxlor: [ Action *****] [error] Could not get Let's Encrypt certificate for *****.de: No challenges received for *****.de. Whole response: {"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}

 

I want to share my experience with other froxlor users.

 

For me the 0.9.35-rc1 was not enought. I made LE working with the git repo from today (0.9.35-rc1 (DB: 201603070)) on Debian Jessie with Apache2.4

 

  • It is important to compare the changes at the configuration files. Do not copy and paste the content of "/etc/apache2/conf-enabled/acme.conf" from the website. Use your config generator in froxlor because the PATH to your froxlor. (per example "/var/www/froxlor/.well-known/acme-challenge" instead of "/.well-known/acme-challenge")
  • Check your syslog oder Logfiles in Froxlor Webinterface (if enabled). Maybe you have to deactivate SSL Redirect temporary for the LE registration
  • I tried a lot of combinations for the default SSL Cert. My working settings are: SSL Cert and SSL Key on SSL IP/Port Settings and the same at Global SSL Settings of Froxlor
  • At Domain settings you have to change from WILDCARD to WWW or NO_ALIAS. If you enable LE but with WILDCARD you get an error message and if you press back all your ip addresses are unselected.
  • For testing I had activated the LE environment for testing at the global SSL settings. After I changed this to the Live environment I doesn't get the error message again.

This was my day from 0.9.34 to a working Froxlor installation with working Let's Encrypt. I'm happy to see that the 0.9.35 is nearly finished.

 

Thank you d00p, you hear from me again if the stable 0.9.35 is released ;)

Link to post
Share on other sites
  • 0

Hello,

 

I'm experiencing the same problem. "No registration exists matching provided key"

 

I'm using the latest git version of Froxlor ( 0.9.35.1 (DB: 201603150) ) and try the create the certs against the staging area of Let's Encrypt

 

I created the /etc/apache2/conf-enabled/acme.conf file and put the right content in. I can access https: //***.de/.well-known/acme-challenge/test.txt with no problems (except old/wrong cert warning)

 

Her is my Logfile:

Apr  9 20:00:18 servername Froxlor: [ Action kunde] [debug] Updating ***.de
Apr  9 20:00:18 servername Froxlor: [ Action kunde] [debug] letsencrypt generating new key / SAN for ***.de
Apr  9 20:00:18 servername Froxlor: [ Action kunde] [information] letsencrypt Using 'https://acme-staging.api.letsencrypt.org' to generate certificate
Apr  9 20:00:18 servername Froxlor: [ Action kunde] [information] letsencrypt Starting new account registration
Apr  9 20:00:21 servername Froxlor: [ Action kunde] [information] letsencrypt Sending registration to letsencrypt server
Apr  9 20:00:22 servername Froxlor: [ Action kunde] [information] letsencrypt Sending signed request to /acme/new-reg
Apr  9 20:00:22 servername Froxlor: [ Action kunde] [information] letsencrypt New account certificate registered
Apr  9 20:00:22 servername Froxlor: [ Action kunde] [information] letsencrypt Starting certificate generation process for domains
Apr  9 20:00:22 servername Froxlor: [ Action kunde] [information] letsencrypt Requesting challenge for ***.de
Apr  9 20:00:22 servername Froxlor: [ Action kunde] [information] letsencrypt Sending signed request to /acme/new-authz
Apr  9 20:00:23 servername Froxlor: [ Action kunde] [error] Could not get Let's Encrypt certificate for ***.de: No challenges received for ***.de. Whole response: {"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}
Apr  9 20:00:23 servername Froxlor: [ Action cronjob] [information] Let's Encrypt certificates have been updated

What I'm doing wrong? I tried with SSL forwarding and without. I also tried with alias www and with no alias at all. Has anyone an idea or tip?

Link to post
Share on other sites
  • 0

Hi

I'm stuck in quite a similar limbo, in this case the domain had a startssl cert before, then I simply activated LetsEncrypt and well - it plain doesn't work:

 

/usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --letsencrypt --debug
[information] Updating Let's Encrypt certificates
[debug] Updating xyzdomaincom
[debug] letsencrypt generating new key / SAN for xyzdomain.com
[information] letsencrypt Using 'https://acme-v01.api.letsencrypt.org'to generate certificate
[information] letsencrypt Account already registered. Continuing.
[information] letsencrypt Starting certificate generation process for domains
[information] letsencrypt Requesting challenge for xyzdomain.com
[information] letsencrypt Sending signed request to /acme/new-authz
[error] Could not get Let's Encrypt certificate for xyzdomain.com: No challenges received for xyzdomain.com. Whole response: {"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}
[information] Let's Encrypt certificates have been updated
[notice] Checking system's last guid
 
 
any help is greatly appreciated.
Link to post
Share on other sites
  • 0

tried that, tried it again, but even after removing all certificate data from the domain, deactivating ssl for the domain and then re-enabling it and setting LE enabled - it keeps telling me the same...

 

please advise,

hk

Link to post
Share on other sites
  • 0

Same problem for me,
Could not get Let's Encrypt certificate for krolika.net: No challenges received for krolika.net. Whole response: {"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}

and only for some domains.

I removed the old certificates (files and from database), still does not work.

Standalone letsencrypt-auto obtained certificates for these domains without problems.

Link to post
Share on other sites
  • 0

Same problem, nothing helps until now.

 

If I clear the lepublickey and leprivatekey I receive the following message at executing

php /var/www/froxlor/scripts/froxlor_master_cronjob.php --letsencrypt --debug
[information] Updating Let's Encrypt certificates
[debug] Updating ?????.de
[debug] Adding SAN entry: ?????.de
[debug] Adding SAN entry: www.?????.de
[information] letsencrypt Using 'https://acme-v01.api.letsencrypt.org' to generate certificate
[information] letsencrypt Starting new account registration
[information] letsencrypt Sending registration to letsencrypt server
[information] letsencrypt Sending signed request to /acme/new-reg
PHP Notice:  Array to string conversion in /var/www/froxlor/lib/classes/ssl/class.lescript.php on line 79
[error] Could not get Let's Encrypt certificate for ?????.de: Account not initialized, probably due to rate limiting. Whole response: Array
[information] Let's Encrypt certificates have been updated
[notice] Checking system's last guid

If I execute this once more, I didn't receive the Exception, but the same error:

[information] Updating Let's Encrypt certificates
[debug] Updating ?????.de
[debug] Adding SAN entry: ?????.de
[debug] Adding SAN entry: www.?????.de
[information] letsencrypt Using 'https://acme-v01.api.letsencrypt.org' to generate certificate
[information] letsencrypt Account already registered. Continuing.
[information] letsencrypt Starting certificate generation process for domains
[information] letsencrypt Requesting challenge for ?????.de
[information] letsencrypt Sending signed request to /acme/new-authz
[error] Could not get Let's Encrypt certificate for ?????.de: No challenges received for ?????.de. Whole response: {"type":"urn:acme:error:unauthorized","detail":"No registration exists matching provided key","status":403}
[information] Let's Encrypt certificates have been updated
[notice] Checking system's last guid

This also happens, if I use a never with SSL used domain.

 

Things I already did:

  • Tested the /.well-known URL: works
  • Cleared the SSL-Fields at the customer panel (for those I already had a SSL certificate for)
  • Cleared lepublickey, leprivatekey in the panel_customers table
  • Cleared domain_ssl_settings at the matching domain (for those I already had a SSL certificate for)
  • allow_url_fopen = On --> Yep
  • Checked acme.conf --> seems to work, I can reach the URL
  • Disabled SSL redirect
  • Domain-settings are not at wildcard

 

Running at Debian 7.11 with 2.2.22 and would welcome a solution or tipp.

Link to post
Share on other sites
  • 0

Okay, patched and cleared everything again. Now I get:

[information] Updating Let's Encrypt certificates
[debug] Updating ????.de
[debug] Adding SAN entry: ????.de
[debug] Adding SAN entry: www.????.de
[information] letsencrypt Using 'https://acme-v01.api.letsencrypt.org' to generate certificate
[information] letsencrypt Account already registered. Continuing.
[information] letsencrypt Starting certificate generation process for domains
[information] letsencrypt Requesting challenge for ????.de
[information] letsencrypt Sending signed request to /acme/new-authz
[information] letsencrypt Got challenge token for ????.de
[information] letsencrypt Token for ????.de saved at /var/www/froxlor/certs//.well-known/acme-challenge/BRYebjH5zEKhwJn_D1ef9REQ2VZ2FIRzTAUAkexianc and should be available at http://????.de/.well-known/acme-challenge/BRYebjH5zEKhwJn_D1ef9REQ2VZ2FIRzTAUAkexianc
[error] Could not get Let's Encrypt certificate for ????.de: Please check http://????.de/.well-known/acme-challenge/BRYebjH5zEKhwJn_D1ef9REQ2VZ2FIRzTAUAkexianc - token not available; PHP error: {"type":2,"message":"file_get_contents(http:\/\/????.de\/.well-known\/acme-challenge\/BRYebjH5zEKhwJn_D1ef9REQ2VZ2FIRzTAUAkexianc): failed to open stream: HTTP request failed! HTTP\/1.1 404 Not Found\r\n","file":"\/var\/www\/froxlor\/lib\/classes\/ssl\/class.lescript.php","line":172}
[information] Let's Encrypt certificates have been updated
[notice] Checking system's last guid

If I take a look into the acme.conf, there's the path: /var/www/froxlor/.well-known/acme-challenge, no "certs" in it.

And if I take a look into the given path it exists but it is empty. It's comprehensible that the path he want's to look up isn't reachable.

The used path was from the server configuration tool. So I fixed the path to this in the log, now it works! :)

Link to post
Share on other sites
  • 0

Here is a little something to make the whole process more easy:

 

These commands are for copy and paste use if your froxlor is installed in /var/www/froxlor/ and your froxlor database name and user are "froxlor"

 

Let's Encrypt Lib update

wget -q -O /var/www/froxlor/lib/classes/ssl/class.lescript.php "https://raw.githubusercontent.com/Froxlor/Froxlor/master/lib/classes/ssl/class.lescript.php"

empty lekeys for all panel_customers

mysqlpw=$(awk 'NR==5{print $0}' /var/www/froxlor/lib/userdata.inc.php | cut -d \' -f4)
mysql -u froxlor -p$mysqlpw
use froxlor
UPDATE panel_customers SET leprivatekey='';
quit

Cronjob + Debug

/usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --letsencrypt --debug

if successful

/usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php

DONE

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Similar Content

    • By Nicholas Wood
      Hey,
      I'm installing Froxlor on CentOS 8 and everything seems to have gone well for the most part. However the config file was supposedly saved in /tmp/xxx but I can't find that file anywhere.
      cd tmp/fxVnlJGY ... doesn't exist. Anyone know where that is?


       
       
      Running the below command from www/html folder and then reinstalling produces the same result.
      sudo chown -R apache:apache froxlor  
    • By Markus Rassow
      Nachdem gestern die ersten Zertifikate von Let's encrypt mit Froxlor 0.9.40.1 nicht mehr erneuert wurden, musste ich nun doch auch auf die aktuelle 0.10.20 umsteigen.
      Das Setting: Apache 2.4, PHP 5.6 FPM,7.2-7.4 FPM, Dovecot, Postfix, diverse Domains, teilweise nur als Mail-Domains, MySQL 5.7.31. Froxlor läuft mit PHP7.3-FPM.
      Nach Backup der Datenbanken und Dateien von Froxlor habe ich den Cron-Dienst mit systemctl cron stop gestoppt und das alte Froxlor in einen Backup-Ordner verschoben und das aktuelle Froxlor in das Domain-Verzeichnis meines Servers abgelegt. Die userdata.inc.php aus dem alten Froxlor/lib ins neue Froxlor/lib kopiert und dann Froxlor aufgerufen.
      Froxlor meldet die Notwendigkeit, die Datenbank anzupassen und fragt, ob Domains durch Froxlor verifiziert werden sollen: ja. Upgrade läuft problemlos durch.
      Nachdem ich den Cron-Dienst wieder mit systemctl cron start gestartet habe, sind für ein paar Minuten noch alle Domains erreichbar, dann killt Froxlor alle bestehenden SSL-Dateien und stirbt selbst. Apache startet nicht mehr.
      Grund: keine SSL-Zertifikate mehr vorhanden. Nach manuellem Ausführen des Master-Cronjob von der Shell aus scheint zunächst auch alles zu funktionieren. Zertifikate wurden von Let's encrypt geholt - aber nicht in den bisherigen Ordner unter /etc/ssl/froxlor-custom/sub.domain.crt abgelegt sondern in einen Unterordner mit dem jeweiligen Domainnamen. Die Dateinamen der Zertifikate lauten wie bisher auf .crt .Dann scheitert alles weitere. Die Zertifikate werden nicht gefunden, die vHosts nicht angelegt. Apache2 startet zwar, aber nur mit den normalen vHosts. Die SSLs sind weg. Also das Script erneut aufgerufen mit Zusatz --verbose und in ein Logfile geschrieben (Usernamen, IPs und Domainnamen geändert):
      /usr/bin/php7.3 -q /customers/web/example/kap.example.de/scripts/froxlor_master_cronjob.php --tasks
      [Mo 10. Aug 14:33:00 CEST 2020] It is recommended to install socat first. [Mo 10. Aug 14:33:00 CEST 2020] We use socat for standalone server if you use standalone mode. [Mo 10. Aug 14:33:00 CEST 2020] If you don't use standalone mode, just ignore this warning. Nach diversen Fehlermeldungen also schnell noch socat installiert mit:
      apt install socat
      Dann erneut das Script aufgerufen
      /usr/bin/php7.3 -q /customers/web/example/kap.example.de/scripts/froxlor_master_cronjob.php --tasks --force --debug
       
      [information] TasksCron: Searching for tasks to do [information] TasksCron: Task10 started - setting filesystem quota [information] Running Let's Encrypt cronjob prior to regenerating webserver config files [information] Checking for LetsEncrypt client upgrades before renewing certificates: [Mo 10. Aug 14:49:42 CEST 2020] Installing from online archive. [Mo 10. Aug 14:49:42 CEST 2020] Downloading https://github.com/acmesh-official/acme.sh/archive/master.tar.gz [Mo 10. Aug 14:49:43 CEST 2020] Extracting master.tar.gz [Mo 10. Aug 14:49:43 CEST 2020] Installing to /etc/ssl/froxlor-custom [Mo 10. Aug 14:49:43 CEST 2020] Installed to /etc/ssl/froxlor-custom/acme.sh [Mo 10. Aug 14:49:43 CEST 2020] Good, bash is found, so change the shebang to use bash as preferred. [Mo 10. Aug 14:49:44 CEST 2020] OK [Mo 10. Aug 14:49:44 CEST 2020] Install success! [Mo 10. Aug 14:49:44 CEST 2020] Upgrade success! [Mo 10. Aug 14:49:44 CEST 2020] Installing cron job 4 0 * * * "/customers/home/root/.acme.sh"/acme.sh --cron --home "/customers/home/root/.acme.sh" > /dev/null [information] Requesting 42 new Let's Encrypt certificates [information] Creating certificate for example.de [information] Adding common-name: example.de [information] Adding SAN entry: www.example.de [information] Validating DNS of example.de [information] Validating DNS of www.example.de [debug] https://github.com/acmesh-official/acme.sh v2.8.6 [Mo 10. Aug 14:49:45 CEST 2020] Domains not changed. [Mo 10. Aug 14:49:45 CEST 2020] Skip, Next renewal time is: Fr 9. Okt 12:33:15 UTC 2020 [Mo 10. Aug 14:49:45 CEST 2020] Add '--force' to force to renew. [error] Could not find file 'example.de.cer' in '/etc/ssl/froxlor-custom/example.de/' [error] Could not find file 'ca.cer' in '/etc/ssl/froxlor-custom/example.de/' [error] Could not find file 'fullchain.cer' in '/etc/ssl/froxlor-custom/example.de/' [error] Could not get Let's Encrypt certificate for example.de: [information] Let's Encrypt certificates have been updated [information] apache::createIpPort: creating ip/port settings for 1.2.3.4:80 [debug] 1.2.3.4:80 :: inserted listen-statement [debug] 1.2.3.4:80 :: inserted vhostcontainer [information] apache::createIpPort: creating ip/port settings for 1.2.3.4:443 [debug] 1.2.3.4:443 :: inserted listen-statement [debug] System certificate file "" does not seem to exist. Disabling SSL-vhost for "mail.example.de" [error] mail.lightserve.de :: empty certificate file! Cannot create ssl-directives [debug] 1.2.3.4:443 :: inserted vhostcontainer [information] apache::createVirtualHosts: creating vhost container for domain 1, customer ichselber [debug] System certificate file "" does not seem to exist. Disabling SSL-vhost for "example.de" [error] rassow.de :: empty certificate file! Cannot create ssl-directives --- und so sieht es dann auch für alle Domains aus ---
      [information] apache::writeConfigs: rebuilding /etc/apache2/sites-enabled/ [information] apache::writeConfigs: rebuilding /etc/apache2/htpasswd/ [information] apache::writeConfigs: rebuilding /etc/apache2/sites-enabled/ [information] Froxlor\Cron\Http\ApacheFcgi::reload: running /etc/init.d/php5.6-fpm reload [information] Froxlor\Cron\Http\ApacheFcgi::reload: running /etc/init.d/php7.2-fpm reload [information] Froxlor\Cron\Http\ApacheFcgi::reload: running /etc/init.d/php7.3-fpm reload [information] Froxlor\Cron\Http\ApacheFcgi::reload: running service php7.4-fpm restart [information] Froxlor\Cron\Http\ApacheFcgi::reload: reloading Froxlor\Cron\Http\ApacheFcgi [notice] Checking system's last guid So endet der erste Durchlauf
      Aus irgend einem Grund sucht das Script nicht wie bisher nach .crt -Zertifikaten sondern nach .cer. In den neu erstellten Unterordnern von /etc/ssl/froxlor-custom finden sich aber z.B. /etc/ssl/froxlor-custom/example.de/mail.example.crt. Nach langer, langer Suche bin ich dahinter gekommen, dass das acme-Script /root/.acme.sh/acme.sh die Schuld daran trägt. Bei mir lag dieses in der Version 2.8.6 vor und legte die Zertifikate als .crt an. Nach einem Update auf 2.8.7 läuft das obige Script nun komplett durch und erstellt die Zertifikate mit dem korrekten Dateinamen. Nun sollten die Configs für Apache auch korrekt erzeugt werden, meint man. Aber leider falsch.
      [information] TasksCron: Searching for tasks to do [information] TasksCron: Task10 started - setting filesystem quota [information] Running Let's Encrypt cronjob prior to regenerating webserver config files [information] Checking for LetsEncrypt client upgrades before renewing certificates: [Mo 10. Aug 15:45:22 CEST 2020] Installing from online archive. [Mo 10. Aug 15:45:22 CEST 2020] Downloading https://github.com/acmesh-official/acme.sh/archive/master.tar.gz [Mo 10. Aug 15:45:23 CEST 2020] Extracting master.tar.gz [Mo 10. Aug 15:45:23 CEST 2020] Installing to /etc/ssl/froxlor-custom [Mo 10. Aug 15:45:23 CEST 2020] Installed to /etc/ssl/froxlor-custom/acme.sh [Mo 10. Aug 15:45:23 CEST 2020] Good, bash is found, so change the shebang to use bash as preferred. [Mo 10. Aug 15:45:24 CEST 2020] OK [Mo 10. Aug 15:45:24 CEST 2020] Install success! [Mo 10. Aug 15:45:24 CEST 2020] Upgrade success! [Mo 10. Aug 15:45:24 CEST 2020] Installing cron job 4 0 * * * "/customers/home/root/.acme.sh"/acme.sh --cron --home "/customers/home/root/.acme.sh" > /dev/null [information] Requesting 42 new Let's Encrypt certificates [information] Creating certificate for example.de [information] Adding common-name: example.de [information] Adding SAN entry: www.example.de [information] Validating DNS of example.de [information] Validating DNS of www.example.de [debug] https://github.com/acmesh-official/acme.sh v2.8.7 [Mo 10. Aug 15:45:25 CEST 2020] Create account key ok. [Mo 10. Aug 15:45:25 CEST 2020] Registering account [Mo 10. Aug 15:45:26 CEST 2020] Registered [Mo 10. Aug 15:45:26 CEST 2020] ACCOUNT_THUMBPRINT='GIEw62wW9oLxZqEaVe-NxhNQKyQbOBDjBWGw8JoZy_c' [Mo 10. Aug 15:45:26 CEST 2020] Creating domain key [Mo 10. Aug 15:45:27 CEST 2020] The domain key is here: /etc/ssl/froxlor-custom/example.de/example.de.key [Mo 10. Aug 15:45:27 CEST 2020] Multi domain='DNS:example.de,DNS:www.example.de' [Mo 10. Aug 15:45:27 CEST 2020] Getting domain auth token for each domain [Mo 10. Aug 15:45:30 CEST 2020] Getting webroot for domain='example.de' [Mo 10. Aug 15:45:30 CEST 2020] Getting webroot for domain='www.example.de' [Mo 10. Aug 15:45:30 CEST 2020] Verifying: example.de [Mo 10. Aug 15:45:33 CEST 2020] Pending [Mo 10. Aug 15:45:44 CEST 2020] Success [Mo 10. Aug 15:45:44 CEST 2020] Verifying: www.example.de [Mo 10. Aug 15:45:47 CEST 2020] Success [Mo 10. Aug 15:45:47 CEST 2020] Verify finished, start to sign. [Mo 10. Aug 15:45:47 CEST 2020] Lets finalize the order, Le_OrderFinalize: https://acme-v02.api.letsencrypt.org/acme/finalize/einpaarzahlen123456789 [Mo 10. Aug 15:45:48 CEST 2020] Download cert, Le_LinkCert: https://acme-v02.api.letsencrypt.org/acme/cert/einhashwert123456789 Certificate: Data: Version: 3 (0x2) Serial Number: 04:ba:42:aa:c3:e2:99:b0:d4:96:55:e8:44:69:b7:85:a8:e7 Signature Algorithm: sha256WithRSAEncryption
      --- hier folgt das Zertifikat ---
      -----END CERTIFICATE----- [Mo 10. Aug 15:45:49 CEST 2020] Your cert is in /etc/ssl/froxlor-custom/example.de/example.de.cer [Mo 10. Aug 15:45:49 CEST 2020] Your cert key is in /etc/ssl/froxlor-custom/example.de/example.de.key [Mo 10. Aug 15:45:49 CEST 2020] The intermediate CA cert is in /etc/ssl/froxlor-custom/example.de/ca.cer [Mo 10. Aug 15:45:49 CEST 2020] And the full chain certs is there: /etc/ssl/froxlor-custom/example.de/fullchain.cer [error] Could not find certificate-folder '/root/.acme.sh/example.de/' [error] Could not get Let's Encrypt certificate for example.de: https://github.com/acmesh-official/acme.sh  
      Und hier folgt dasselbe Problem wie zuvor. Die Zertifikate liegen nun korrekt in den Unterordnern. Warum werden diese nun im Unterordner von /root/.acme.sh/ gesucht?
      Bis hierher bin ich in den vergangenen 16 Stunden vorgedrungen.
      Nun bitte ich um hilfreiche Tipps, wie und wo ich weiter machen soll.
    • By logicbloke
      Hi,
      I'm just wondering what the difference is between the following 2 folders:
      Why is froxlor installing acme.sh cron everytime it runs at 3am everyday especially since the 5-min let's encrypt froxlor cron is already in place? Also, all my db config points to /etc/ssl/froxlor-custom for the domains and all keys/certificates inside that folder have a different md5 from the ones under /root/.acme.sh/, so I'm wondering what's with the mismatch? Are we updating certificates for domains twice?
       
      If anyone can shed some more light on this, it will be very much appreciated.
       
      Many thanks!
    • By Matteo
      I am installing Froxlor 10 on Debian 10 with MySQL and Apache2 on a home web server.
      I get to the installation screen by going to localhost/froxlor and I get
      "Welcome to Froxlor"
      "It seems that Froxlor has not been installed yet."
      "Click on the link below to start the installation."
      I click "Start Install" and get to this page:
      Checking system requirements...
      All requirements are satisfied [green] and this is at the bottom:
      All requirements are satisfied
        Clicking the link to continue takes me to:
      Database connection
      MySQL-Hostname:
      Database name:
      Username for the unprivileged MySQL-account:
      Password for the unprivileged MySQL-account:
      Username for the MySQL-root-account:
      Password for the MySQL-root-account:
       
      Administrator Account
      Administrator Username:
      Administrator Password:
      Administrator-Password (confirm):
      Enable the official newsfeed
      (https://inside.froxlor.org/news/):
       
      Server settings
      Server name (FQDN, no ip-address):
      Server IP:
      Webserver Apache 2.4:
      HTTP username:
      HTTP groupname:
       
      [With all the correct fields and passwords filled in...]
      Clicking the [continue] button takes me to the success screen...:
      Froxlor install - setup
      Checking MySQL-root access... OK Creating backup of old database... OK  Preparing database... OK Creating database and username... OK Testing if database and user have been created correctly... OK Importing data... OK Adjusting settings... OK Inserting new values... OK Creating admin-account... OK Creating configfile... File was saved in /... Froxlor was installed successfully.
        Clicking the login button takes me to this:
      "Welcome to Froxlor"
      "It seems that Froxlor has not been installed yet."
      "Click on the link below to start the installation."
      And the process starts all over again...
      It doesn't matter which browser I use - Chrome, Firefox - the result is the same.
      I am a new Linux user, so some help would be appreciated.
      Thank you.
       
    • By Marcel -//- AdSoleWare
      Hello.
      I manually installed Froxlor on Debian 8 and tried setting up. i installed php 7.3 in as it was the only missing point. i restarted apache2 and now it wont start. I need help
       
      Error Log:
       
×
×
  • Create New...