mirror of
https://github.com/pocket-id/pocket-id.git
synced 2025-12-09 14:42:59 +03:00
🐛 Bug Report: Pocket ID not starting #22
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hafedh-trimeche on GitHub.
Reproduction steps
New version 1.11.0
Windows 2019 Server
Expected behavior
Starting normally
Actual Behavior
Sep 18 22:17:42 INF Pocket ID is starting app=pocket-id version=1.11.0
Sep 18 22:17:42 INF Writing new application image app=pocket-id version=1.11.0 name=background.webp
Sep 18 22:17:42 ERR Failed to run pocket-id app=pocket-id version=1.11.0 error="failed to initialize application images: failed to copy file: failed to open embedded file: open images\background.webp: file does not exist"
Pocket ID Version
1.11.0
Database
Embedded (Windows version)
OS and Environment
Windows Server 2019
Log Output
No response
@hafedh-trimeche commented on GitHub:
Not using Docker. Just directly installed as .exe!
@MaroonBrian1928 commented on GitHub:
Same issue here running the docker version of 1.11.1 on Ubuntu server, also was not able to rollback easily because there was a database migration.
time=2025-09-18T22:41:45.292Z level=ERROR msg="Failed to run pocket-id" app=pocket-id version=1.10.0 error="failed to initialize database: failed to run migrations: database version (20250917170000) is newer than application version (20250822000000), downgrades are not allowed (set ALLOW_DOWNGRADE=true to enable)"
It looks like my instance is starting but I get the following error:
Refused to execute a script because its hash, its nonce, or 'unsafe-inline' does not appear in the script-src directive of the Content Security Policy.
@stonith404 commented on GitHub:
@hafedh-trimeche With "Embedded" you mean you are using Sqlite? Are you using Docker or the executable to run Pocket ID?
@stanrc85 commented on GitHub:
I'm having a similar issue on a hidden folder that my Synology creates
@kmendell commented on GitHub:
We will look into this, there was some logic to help decrease the background size and format, this is most likely the cause.
@stanrc85 commented on GitHub:
@instigate I just rolled back to a previous snapshot, I'd rather not delete folders that its likely to recreate anyways.
@instigate commented on GitHub:
It's how the synology works, some indexing service I assume, so running dockerized with volumes on the NAS it will see this hidden directory.
@stonith404 commented on GitHub:
This should be fixed in
v1.11.2.@instigate commented on GitHub:
@stanrc85, Remove the "@eaDir" in /uploads/application-images as a temp solution if you want to run the newer image.
@ItalyPaleAle commented on GitHub:
Weird that you have a folder in there.
Anyways, fix in #966