Jump to content
Froxlor Forum


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About hk@

  • Rank
  • Birthday 09/14/1973

Contact Methods

  • Website URL

Profile Information

  • Gender
  • 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 sta
  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 cert
  13. Hi actually this fix is missing the removal of the compromised logfiles, otherwise it fixes future logging of passwords, but not the access to the logfile that has been compromised. I ask you to add a proper .htaccess-block for the logs-directory _and_ remove the logfiles from there as they - if kept - are still a security-risk in the current release. thx hk
  • Create New...