Jump to content
Froxlor Forum

hk@

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About hk@

  • Rank
    Froxie
  • Birthday 09/14/1973

Contact Methods

  • Website URL
    kapper.net

Profile Information

  • Gender
    Male
  • Location
    Vienna, Austria
  1. Froxor -> Ressourcen -> SSL-Zertifikate -> dort das LE-Cert für den VHost gelöscht.
  2. Danke - noch eine Kleinigkeit: hätte jetzt auch das LE-Cert für den froxlor-VHost gelöscht - aber das wird anscheinend nicht wieder generiert?
  3. merci - kann das hier bestätigen, nach einem --force sind die LE-Certs wieder gut. Krieg ich eventuell einen Tipp, wie dsa LOG_WARN wegzubekommen wäre? Danke!
  4. Hallo, wir haben das gleiche Phänomen auf einer Froxlor-Installation. Gibt's da zufällig einen geordneten Fix? Danke, hk
  5. and sorry for taking the wrong forum, obviously should have posted in german here, maybe you can move this thread to the international one. thank you again.
  6. uhm, that's exactly what is (and was) running on this box, yet we got lots of mails reporting about socat.
  7. well, the acme.sh is reporting this on a 5-minute-basis because of the --tasks job and to get rid of this had to install it but any other "get rid of this" solutions would be welcome.
  8. today we suddenly got this: /usr/bin/php /var/www/html/scripts/froxlor_master_cronjob.php --tasks --debug [information] TasksCron: Searching for tasks to do [information] Running Let's Encrypt cronjob prior to regenerating webserver config files [information] Requesting/renewing Let's Encrypt certificates [information] Updating certificate for xxx.server.local [Tue Dec 31 15:47:09 CET 2019] It is recommended to install socat first. [Tue Dec 31 15:47:09 CET 2019] We use socat for standalone server if you use standalone mode. [Tue Dec 31 15:47:09 CET 2019] If you don't use standalone mode, just ignore this warning. [information] Checking for LetsEncrypt client upgrades before renewing certificates: [Tue Dec 31 15:47:08 CET 2019] Installing from online archive. [Tue Dec 31 15:47:08 CET 2019] Downloading https://github.com/Neilpang/acme.sh/archive/master.tar.gz [Tue Dec 31 15:47:09 CET 2019] Extracting master.tar.gz [Tue Dec 31 15:47:09 CET 2019] Installing to /root/.acme.sh [Tue Dec 31 15:47:09 CET 2019] Installed to /root/.acme.sh/acme.sh [Tue Dec 31 15:47:09 CET 2019] Good, bash is found, so change the shebang to use bash as preferred. [Tue Dec 31 15:47:10 CET 2019] OK [Tue Dec 31 15:47:10 CET 2019] Install success! [Tue Dec 31 15:47:10 CET 2019] Upgrade success! [Tue Dec 31 15:47:10 CET 2019] Removing cron job the box is ubuntu buster/sid after a bit of digging into the issue "apt install socat" did the trick. please add it to the required packages.
  9. Hi good news! Is there a sane way for current debian-package-users to upgrade without breaking anything (ie. upgrading using the latest tar.gz)? thx, hk
  10. 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
  11. with letsencrypt arriving for froxlor, I wonder if there is a sane way to get https for froxlor itself this way? thank you in advance, hk
  12. 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.
  13. Hi as I'm trying to find the reason behind letsencrypt not working at all, I tried to enable cronjob-debugging, I happily check the box to enable debugging, but in fact I have no idea, where those lock and hopefully logfiles might be found on the system... please advise, hk
  14. Hi after upgrading to 0.9.35.1-1+wheezy1 (DB: 201603150) and trying to enable letsencrypt I don't see any commands to create the mentioned directory in the setup process. Should this one be autocreated? (if so it doesn't seem to work) Or should I manually create it (if so please update the release notes https://forum.froxlor.org/index.php/topic/13348-release-0935-lets-encrypt-auto-update-and-more/ ) regards hk
×
×
  • Create New...