I am running 7.3.14 at the moment and on my SiteGound server it's 7.3.16 so I think that if I upgrade I might get rid of my bug manifestation on my Turnkey Linux VM! :-)

I have a working site at SiteGround, it runs on WP 5.4.2. When I run it locally on my turnkey VM with 5.4 there is only a white page both in root and wp-admin, and with debug true I see the create_function warnings.

I'm setting up a small Proxmox cluster, and had intended to deploy several TKL appliances on it, however I've run into an issue with Webmin.

I've done some troubleshooting, and narrowed the issue down to systemd, presumably the unit file.

If launched by systemd, it'll run for a few seconds before dying, then relaunch, then rinse and repeat.

If executed manually (/usr/share/webmin/miniserv.pl /etc/webmin/miniserv.conf), it'll run just fine and continue to work.

I've quickly set up an Observium VM using the v16 ova and in parallel to it I've deployed a Core VM using also the v16 ova.

Platform is ESXi 6.5.

Core works nicely, but with Observium I have a no-go situation, still problems finding a way to boot.

I've attached a screenshot-comparison of both VMs, deployed in the same ESXi server, in the same Datastore.

Differences I've noticed:

Hello,

I've tried downloading turnkey-observium-16.0-buster-amd64.ova 3 times and installed in ESXi 5.5 and ESXi 6.5.

In both cases it stops at the boot in the GRUB menu.

error: file '/boot/vmlinuz-4.19.0-8-amd64' not found

How can I correct it?

BR

Udo

we have a few sites running on a wordpress turnkey. One of the sites is a multi-site from IIS I brought over. i have the apache server set for address of efg.com and servername of efg.com pointing to the directory it should. i have an ServerAlias of www.efg.com in the directive file. The problem is if i just go to efg.com it goes to a different server listed in the virtual hosts list, or will go to the main site of the multisite which isnt even created in the virtual host.

Hello, I'm deploying a Turnkey 16 box (Mattermost) on a provider which doesn't use DHCP, instead they have their users enter static IP information.

This is how my install goes with Turnkey 16. Not sure how much of this is intentional, just describing the process to the best of my recollection.

* the lack of networking isn't mentioned prior to the first reboot

Am I blind, or is there no issue tracker for the various Turnkey repos on Github?

Where do we file bug reports?

http://mirror.turnkeylinux.org/turnkeylinux/images/iso/turnkey-mattermos...

this is returning a 404, perhaps other things are also broken?

Cannot load web gui for next cloud using tunrkey nextcloud 16 after first install. I am unable to start webmin service

errors I have are

stunnel4@webmin.service: Start request repeated too quickly.

stunnel4@webmin.service: Failed with result 'exit-code'.

Failed to start Universal SSL tunnel for network daemons (webmin).