Login doesn't work after update to v2.5.0.4

[BroOtti]

Bug Report

System Information

┏━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Key                  ┃ Value                                 ┃
┣━━━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ Operating System     ┃ Linux - Debian GNU/Linux 12 on x86_64 ┃
┃ Product              ┃ AMP 'Callisto' v2.5.0.4 (Mainline)    ┃
┃ Virtualization       ┃ ProxmoxLXC                            ┃
┃ Application          ┃ Application Deployment                ┃
┃ Module               ┃ ADSModule                             ┃
┃ Running in Container ┃ No                                    ┃
┃ Current State        ┃ Indeterminate                         ┃
┗━━━━━━━━━━━━━━━━━━━━━━┻━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛

I confirm:

• [x] that I have searched for an existing bug report for this issue.
• [x] that I am using the latest available version of AMP.
• [x] that my operating system is up-to-date.

Symptoms

• What are you trying to do? Login to AMP with normal user.
• What are you expecting to happen? I can successful login to AMP
• What is actually happening? ('Nothing' is not an acceptable answer!) The login doesn't work and an error is presented in the browser console. Cleaning browser cache or using different browser did not solve the problem.

  PluginHandler.js?v=2.5.0.4:155 Uncaught (in promise) TypeError: tab.vm?.disabled is not a function
  at scriptLoaded (PluginHandler.js?v=2.5.0.4:155:29)
  at Object.LoadPluginAsync (PluginHandler.js?v=2.5.0.4:160:19)
  at async Promise.all (/index 2)
  at async Object.loginCallback (AMP.js?v=2.5.0.4:581:5)

Reproduction

1. Update to v2.5.0.4 built 03/04/2024 18:20
2. Try to log in with a normal user
3. The login gets stuck at "Loading plugins one moment please..."
4. Try with a superadmin user and you see, it will work

There is already a post in discord for this issue opened by another user: https://ptb.discord.com/channels/266012086423912458/1225377495348547594

I couldn't test it with the just released patch, but I guess the error persists?

[BroOtti]

Forgot to mention, this error only occurs on login to ADS. If the user tries to login to the instance specific URL (https://amp/?instance=xxx) it works. So supplying an user with this URL is a work around.

Also, just tested again with the latest patch (v2.5.0.4, built 04/04/2024 11:59) and as assumed the problem is still there.

[BroOtti]

lol, edited the first post as it accidentally included info from my other bug report xD

[DerpehKitteh]

I am experiencing the same exact symptoms as you are. Browser console is reporting the same exact thing to my users. My panel also runs inside ProxMox.

[ssfdre38]

try this https://discord.com/channels/266012086423912458/1225507232427409540/1225520438407467159 users on discord have a fix found

[DerpehKitteh]

Appreciate that!

[BroOtti]

The fix mentioned is adding permissions to View Backups List:

[IceOfWraith]

This is resolved in the development release.