Application error after upgrading to 0.4.11

[jmcruvellier]

✅ Have you read and understood the above guidelines?

yes

📝 Provide a clear and concise description of the issue.

I'm no more able to log into PVE Script Local instance after the upgrade to version 0.4.11

🔄 Steps to reproduce the issue.

Update from 0.4.10 to version 0.4.11

❌ Paste the full error output (if available).

Application error: a client-side exception has occurred while loading my.domain.com (see the browser console for more information).

🖼️ Additional context (optional).

[smartkid808]

same issue here, rolled back for now. Thanks for all you do!

[michelroegl-brunner]

Question: Do you access by IP or by Domain with a Proxy before the App? If so, can you try accessing via IP:3000?

[smartkid808]

Hi, I was accessing locally via IP:3000, no proxy in between. I can update again, and give you more details or whatever you need. One thing I noticed, was the update took a bit to do. wasn't as quick as previous ones

[jmcruvellier]

Question: Do you access by IP or by Domain with a Proxy before the App? If so, can you try accessing via IP:3000?

I have installed the update when I was connected remotely from work via Cloudflared tunnel.
Just tried to connect locally from IP:3000 and same error :

Here is the error in the browser DEV console:

FYI this is happening just after entering login information

[jmcruvellier]

Nothing wrong at service level, everything is ok:

[michelroegl-brunner]

One last thing would be awesom if you can try: go inder /opt/ProxmoxVE-Local and change in the .env file AUTH_ENABLED to false, and see if you have access again?

[jmcruvellier]

OK, si I have re-installed v0.4.11, updated /opt/ProxmoxVE-Local/.env by setting AUTH_ENABLED=false :

• stop/start of pvescriptslocal.service => same error
• reboot LXC => same error

[michelroegl-brunner]

It even happens with a new install? That is truly odd. I turn on my debugger tomorrow and have a deep dive what the cause might be.

[jmcruvellier]

Updated from a backup, not a fresh install

It even happens with a new install? That is truly odd. I turn on my debugger tomorrow and have a deep dive what the cause might be.

[xb00tt]

Same here and I don't use any auth.
Page actually loads but the error appears immediately after the Release Notes modal window tries to load and the console is pointing to selectedRepositories.length as the error.

Edit: Fresh install works just fine. 👍

[jmcruvellier]

I've re-installed from scratch and then v0.4.1 works => there's something wrong in the upgrade process

[jwtoler]

Yeah, same upgrade issue

[jwtoler]

One last thing would be awesom if you can try: go inder /opt/ProxmoxVE-Local and change in the .env file AUTH_ENABLED to false, and see if you have access again?

Just fyi - did not work for me. Remember a previous upgrade that doing this, did fix a login issue. However, appears to not fix this time.

[michelroegl-brunner]

After investigation the Problem seems to be with the Database Migrations. For some, to me at this point not really known, reasons, this seems to be happening on "older" installs wich never had a migration with Prisma happen. (Installs before Version 0.4.3). So the migrations fails gracefully and the update dose not stop. I am not able to reporduce the error on my end atm, but i have a tester @Kaputtnique, and he helps me trying to understand the Problem. Best course of action will most likley be to install a new instance. But i keep you guys posted if i can come up with a solution to it.