Jump to content
Froxlor Forum

d00p

Administrators
  • Content Count

    7871
  • Joined

  • Last visited

  • Days Won

    41

Everything posted by d00p

  1. Sorry, no idea what you are doing there, if wanted, I can take a look at that via shell. just sens me a PM with the credentials (root!) and I can see what's up there
  2. Du meinst ohne dedizierte IP für die Domain? Ja na klar, Browser können das, nennt sich SNI, siehe https://de.wikipedia.org/wiki/Server_Name_Indication Und nein, das geht NICHT wenn Let's Encrypt für diese Domain aktiviert ist, denn dann kümmert sich froxlor ja automatisch selbst um das Zertifikat. Aktivierst du SSL für eine Domain aber lässt Let's Encrypt deaktiviert, hast du als Kunde in der Domain-Übersichtsliste rechts für entsprechende Domains einen Button "SSL Editor" wo die Zertifikatsdaten reinkopiert werden können. Macht nix, gabs so auch schon alles in 0.9 und sollte problemlos funktionieren
  3. Well did you restart apache after the changes? Whatelse lies in /etc/apache2/sites-enabled/? When in doubt, grep "/var/www/html" in all /etc/apache2 to find out where this might be set
  4. d00p

    Debian 10 (Buster)

    ja dann lief da vllt nur der entsprechende cron nicht, der schreibt dateien ja nur wenn was geändert wurde, also wenn du da eine installation komplett wegziehst macht es durchaus sinn da den cron manuell mit --force --debug auszuführen um alles wieder anzulegen
  5. d00p

    Debian 10 (Buster)

    Hattest du denn auf dem alten Server libnss-mysql/libnss-extrausers verwendet? Das wäre die Schnittstelle zwischen Datenbank und System was die User angeht. Ebenso hast du bei den Datenbanken hoffentlich auch an die mysql-Datenbank gedacht in der sich die ganzen Datenbankbenutzer und Passwörter verstecken, sonst sind zwar die Kundendatenbanken da, aber die Rechte dafür nicht.
  6. ??? That's the full content of /etc/apache2/sites-enabled/000-default???
  7. That's definitely not everything in that file (I hope)
  8. So what does you 000-default vhost look like?
  9. I can reproduce that, can you please open an issue on github, I'll look into that tomorrow
  10. There is no explicit wiki entry, just edit /etc/apache2/sites-enabled/000-default and change /var/www/html to /var/www
  11. and there is your problem, that's 1) by far not a complete froxlor installation, you are missing TONS of files 2) not owned by www-data, hence the problem creating the userdata.inc.php file 3) when installing via deb-package, it's being installed to /var/www/ and not /var/www/html - adjust your default vhost as stated in the wiki entry
  12. Okay, weird, that looks just fine, both are www-data. And you are sure you pointed the default vhost to /var/www/ instead of /var/www/html/? Because your standard index.html looks more like it points to /var/www/html - do you by any chance have /var/www/html/froxlor/? What's the ownership there?
  13. Then it's either the wrong user or you did something wrong with the chown. Bs sure to use the user the Webserver runs as, otherwise it cannot create files or write to the directory. What do the following two commands output? # ls -la /var/www/ # ps faux | grep apache
  14. That is correct, now did you especially follow part 4? And then as said from part 3 on in the tarball wiki entry? -> https://github.com/Froxlor/Froxlor/wiki/Install-froxlor-from-tarball Also, be SURE the ubuntu package set the ownership correctly to www-data for /var/www/froxlor if not done already
  15. Well you did not copy the lib/userdata.inc.php file as stated thus froxlor does not know about its database hence installation. Please just follow the installation manual in our wiki, it's all in there and if followed correctly you will not have any issues
  16. Well where did you install froxlor to? That's something you should know instead of blindly copy'n'pasting and running commands posted here
  17. chown -R www-data:www-data /var/www/froxlor
  18. If the file.is really saved there, you as root should be able to copy it - to avoid that extra step, just chown your Froxlor directory with www-data user
  19. Seemed about right, you somehow missed index.php as DirectoryIndex, if you open /install/index.php directly it works, but seems.to.be fixed now as I see the index right away
  20. Yup, looks about right, the $cert_mode variable is not re-initialized to its initial state 'issue' in the foreach-loop, following patch should fix that: diff --git a/lib/Froxlor/Cron/Http/LetsEncrypt/AcmeSh.php b/lib/Froxlor/Cron/Http/LetsEncrypt/AcmeSh.php index 545ad323..eb620603 100644 --- a/lib/Froxlor/Cron/Http/LetsEncrypt/AcmeSh.php +++ b/lib/Froxlor/Cron/Http/LetsEncrypt/AcmeSh.php @@ -243,9 +243,11 @@ class AcmeSh extends \Froxlor\Cron\FroxlorCron // customer domains $certrows = $needRenew ? $needRenew['customer_ssl'] : array(); - $cert_mode = 'issue'; foreach ($certrows as $certrow) { + // initialize mode to 'issue' + $cert_mode = 'issue'; + // set logger to corresponding loginname for the log to appear in the users system-log $cronlog = FroxlorLogger::getInstanceOf(array( 'loginname' => $certrow['loginname'], Will be part of next release (0.10.6)
  21. Meaning? Is there an entry for that domain or not? Might be correct after all, need to check later when back home. Yes, Froxlor checks the date from its entries in the database. No, even if updating from 0.9 to 0.10.5 all required changes are being executed. Yes that what I meant earlier with "might be correct after all"
  22. Well Looks like it still wants to renew, so you did not delete completely, check the froxlor SSL certificates page (or manually check the domain_ssl_settings table looking for entries with the corresponding domain id)
  23. Just reproduced that: removed ssl-certificate in froxlor, removed acme.sh certificate, removed acme.sh directory of that domain: root@froxsrv:~# php /var/www/html/froxlor/scripts/froxlor_master_cronjob.php --force --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] Creating certificate for demo.froxlor.org [information] Adding SAN entry: demo.froxlor.org [information] Adding SAN entry: www.demo.froxlor.org [information] Checking for LetsEncrypt client upgrades before renewing certificates: [So 10. Nov 10:03:13 CET 2019] Installing from online archive. [So 10. Nov 10:03:13 CET 2019] Downloading https://github.com/Neilpang/acme.sh/archive/master.tar.gz [So 10. Nov 10:03:14 CET 2019] Extracting master.tar.gz [So 10. Nov 10:03:14 CET 2019] Installing to /root/.acme.sh [So 10. Nov 10:03:14 CET 2019] Installed to /root/.acme.sh/acme.sh [So 10. Nov 10:03:14 CET 2019] Good, bash is found, so change the shebang to use bash as preferred. [So 10. Nov 10:03:14 CET 2019] OK [So 10. Nov 10:03:14 CET 2019] Install success! [So 10. Nov 10:03:14 CET 2019] Upgrade success! [So 10. Nov 10:03:15 CET 2019] Removing cron job [debug] [So 10. Nov 10:03:15 CET 2019] Creating domain key [So 10. Nov 10:03:16 CET 2019] The domain key is here: /root/.acme.sh/demo.froxlor.org/demo.froxlor.org.key [So 10. Nov 10:03:16 CET 2019] Multi domain='DNS:demo.froxlor.org,DNS:www.demo.froxlor.org' [So 10. Nov 10:03:16 CET 2019] Getting domain auth token for each domain [So 10. Nov 10:03:19 CET 2019] Getting webroot for domain='demo.froxlor.org' [So 10. Nov 10:03:19 CET 2019] Getting webroot for domain='www.demo.froxlor.org' [So 10. Nov 10:03:19 CET 2019] demo.froxlor.org is already verified, skip http-01. [So 10. Nov 10:03:19 CET 2019] www.demo.froxlor.org is already verified, skip http-01. [So 10. Nov 10:03:20 CET 2019] Verify finished, start to sign. [So 10. Nov 10:03:20 CET 2019] Lets finalize the order, Le_OrderFinalize: https://acme-v02.api.letsencrypt.org/acme/finalize/xxx/yyy [So 10. Nov 10:03:21 CET 2019] Download cert, Le_LinkCert: https://acme-v02.api.letsencrypt.org/acme/cert/asdasdasd [So 10. Nov 10:03:22 CET 2019] Cert success. -----BEGIN CERTIFICATE----- ... -----END CERTIFICATE----- [So 10. Nov 10:03:22 CET 2019] Your cert is in /root/.acme.sh/demo.froxlor.org/demo.froxlor.org.cer [So 10. Nov 10:03:22 CET 2019] Your cert key is in /root/.acme.sh/demo.froxlor.org/demo.froxlor.org.key [So 10. Nov 10:03:22 CET 2019] The intermediate CA cert is in /root/.acme.sh/demo.froxlor.org/ca.cer [So 10. Nov 10:03:22 CET 2019] And the full chain certs is there: /root/.acme.sh/demo.froxlor.org/fullchain.cer [information] Updated Let's Encrypt certificate for demo.froxlor.org [information] Let's Encrypt certificates have been updated works just fine
  24. Also, do not manually call --tasks or --letsencrypt, just use --force --debug to be sure that regeneration tasks are inserted (because --tasks does nothing without tasks and --letsencrypt does nothing else but check for renew and inserts a tasks for --tasks)
×
×
  • Create New...