TKL Odoo 17.1 seems to install properly from ISO but not from Turnkey Hub

[l-arnold]

Hi,
I just ran through 2 installs on TKL Hub of TKL Odoo 17.1 but was never able to log in to Odoo or Debian (shell or webmin).

I did just pull down an ISO of the new Odoo and seem to have been successful using Virtual Box.
Not sure what is not going through on the Hub but definitely cannot access.

When trying to install a New Database in Odoo as a workaround I am getting "Access Denied".
It appears that the passwords set at launch on the hub are not taking w/ root, postgres and likely also with odoo.

Have killed both hub installs for now.

[JedMeister]

Hi Landis. Apologies for the slow response. It was going to be slow as I've been unwell, but also because I swear that I already responded to this the other day! (I notice that I applied tags 2 days ago, so that was likely when I thought I already responded). Clearly I must have neglected to click "comment"! Grr!

So, I tested myself and it seemed to work ok for me. Although I did use a fairly simple password.

We did have another Hub user the other day report that a password wasn't working. The password they were trying to use had a lot of "special characters" (i.e. punctuation marks). I confirmed that it was a problem, but never did get to the bottom of what the actual issues is. I do hope to circle back to it.

A work around for now would be to launch from the Hub setting not so great passwords, then log in via SSH. Obviously you'll need to either (preferably) set up a SSH keypair or set a not so complex root password (not recommended).

Then once you've logged in, run turnkey-init to reset better passwords.

PS I suggest setting up a SSh keypair and save the public one in the Hub - on the SSH keys page - then so long as you have your private key handy, you'll never need a SSH password again! :) Please be sure that you don't lose your private key though!

[l-arnold]

Ok. I will test again. Yes, was using somewhat complcated password but the approach has worked in the past.
I'll get the keypair working again (generally just need to point to it I believe)

[l-arnold]

edit (nevermind).. Seems to have taken up the ODOO Settings upon Retry
Will check if we can login after full install process. Updates running now.

Original comment below:

Just went to Hub.turnkeylnux.org try to install a server again again and I note that the general inithooks questions are not being asked regarding:
posgres password
odoo admin password

Only root is being asked.
Seems to be for both 16.1 and 17.1 TKL versions for Odoo App.

The ISO was asking these things I recall and it seems should be on the hub.. particularly so that TKLBAM etc will work properly.

[l-arnold]

OK. Can log in in the various ways.

[JedMeister]

Hmm, that's interesting that the Odoo questions weren't originally showing in the Hub. I've actually come across that before too (not with Odoo but with something else). It's never happened before or since, so I thought it must have been a mistake on my end (e.g. perhaps accidentally trying to load Core or something?). But now you've mentioned it, I wonder if it really is a minor intermittent glitch?

[l-arnold]

Jeremy,
I am reopening this.
So 3 times in as many days now, I have not been able to login after creating to a Hub Created instance of Odoo TKL 17.1 - at least not using the passwords that I set up at creation. I did also set a Key and can get in via Putty. Found there I could use passwd root.. but the other day my Odoo Passwords were also not passing through.
Right now I am trying a TKLBAM Restore (from 16.1) skipping database in hopes that that may set everything on one.

Was quite strange on another.. I swear I got a 17.1 to work but now when I see it on the web it is telling me it is a 16.1 install.

Anyway, Root Passwords are not going easily in with TKL Odoo 17.1 on the Hub.
Ca

[JedMeister]

As I noted in my email to you, I did a test launch of a v17.1 Odoo appliance and it all appeared to work for me?!

I wonder if there is a character in your password that the Hub doesn't like? FWIW over the last couple of months, 2 others have reported issues with passwords set in the Hub not working (although on different appliances and retrying with a different password seemed to resolve it), so I'm thinking that there may be a character that is not being processed properly (either being misinterpreted - or perhaps being lost somewhere)?

I have some ideas on how I might be able to troubleshoot that, but I really need to understand which characters may be the ones causing the issue first (i.e. I need to be able to reliably recreate the issue). The other possibility is that it's a race condition of some sort. They are notoriously hard to diagnose, but I'll try to have a closer look ASAP.

As a workaround, if you can log in (via PuTTY) with your key, then you could try manually re-running the firstboot script(s).

You can rerun them all like this:

turnkey-init

Alternatively, you can just rerun the Odoo specific inithook like this:

/usr/lib/inithooks/bin/odoo.py

[l-arnold]

Thanks for the turnkey-init reminder..

So my current take is that "if left to sit" the Servers will eventually take the passwords that are given... but that is strangely after 24 hours or so.

I have done new Hub / Odoo installs with both Chrome and Firefox and they are not taking root passwords properly after first boot of Webshell or Webmin.

They are taking the assigned Cert and the turnkey-init will set them to properly (and immediately) take the passwords (yes, they can be turned off in SSH and it would be nice to have them be responsive to Certs in Webmin and Webshell - and not take passwords there, but that is a different subject).

It is a real bear getting Odoo DB's to move from TKL 16.1 to TKL 17.1...
Working on a few of those again now.

To the "Issue at hand" though, the HUB is likely rebuffing more than me at first boot. Somewhere in this thread above I likely mentioned reboots (recall that anyway)... Not sure what is getting lost in the system.

[l-arnold]

The issue of starting a password with a symbol other than a letter or number continues in TKL 18 using the HUB. (Prestashop 18)
Strangely also, putty did not take the certificate that I assigned.
Unfortunately also Putty will time you out after only a few attempts then there is no way back in. I rebooted the server and still the same.

Also unclear as to whether I will be using admin or root to sign in...
Killing the server but all this takes time.