Systems where we’d already fixed the broken crontab jobs for backup and LE Cert renewal are broken again. This is frankly crazy-making incompetence. Known issues coming back up indicates a gross failure in testing. Is this just how it’s going to be?
What version of systems are these? That would be helpful.
This has been reported here ad nauseum for YEARS now. And it continues. It spans many module versions and full FreePBX versions. Everything we support is on v16 due to the onerous and unprecedented process to get to v17, and ongoing reports of “restore from backup” debacles during that process.
To clarify, you’ve previously modified the stock crontab jobs as generated by FreePBX ? So that when the system updates now, it conflicts with your modifications ?
No. I did not do that. To fix it we’ve deleted the backup job and recreated and deleted the cert and setup new.
Could you please raise Github jira and share below details so we can try to investigate further -
- your cron job output to see how many jobs you are running ?
- module updates information like how many modules got updated and if by chance any idea from older version its good to know else no issue.
- your systems freepbx logs so we can see module updates logs
Best Regards
Kapil
Nope. I’ve done such things over and over for well over a decade. All I have ever gotten is “it’s you, not the code” and a bunch of wasted time.
As often as this happens and has been reported here, if you cannot replicate you aren’t testing remotely close to thoroughly.
I just had this happen again as well.
I followed a tutorial to manually add it back in, and it got erased again.
My certs never renew automatically. I always have to update them myself.
I’m running 16 for the same reason. It’s a real pain.
1 Like
Any errors or output in logs or warnings?