Hi, everyone. I recently learned that the cron job that ships with TKL WordPress (and perhaps other appliances) was not working for my sites. I learned this because I kept getting error messages ("You have some tasks that are overdue, etc.") and automatic updates were not being installed. "Surely, this cannot be correct," I thought. "TKL disables wp_cron by default, which makes sense for many reasons, but they use a system cron instead." 

All of that is true, but I was wrong. This is the default cron job:

Hi, I want to use this as VM to install Grocy which requires PHP 8

As I faced the tragic in the NextCloud iso with PHP 8

I mayby better loock for another image for this project if this is the same here!

Don't start Delayed_job on Canvas LMS (on all 16 subversions),

I am developer on Rails.

Bun can not run delayed_jobs on the Canvas.

  Very much trace errors. And don't work the process in Rails.  

Hi, there is a system hint in overview:

• You are currently running PHP 7.4.33. Upgrade your PHP version to take advantage of performance and security updates provided by the PHP Group ↗ as soon as your distribution supports it.

I intend to try out The App Custom menu

Requirements:

RE: Disable Email for: System monitoring and security alerts

How do I edit/stop the formentioned?

My TKLDev instance seems to be downloading OS updates and the like over and over again. Might this have something to do with squid-deb-proxy-client being installed? I typically install it on all my Debian VMs as I have an instance of apt-cacher-ng running for my network. But with this latest TKLDev instance, it seems like neither cache is getting used - not TKLDev's and not my apt-cacher-ng instance.

On a virtual machine with a private IPv4, and a public IPv6 interfaces/addresses, running the gitea appliance

root@g ~# turnkey-version
turnkey-gitea-17.1-bullseye-amd64
root@g ~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

Dehydrated fails to obtain a cert with a time out error.

Investigation shows that the python script that Dehydrated spawns is only listening on 0.0.0.0:80

Argh! I just accidentally deleted a forum user account for a fairly new user named "Jay Hova". Jay had posted a question, which I still intend to answer - even though I'm unsure if Jay will see it?!

I'm using proxmox 7.1-7, Turnkey Linux WordPress containers 17.1-1. I have nginx proxy manager in front. No errors in Nginx logs. The issue started when I moved my websites to 17.1 from 16.1. I made the move because I needed php7.4. I still have 1 website on 16.1 and it works fine on all devices. Getting connection refused. Like it can't parse the response. I spun up a brand new container with no plugins installed to test, it does the same thing. I assume it has something to do with TLS. 

Apache System logs show this when an iOS device tries to connect:

Hi there, i am on a need of update the PHP Version of my Proxmox LXC (turnkey-ngnix-php-fastcgi 17.1.1)  from php 7.4 to 8 or 8.1, any guide to follow? help is much appreciated.