Whilst your experience may appear the same, as noted in this thread, the issue was resolved. Regardless, something clearly isn't quite right on your server.

To step back a bit, what you are seeing we call the "initfence". It is designed to block all contact with web interfaces on your server until you have logged in via SSH and completed the firstboot scripts (inc things such as setting passwords, regenerating secrets, etc).

Did you go through those questions when you first logged in (via SSH or in the PVE terminal)? As noted by the OP in this thread, they did, then even ran turnkey-init afterwards - but you didn't note whether you did that too?

If you've definitely answered the questions at least once, please double check that the value of 'RUN_FIRSTBOOT' is false. I.e.:

grep RUN_FIRSTBOOT /etc/default/inithooks

Should return:

RUN_FIRSTBOOT=false

If it is 'true', then something has clearly gone wrong.

The logs don't give much detail, but you may get an insight into what went wrong from the log: /var/log/inithooks.log. To check for errors:

grep 'exit code' /var/log/inithooks.log

Please share any errors and/or feel free to post the whole file if you want my 2c.

If everything appears to be working ok otherwise, but 'RUN_FIRSTBOOT=true' then you can manually change that like this:

sed -i "\|^RUN_FIRSTBOOT|s|=.*|=false|" /etc/default/inithooks

And to manually disable the initfence:

_TURNKEY_INIT=y /usr/lib/inithooks/firstboot.d/97turnkey-init-fence-disable

I recommend a reboot to ensure that all is well.