First time bringing up Trilium (via Docker Compose) and it asks me to LOGIN

cleverestx commented 2 months ago

Trilium Version

v0.63.5

What operating system are you using?

Other (specify below)

What is your setup?

Local (no sync)

Operating System Version

DSM 7

Description

Latest PULL....On a Synology NAS, this is my first time bringing this up. Why would it be asking me to log in? I don't have a password yet...

My compose:

`services: trilium: image: zadam/trilium container_name: trilium ports:

4299:8080 environment:
TRILIUM_DATA_DIR=/home/node/trilium-data volumes:
/volume1/docker/trilium:/home/node/trilium-data restart: unless-stopped`

Error logs

Migration to version 220 has been successful. Attempting migration to version 221 Migration with SQL script: DELETE FROM options WHERE name = 'hideIncludedImages_main'; DELETE FROM entity_changes WHERE entityName = 'options' AND entityId = 'hideIncludedImages_main'; Migration to version 221 has been successful. Attempting migration to version 222 Migration with SQL script: UPDATE options SET name = 'openNoteContexts' WHERE name = 'openTabs'; UPDATE entity_changes SET entityId = 'openNoteContexts' WHERE entityName = 'options' AND entityId = 'openTabs'; Migration to version 222 has been successful. Attempting migration to version 223 Migration with SQL script: SELECT 1; Migration to version 223 has been successful. Attempting migration to version 224 Migration with SQL script: UPDATE blobs SET blobId = REPLACE(blobId, '+', 'X'); UPDATE blobs SET blobId = REPLACE(blobId, '/', 'Y'); UPDATE notes SET blobId = REPLACE(blobId, '+', 'X'); UPDATE notes SET blobId = REPLACE(blobId, '/', 'Y'); UPDATE attachments SET blobId = REPLACE(blobId, '+', 'X'); UPDATE attachments SET blobId = REPLACE(blobId, '/', 'Y'); UPDATE revisions SET blobId = REPLACE(blobId, '+', 'X'); UPDATE revisions SET blobId = REPLACE(blobId, '/', 'Y'); UPDATE entity_changes SET entityId = REPLACE(entityId, '+', 'X') WHERE entityName = 'blobs'; UPDATE entity_changes SET entityId = REPLACE(entityId, '/', 'Y') WHERE entityName = 'blobs'; Migration to version 224 has been successful. Attempting migration to version 225 Migration with SQL script: CREATE INDEX IF NOT EXISTS IDX_notes_blobId on notes (blobId); CREATE INDEX IF NOT EXISTS IDX_revisions_blobId on revisions (blobId); CREATE INDEX IF NOT EXISTS IDX_attachments_blobId on attachments (blobId); Migration to version 225 has been successful. Attempting migration to version 226 Migration with SQL script: UPDATE attributes SET value = 'contentAndAttachmentsAndRevisionsSize' WHERE name = 'orderBy' AND value = 'noteSize'; Migration to version 226 has been successful. Attempting migration to version 227 Migration with SQL script: -- emergency disabling of image compression since it appears to make problems in migration to 0.61 UPDATE options SET value = 'false' WHERE name = 'compressImages'; Migration to version 227 has been successful. Attempting migration to version 228 Migration with SQL script: -- + is normally replaced by X and / by Y, but this can temporarily cause UNIQUE key exception -- this might create blob duplicates, but cleanup will eventually take care of it UPDATE blobs SET blobId = REPLACE(blobId, '+', 'A'); UPDATE blobs SET blobId = REPLACE(blobId, '/', 'B'); UPDATE notes SET blobId = REPLACE(blobId, '+', 'A'); UPDATE notes SET blobId = REPLACE(blobId, '/', 'B'); UPDATE attachments SET blobId = REPLACE(blobId, '+', 'A'); UPDATE attachments SET blobId = REPLACE(blobId, '/', 'B'); UPDATE revisions SET blobId = REPLACE(blobId, '+', 'A'); UPDATE revisions SET blobId = REPLACE(blobId, '/', 'B'); UPDATE entity_changes SET entityId = REPLACE(entityId, '+', 'A') WHERE entityName = 'blobs'; UPDATE entity_changes SET entityId = REPLACE(entityId, '/', 'B') WHERE entityName = 'blobs'; Migration to version 228 has been successful. VACUUMing database, this might take a while ... Becca (note cache) load took 9ms Created option "revisionSnapshotTimeInterval" with default value "600" Created option "highlightsList" with default value "["bold","italic","underline","color","bgColor"]" Created option "eraseUnusedAttachmentsAfterSeconds" with default value "2592000" Created option "promotedAttributesOpenInRibbon" with default value "true" Created option "editedNotesOpenInRibbon" with default value "true" Created option "keyboardShortcutsToggleTray" with default value "[]" Created option "keyboardShortcutsFirstTab" with default value "["Ctrl+1"]" Created option "keyboardShortcutsSecondTab" with default value "["Ctrl+2"]" Created option "keyboardShortcutsThirdTab" with default value "["Ctrl+3"]" Created option "keyboardShortcutsFourthTab" with default value "["Ctrl+4"]" Created option "keyboardShortcutsFifthTab" with default value "["Ctrl+5"]" Created option "keyboardShortcutsSixthTab" with default value "["Ctrl+6"]" Created option "keyboardShortcutsSeventhTab" with default value "["Ctrl+7"]" Created option "keyboardShortcutsEigthTab" with default value "["Ctrl+8"]" Created option "keyboardShortcutsNinthTab" with default value "["Ctrl+9"]" Created option "keyboardShortcutsLastTab" with default value "[]" Created option "keyboardShortcutsShowRevisions" with default value "[]" Created option "keyboardShortcutsToggleRightPane" with default value "[]" Created option "keyboardShortcutsZoomReset" with default value "[]" Created option "keyboardShortcutsForceSaveRevision" with default value "[]" Slow 200 GET /api/health-check with 15 bytes took 10ms Table counts: notes: 224, revisions: 4, attachments: 6, branches: 245, attributes: 368, etapi_tokens: 0, blobs: 117 All consistency checks passed with no errors detected (took 21ms) 200 GET /api/health-check with 15 bytes took 1ms 200 GET /api/health-check with 15 bytes took 1ms 200 GET /api/health-check with 15 bytes took 1ms 200 GET /api/health-check with 15 bytes took 1ms 200 GET /api/health-check with 15 bytes took 1ms 200 GET /api/health-check with 15 bytes took 1ms WARNING: Wrong password from 172.20.0.1, rejecting. 200 GET /api/health-check with 15 bytes took 1ms 200 GET /api/health-check with 15 bytes took 1ms

Nriver commented 2 months ago

It seems you've used Trilium before but forgot your password. To start fresh, you can delete the data folder to create a new database.

cleverestx commented 2 months ago

It seems you've used Trilium before but forgot your password. To start fresh, you can delete the data folder to create a new database.

Ahhh I missed that somehow...forgot I tried this in the past, and couldn't get it working before for some reason. I'll try that. Thanks.

cleverestx commented 2 months ago

Yup, now I remember. It is doing the same issue... I set up a password in the proceeding screen, get this this screen and it simply refuses accepting it. I gave up last time this happened....why can't I log in with the password I just created, no $ in the password or spaces, or anything odd like that....

cleverestx commented 2 months ago

Tail of my logs is this:

`200 GET /api/health-check with 15 bytes took 1ms

200 GET /api/health-check with 15 bytes took 1ms

[session-file-store] will retry, error on last attempt: Error: ENOENT: no such file or directory, open '/home/node/trilium-data/sessions/M0BUO4_CxdduG1C4DdLSMPNaBSJ-bFwh.json'

[session-file-store] will retry, error on last attempt: Error: ENOENT: no such file or directory, open '/home/node/trilium-data/sessions/M0BUO4_CxdduG1C4DdLSMPNaBSJ-bFwh.json'`

cleverestx commented 2 months ago

Should I open another issue for this? I've never been able to get beyond this issue and never seem Trilium load even once. What else do you need?

perfectra1n commented 1 month ago

It appears as though it's unable to write / read files from /home/node/trilium-data/sessions @cleverestx, what are the permissions on your local folder /volume1/docker/trilium? The container I believe has uid:gid 1000 if I remember correctly, so it might not be able to write to that folder you're trying to have it write to.

zadam / trilium