Application error after upgrading to 0.4.11 #105

@jmcruvellier commented on GitHub (Nov 13, 2025):

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 commented on GitHub (Nov 13, 2025): > 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 : <img width="1341" height="296" alt="Image" src="https://github.com/user-attachments/assets/15b792ba-b658-4a84-b9e4-ec751208d53f" /> Here is the error in the browser DEV console: <img width="819" height="259" alt="Image" src="https://github.com/user-attachments/assets/9c65b67e-2810-4fbc-9a8b-74e7858ae1cb" /> FYI this is happening just after entering login information

saavagebueno commented

@jmcruvellier commented on GitHub (Nov 13, 2025):

Nothing wrong at service level, everything is ok:

@jmcruvellier commented on GitHub (Nov 13, 2025): Nothing wrong at service level, everything is ok: <img width="1766" height="605" alt="Image" src="https://github.com/user-attachments/assets/157711c1-23ea-4e6a-9a48-70c6b3b717ef" />

saavagebueno commented

@michelroegl-brunner commented on GitHub (Nov 13, 2025):

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?

@michelroegl-brunner commented on GitHub (Nov 13, 2025): 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?

saavagebueno commented

@jmcruvellier commented on GitHub (Nov 13, 2025):

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

@jmcruvellier commented on GitHub (Nov 13, 2025): 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

saavagebueno commented

@michelroegl-brunner commented on GitHub (Nov 13, 2025):

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.

@michelroegl-brunner commented on GitHub (Nov 13, 2025): 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.

saavagebueno commented

@jmcruvellier commented on GitHub (Nov 13, 2025):

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.

@jmcruvellier commented on GitHub (Nov 13, 2025): 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.

saavagebueno commented

@xb00tt commented on GitHub (Nov 13, 2025):

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. 👍

@xb00tt commented on GitHub (Nov 13, 2025): 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. 👍

saavagebueno commented

@jmcruvellier commented on GitHub (Nov 13, 2025):

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

@jmcruvellier commented on GitHub (Nov 13, 2025): I've re-installed from scratch and then v0.4.1 works => there's something wrong in the upgrade process

saavagebueno commented

@jwtoler commented on GitHub (Nov 13, 2025):

Yeah, same upgrade issue

@jwtoler commented on GitHub (Nov 13, 2025): Yeah, same upgrade issue

saavagebueno commented

@jwtoler commented on GitHub (Nov 13, 2025):

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.

@jwtoler commented on GitHub (Nov 13, 2025): > 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.

saavagebueno commented

@michelroegl-brunner commented on GitHub (Nov 14, 2025):

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.

@michelroegl-brunner commented on GitHub (Nov 14, 2025): 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.

saavagebueno commented

@michelroegl-brunner commented on GitHub (Nov 14, 2025):

Scratch the above, Migrations are not the Issue, but i found it! The Problem is with the Filters. I added some more filtering Options, and those options are missing in the .env File.

To solve the issue do the following: open the shell of the LXC and navigate to cd /opt/ProxmoxVE-local/ in there open the .env file: nano .env. In this file delete the two lines SAVE_FILTER=* and FILTERS=* or comment them out. There after the applications is running again, as far as i was able to test.

Feedback is welcome, and fix will be implemented to prevent this behaviour.

@michelroegl-brunner commented on GitHub (Nov 14, 2025): Scratch the above, Migrations are not the Issue, but i found it! The Problem is with the Filters. I added some more filtering Options, and those options are missing in the .env File. To solve the issue do the following: open the shell of the LXC and navigate to `cd /opt/ProxmoxVE-local/` in there open the .env file: `nano .env`. In this file delete the two lines `SAVE_FILTER=*` and `FILTERS=*` or comment them out. There after the applications is running again, as far as i was able to test. Feedback is welcome, and fix will be implemented to prevent this behaviour.

saavagebueno commented

@jmcruvellier commented on GitHub (Nov 14, 2025):

Will try it during the week-end, or earlier if I can find a slot because I need to rollback to v0.4.10 from a backup as yesterday I re-installed from scratch. Coming back to you to let you know if this is a sustainable fix or not.

Scratch the above, Migrations are not the Issue, but i found it! The Problem is with the Filters. I added some more filtering Options, and those options are missing in the .env File.

To solve the issue do the following: open the shell of the LXC and navigate to cd /opt/ProxmoxVE-local/ in there open the .env file: nano .env. In this file delete the two lines SAVE_FILTER=* and FILTERS=* or comment them out. There after the applications is running again, as far as i was able to test.

Feedback is welcome, and fix will be implemented to prevent this behaviour.

@jmcruvellier commented on GitHub (Nov 14, 2025): Will try it during the week-end, or earlier if I can find a slot because I need to rollback to v0.4.10 from a backup as yesterday I re-installed from scratch. Coming back to you to let you know if this is a sustainable fix or not. > Scratch the above, Migrations are not the Issue, but i found it! The Problem is with the Filters. I added some more filtering Options, and those options are missing in the .env File. > > To solve the issue do the following: open the shell of the LXC and navigate to `cd /opt/ProxmoxVE-local/` in there open the .env file: `nano .env`. In this file delete the two lines `SAVE_FILTER=*` and `FILTERS=*` or comment them out. There after the applications is running again, as far as i was able to test. > > Feedback is welcome, and fix will be implemented to prevent this behaviour.

saavagebueno commented

@jwtoler commented on GitHub (Nov 14, 2025):

Scratch the above, Migrations are not the Issue, but i found it! The Problem is with the Filters. I added some more filtering Options, and those options are missing in the .env File.

To solve the issue do the following: open the shell of the LXC and navigate to cd /opt/ProxmoxVE-local/ in there open the .env file: nano .env. In this file delete the two lines SAVE_FILTER=* and FILTERS=* or comment them out. There after the applications is running again, as far as i was able to test.

Feedback is welcome, and fix will be implemented to prevent this behaviour.

Just had to comment out SAVE_FILTER to get it working. Thank you!

@jwtoler commented on GitHub (Nov 14, 2025): > Scratch the above, Migrations are not the Issue, but i found it! The Problem is with the Filters. I added some more filtering Options, and those options are missing in the .env File. > > To solve the issue do the following: open the shell of the LXC and navigate to `cd /opt/ProxmoxVE-local/` in there open the .env file: `nano .env`. In this file delete the two lines `SAVE_FILTER=*` and `FILTERS=*` or comment them out. There after the applications is running again, as far as i was able to test. > > Feedback is welcome, and fix will be implemented to prevent this behaviour. Just had to comment out `SAVE_FILTER` to get it working. Thank you!

saavagebueno commented

@Kaputtnique commented on GitHub (Nov 14, 2025):

Application Error is done, but main repo doesnt apply :(

Invalid prisma.repository.findUnique()invocation: The tablemain.repositories does not exist in the current database.

@Kaputtnique commented on GitHub (Nov 14, 2025): Application Error is done, but main repo doesnt apply :( `Invalid `prisma.repository.findUnique()` invocation: The table `main.repositories` does not exist in the current database.`

saavagebueno commented

@smartkid808 commented on GitHub (Nov 14, 2025):

looks like commenting out SAVE_FILTER worked for me as well!

@smartkid808 commented on GitHub (Nov 14, 2025): looks like commenting out SAVE_FILTER worked for me as well!

saavagebueno commented

@Blue0ctober commented on GitHub (Nov 14, 2025):

Commenting out SAVE_FILTER no longer gives me a 404 after login.

Unfortunately now there's no scripts that load; trying to refresh json fails. PVE servers previously configured are no longer loading giving Failed to fetch servers and trying to add a new PVE returns Failed to create Server.

.env also has about a half dozen JWT_SECRET vars in it.

and looking at journalctl i see the following:

Nov 14 14:26:28 pvehelper npm[579]: Starting multi-repository JSON sync...
Nov 14 14:26:28 pvehelper npm[579]: prisma:error
Nov 14 14:26:28 pvehelper npm[579]: Invalid `prisma.repository.findMany()` invocation:
Nov 14 14:26:28 pvehelper npm[579]: Error querying the database: Error code 14: Unable to open the database file
Nov 14 14:26:28 pvehelper npm[579]: Multi-repository JSON sync failed: Error [PrismaClientInitializationError]:
Nov 14 14:26:28 pvehelper npm[579]: Invalid `prisma.repository.findMany()` invocation:
Nov 14 14:26:28 pvehelper npm[579]: Error querying the database: Error code 14: Unable to open the database file
Nov 14 14:26:28 pvehelper npm[579]:     at async f.getEnabledRepositories (.next/server/chunks/217.js:1:2470)
Nov 14 14:26:28 pvehelper npm[579]:     at async h.syncJsonFiles (.next/server/chunks/217.js:1:9082)
Nov 14 14:26:28 pvehelper npm[579]:     at async (.next/server/app/api/trpc/[trpc]/route.js:8:21145)
Nov 14 14:26:28 pvehelper npm[579]:     at async bC.middlewares (.next/server/app/api/trpc/[trpc]/route.js:5:7721)
Nov 14 14:26:28 pvehelper npm[579]:     at async bG (.next/server/app/api/trpc/[trpc]/route.js:8:69)
Nov 14 14:26:28 pvehelper npm[579]:     at async b (.next/server/app/api/trpc/[trpc]/route.js:5:7957) {
Nov 14 14:26:28 pvehelper npm[579]:   clientVersion: '6.19.0',
Nov 14 14:26:28 pvehelper npm[579]:   errorCode: undefined,
Nov 14 14:26:28 pvehelper npm[579]:   retryable: undefined
Nov 14 14:26:28 pvehelper npm[579]: }

I don't mind doing a fresh install, but hopefully the above help with troubleshooting the upgraded instances.

@Blue0ctober commented on GitHub (Nov 14, 2025): Commenting out `SAVE_FILTER` no longer gives me a 404 after login. Unfortunately now there's no scripts that load; trying to refresh json fails. PVE servers previously configured are no longer loading giving `Failed to fetch servers` and trying to add a new PVE returns `Failed to create Server`. `.env` also has about a half dozen `JWT_SECRET` vars in it. and looking at journalctl i see the following: ``` Nov 14 14:26:28 pvehelper npm[579]: Starting multi-repository JSON sync... Nov 14 14:26:28 pvehelper npm[579]: prisma:error Nov 14 14:26:28 pvehelper npm[579]: Invalid `prisma.repository.findMany()` invocation: Nov 14 14:26:28 pvehelper npm[579]: Error querying the database: Error code 14: Unable to open the database file Nov 14 14:26:28 pvehelper npm[579]: Multi-repository JSON sync failed: Error [PrismaClientInitializationError]: Nov 14 14:26:28 pvehelper npm[579]: Invalid `prisma.repository.findMany()` invocation: Nov 14 14:26:28 pvehelper npm[579]: Error querying the database: Error code 14: Unable to open the database file Nov 14 14:26:28 pvehelper npm[579]: at async f.getEnabledRepositories (.next/server/chunks/217.js:1:2470) Nov 14 14:26:28 pvehelper npm[579]: at async h.syncJsonFiles (.next/server/chunks/217.js:1:9082) Nov 14 14:26:28 pvehelper npm[579]: at async (.next/server/app/api/trpc/[trpc]/route.js:8:21145) Nov 14 14:26:28 pvehelper npm[579]: at async bC.middlewares (.next/server/app/api/trpc/[trpc]/route.js:5:7721) Nov 14 14:26:28 pvehelper npm[579]: at async bG (.next/server/app/api/trpc/[trpc]/route.js:8:69) Nov 14 14:26:28 pvehelper npm[579]: at async b (.next/server/app/api/trpc/[trpc]/route.js:5:7957) { Nov 14 14:26:28 pvehelper npm[579]: clientVersion: '6.19.0', Nov 14 14:26:28 pvehelper npm[579]: errorCode: undefined, Nov 14 14:26:28 pvehelper npm[579]: retryable: undefined Nov 14 14:26:28 pvehelper npm[579]: } ``` I don't mind doing a fresh install, but hopefully the above help with troubleshooting the upgraded instances.

saavagebueno commented

@michelroegl-brunner commented on GitHub (Nov 17, 2025):

Commenting out SAVE_FILTER no longer gives me a 404 after login.

Unfortunately now there's no scripts that load; trying to refresh json fails. PVE servers previously configured are no longer loading giving Failed to fetch servers and trying to add a new PVE returns Failed to create Server.

.env also has about a half dozen JWT_SECRET vars in it.

and looking at journalctl i see the following:

Nov 14 14:26:28 pvehelper npm[579]: Starting multi-repository JSON sync...
Nov 14 14:26:28 pvehelper npm[579]: prisma:error
Nov 14 14:26:28 pvehelper npm[579]: Invalid `prisma.repository.findMany()` invocation:
Nov 14 14:26:28 pvehelper npm[579]: Error querying the database: Error code 14: Unable to open the database file
Nov 14 14:26:28 pvehelper npm[579]: Multi-repository JSON sync failed: Error [PrismaClientInitializationError]:
Nov 14 14:26:28 pvehelper npm[579]: Invalid `prisma.repository.findMany()` invocation:
Nov 14 14:26:28 pvehelper npm[579]: Error querying the database: Error code 14: Unable to open the database file
Nov 14 14:26:28 pvehelper npm[579]:     at async f.getEnabledRepositories (.next/server/chunks/217.js:1:2470)
Nov 14 14:26:28 pvehelper npm[579]:     at async h.syncJsonFiles (.next/server/chunks/217.js:1:9082)
Nov 14 14:26:28 pvehelper npm[579]:     at async (.next/server/app/api/trpc/[trpc]/route.js:8:21145)
Nov 14 14:26:28 pvehelper npm[579]:     at async bC.middlewares (.next/server/app/api/trpc/[trpc]/route.js:5:7721)
Nov 14 14:26:28 pvehelper npm[579]:     at async bG (.next/server/app/api/trpc/[trpc]/route.js:8:69)
Nov 14 14:26:28 pvehelper npm[579]:     at async b (.next/server/app/api/trpc/[trpc]/route.js:5:7957) {
Nov 14 14:26:28 pvehelper npm[579]:   clientVersion: '6.19.0',
Nov 14 14:26:28 pvehelper npm[579]:   errorCode: undefined,
Nov 14 14:26:28 pvehelper npm[579]:   retryable: undefined
Nov 14 14:26:28 pvehelper npm[579]: }

I don't mind doing a fresh install, but hopefully the above help with troubleshooting the upgraded instances.

There is a wired error with prisma migratin wich i was not yet able to recreate fully. Best course of action would be to reinsall the lxc tbh.

@michelroegl-brunner commented on GitHub (Nov 17, 2025): > Commenting out `SAVE_FILTER` no longer gives me a 404 after login. > > Unfortunately now there's no scripts that load; trying to refresh json fails. PVE servers previously configured are no longer loading giving `Failed to fetch servers` and trying to add a new PVE returns `Failed to create Server`. > > `.env` also has about a half dozen `JWT_SECRET` vars in it. > > and looking at journalctl i see the following: > > ``` > Nov 14 14:26:28 pvehelper npm[579]: Starting multi-repository JSON sync... > Nov 14 14:26:28 pvehelper npm[579]: prisma:error > Nov 14 14:26:28 pvehelper npm[579]: Invalid `prisma.repository.findMany()` invocation: > Nov 14 14:26:28 pvehelper npm[579]: Error querying the database: Error code 14: Unable to open the database file > Nov 14 14:26:28 pvehelper npm[579]: Multi-repository JSON sync failed: Error [PrismaClientInitializationError]: > Nov 14 14:26:28 pvehelper npm[579]: Invalid `prisma.repository.findMany()` invocation: > Nov 14 14:26:28 pvehelper npm[579]: Error querying the database: Error code 14: Unable to open the database file > Nov 14 14:26:28 pvehelper npm[579]: at async f.getEnabledRepositories (.next/server/chunks/217.js:1:2470) > Nov 14 14:26:28 pvehelper npm[579]: at async h.syncJsonFiles (.next/server/chunks/217.js:1:9082) > Nov 14 14:26:28 pvehelper npm[579]: at async (.next/server/app/api/trpc/[trpc]/route.js:8:21145) > Nov 14 14:26:28 pvehelper npm[579]: at async bC.middlewares (.next/server/app/api/trpc/[trpc]/route.js:5:7721) > Nov 14 14:26:28 pvehelper npm[579]: at async bG (.next/server/app/api/trpc/[trpc]/route.js:8:69) > Nov 14 14:26:28 pvehelper npm[579]: at async b (.next/server/app/api/trpc/[trpc]/route.js:5:7957) { > Nov 14 14:26:28 pvehelper npm[579]: clientVersion: '6.19.0', > Nov 14 14:26:28 pvehelper npm[579]: errorCode: undefined, > Nov 14 14:26:28 pvehelper npm[579]: retryable: undefined > Nov 14 14:26:28 pvehelper npm[579]: } > ``` > > I don't mind doing a fresh install, but hopefully the above help with troubleshooting the upgraded instances. There is a wired error with prisma migratin wich i was not yet able to recreate fully. Best course of action would be to reinsall the lxc tbh.

saavagebueno commented