I just verified this on a Hub 17.x Joomla3 install.  I know that it is frequent or always with Odoo installs.

Basically when you set your new server up and assign passwords etc,  Those passwords do not work after the install and you try to login for the first time.

I thought perhaps a further restart was needed, but in this instance, still no.

Good thing system is suggesting and makes it easy to assign a Cert to hub builds.  This does allow Putty Logins.

In Putty, once logged in, command

turnkey-init 

I have been "trying" to move a Joomla3 TKL15.3 Joomla build up to a Joomla3 TKL17.x build.

Two times now I have run

tklbam restore (backup number)

Lots of things move and when I log in to the backend it looks like a mix of versions.

First thing that strikes me though is that Webmin indicates
Debian 11 before the restore.  Debian 9 after the restore.

Hello TKL Team!

Unfortunately my LetsEncrypt stopped working and I can't migrate (first try anyway) my Joomla 3 Server running TKL 15.5 - Stretch.

Hi team,

I’ve got a turnkey linux wordpress VM running, and I want to put it behind my NGINX reverse proxy, as I’ve done with many of my other websites/appliances.

For some reason the Turnkey Linux Wordpress server is inaccessible outside the LAN using NGINX, with the exact same configuration that works for non-Turnkey Linux Wordpress websites.

I don’t know what it is about the Turnkey Linux instance that seems to break the reverse proxy, and so I’m hoping you might be able to steer me in the right direction.

Kind regards,

What is the easier way to see who is connected?

I can look at the  /var/log/openvpn/server.log using the web gui but its not live its ok data.

Is there a built in file that gets updated with who is connected?   If not it should be part of the installation package.

Hi

I wonder if you can help? I have 2 wordpress appliances running, the current version and the previous version. I'm getting an issue with the current version detailed below:

When sending emails via a host I have a username and password configured in the SMTP Authentication And Encryption section of Postfix.

The postfix server v3.4.14 works fine but in the same configuration on the v3.5.13 postfix server I get the error  warning: SASL authentication failure: No worthy mechs found.

I have a mergerfs/snapraid pool on an Ubuntu 22.04 Lts server, and I need it to be recognized by nextcloud.

In the nextcloud container, I activated the external storage, but when trying to configure it, I get a message that I don't have permission.  But the only existing account in the container is the administrator, who in my understanding should have full power over it.

Note: Google translation, I speak Portuguese.

Hi All,

This is my follow up from this thread: https://www.turnkeylinux.org/comment/55352#comment-55352

I  wanted to upgrade my nextcloud turnkey linux container on proxmox to the latest version 17.2. I am a new to all this, so apologies in advance.

I did run the command previously suggested and found that I am running version 17.1.

Hi everyone.

I already install turnkey-mediaserver.. every was fine..

but i dont know what is the default user and pass for console....either the web

can helpme pls?

Not sure how to fix the SSL for TK Wordpress or Bullseye (17.1).

Not a great linux guy to figure this one out, but if i had a little help, it would be greatly appreciated.

Getting Fatal error also with dehydrated-wrapper. Exited with non-zero exit code.

We have briefly opened the firewall to the site with the correct DNS and tested connection from outside.

Opened confconsole and added webservername.domain.com (listed in DNS) and ran the script.

Fatal Error.

Thank you for the help.