Jump to content
Froxlor Forum

halfgaar

Members
  • Content Count

    26
  • Joined

  • Last visited

  • Days Won

    1

halfgaar last won the day on June 27

halfgaar had the most liked content!

Community Reputation

-3 Poor

About halfgaar

  • Rank
    Froxie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I saw the Github notification. I didn't have the opportunity to test. Anyway, that fix worked.
  2. I'm still not 100% on the original issue I had, but it's probably related to this ticket I just made.
  3. I'm confused. That's how it's run from the crontab /etc/cron.d/froxlor. See my original post. But, it doesn't seem to do anything (the files in /etc/ssl/froxlor were not updated), until I add --debug. And even then, it keeps thinking the domain 'thedomain.nl' (and only this one) has a new certificate, every time I run it. Once dealt with, I expect it not to show up as 'Updated Let's Encrypt certificate' anymore.
  4. Something still amiss. The certificate wasn't updated. It was created in /root/.acme.sh, but not in /etc/ssl/froxlor. It didn't do anything, until I ran the cronjob with the --debug flag. That's something that seems to happen more often to me (requiring --debug to make the jobs work). When I run it multiple times, now, I see it still wants to pick up that domain again and again: root@myfroxlorserver: /etc/cron.d <master> # /usr/bin/php -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --letsencrypt --debug [information] Updated Let's Encrypt certificate for thedomain.nl [in
  5. I had just finished writing it 😢 😀.
  6. I had checked that actually, there is no cron for root. There are no crons in /var/spool/cron/crontabs. I just ran 'acme.sh --install-crobjob' by hand, and it created a cron job. runIssueFor() in AcmeSh.php runs 'acme.sh --install-crobjob' on issue. So in other words, when you upgrade to the Froxlor version with the new acme system, you won't get the cronjob until you issue new certificates?
  7. My monitoring alerted me that SSL certificates from Froxlor sites are expiring. As in, the first one triggered my warning level of 24 days. I see the PHP code only loads certificates from disk now, and a recent commit message says that acme.sh is supposed to renew? Am I missing a cron? My /etc/cron.d/froxlor is: # 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/php -q /var/www/froxlor/scripts/fr
  8. You never know what apt restarts, and also because of reboots, I prefer to make it permanent. Froxlor went haywire last time running on php5, so I wanted to be sure this time. I communicated the PHP5 to 7.3 upgrade to users before the upgrade, so I was covered there. I could, perhaps, but I don't have any special reason to use it (. I just didn't want to tag a Courier-to-dovecot migration to my upgrade as well. People installing fresh would like not care, but people upgrading like me do. But, I've found very little comments that people do. This forum post may help the few who d
  9. Because I had to revert a failed upgrade some time ago from Debian 8 with Froxlor 0.9 with Courier IMAP/POP3, I learned some things that may be relevant to others upgrading, so I thought I'd post them. Important pre-steps: Tip: put /etc all in git. Disable all lines in /etc/cron.d/froxlor before doing anything. When upgrading Debian, it always leaves the old PHP versions around. You have to explicitly remove them after 'dist-upgrade'. Having php5 still around, unknowingly, was one of my previous problems. See your installed packages with 'aptitude search php | grep ^i'
  10. What is the recommended upgrade path when running Debian 8 (Jessie) with Froxlor 0.9.40.1-1+jessie1? Upgrade Debian twice, then add the repo 'deb https://deb.froxlor.org/debian buster main', then upgrade Froxlor? Also, is that repo still only 'testing', as was mentioned here (earlier in this thread)? I will make an VPS snapshot so I have some room for experimentation (I can revert in a pinch), but knowing what to expect is better of course
  11. It now says: # cat 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/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --tasks 1> /dev/null 0 0 * * * root /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --traffic 1> /dev/null 5 0 * * * root /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --used_ti
  12. /etc/cron.d/froxlor states that it is auto-generated, but mine is rather old: # lh froxlor -rw-r----- 1 root root 983 Oct 6 2014 froxlor It needs to have the 'php /var/www/froxlor/scripts/froxlor_master_cronjob.php --letsencrypt' call. I can add it, but isn't it supposed to be included automatically?
×
×
  • Create New...