Hi! I've been trying to setup the self-hosted version in my docker VM (running Ubuntu 22.04 - up to date) using portainer. However, no matter what I do, the mongodb container fails to authenticate when the self-hosted container tries to authenticate. I've tried a bunch of different fixes, but nothing has worked. I followed the instructions precisely and copied and pasted the .yaml file, changing the items it requests. The VM is running on a Proxmox machine running an intel 12th gen i9-12900H.

Here's my config with my password changed to generic for privacy...
services:
journey-sync-self-hosted-service:
image: journeycloud/journey-sync-self-hosted
labels:
kompose.volume.size: 4Gi
environment:
EXPRESS_SERVER_PORT: 8080
REDIS_PORT: 6379
DISABLE_SSL: NO
DOMAIN: journey.4bowers.net
ROOT_MONGO_DB_URL: mongodb://root:password@journey-mongodb-service:27017
MONGO_DB_URL: mongodb://user:password@journey-mongodb-service:27017/journey
REDIS_URL: redis://journey-redis-service:6379
FS_PATH: /mnt/data
SIGNED: REMOVED_FOR_PRIVACY
ADMIN_JS_COOKIE_PASSWORD: REMOVED_FOR_PRIVACY
TYPESENSE_HOST: journey-typesense-service
TYPESENSE_PORT: 8108
TYPESENSE_PROTOCOL: http
TYPESENSE_API_KEY: xyz
entrypoint: 'npm run launch'
depends_on:
- journey-mongodb-service
- journey-redis-service
- journey-typesense-service
volumes:
- journey-fs-volume:/mnt/data
ports:
- 8080:8080
journey-sync-self-hosted-media:
image: journeycloud/journey-sync-self-hosted
labels:
kompose.volume.size: 4Gi
environment:
REDIS_PORT: 6379
DISABLE_SSL: NO
DOMAIN: journey.4bowers.net
ROOT_MONGO_DB_URL: mongodb://root:password@journey-mongodb-service:27017
MONGO_DB_URL: mongodb://user:password@journey-mongodb-service:27017/journey
REDIS_URL: redis://journey-redis-service:6379
FS_PATH: /mnt/data
entrypoint: 'npm run launchMedia'
depends_on:
- journey-sync-self-hosted-service
volumes:
- journey-fs-volume:/mnt/data
journey-mongodb-service:
image: mongo:7.0
labels:
kompose.volume.size: 4Gi
environment:
MONGO_INITDB_ROOT_USERNAME: root
MONGO_INITDB_ROOT_PASSWORD: password
MONGO_INITDB_DATABASE: journey
volumes:
- journey-mongodb-volume:/data/db
journey-redis-service:
image: redis:7.2.4-alpine
labels:
kompose.volume.size: 4Gi
volumes:
- journey-redis-volume:/data
command: redis-server
journey-typesense-service:
image: typesense/typesense:26.0
labels:
kompose.volume.size: 10Gi
volumes:
- journey-typesense-volume:/data
command: '--data-dir /data --api-key=xyz --enable-cors'
volumes:
journey-mongodb-volume:
labels:
kompose.volume.size: 10Gi
journey-typesense-volume:
labels:
kompose.volume.size: 10Gi
journey-fs-volume:
labels:
kompose.volume.size: 20Gi
journey-redis-volume:
labels:
kompose.volume.size: 4Gi

Any help would be very much appreciated.

Sorry, I forgot the log....here it is....

2024-10-04T18:06:46.953620244Z
2024-10-04T18:06:46.953661333Z > journey-sync-self-hosted@0.1.0-alpha04 launch
2024-10-04T18:06:46.953667027Z > node index.js --no-warnings=ExperimentalWarning
2024-10-04T18:06:46.953670221Z
2024-10-04T18:06:47.009335498Z (node:19) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
2024-10-04T18:06:47.009357421Z (Use
node --trace-warnings ...to show where the warning was created)
2024-10-04T18:06:48.121179488Z 🔎 Typesense: Client created.
2024-10-04T18:06:48.130758940Z (node:19) [DEP0040] DeprecationWarning: The
punycodemodule is deprecated. Please use a userland alternative instead.
2024-10-04T18:06:48.135436985Z Request #1728065208121: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
2024-10-04T18:06:48.135447269Z Request #1728065208121: Sleeping for 0.1s and then retrying request...
2024-10-04T18:06:48.238275930Z Request #1728065208121: Request to Node 0 failed due to "undefined Request failed with HTTP code 503 | Server said: Not Ready or Lagging"
2024-10-04T18:06:48.238294754Z Request #1728065208121: Sleeping for 0.1s and then retrying request...
2024-10-04T18:06:48.340455812Z ServerError: Request failed with HTTP code 503 | Server said: Not Ready or Lagging
2024-10-04T18:06:48.340475073Z at ServerError.TypesenseError [as constructor] (/app/node_modules/typesense/lib/Typesense/Errors/TypesenseError.js:23:28)
2024-10-04T18:06:48.340476759Z at new ServerError (/app/node_modules/typesense/lib/Typesense/Errors/ServerError.js:25:42)
2024-10-04T18:06:48.340478090Z at ApiCall.customErrorForResponse (/app/node_modules/typesense/lib/Typesense/ApiCall.js:384:21)
2024-10-04T18:06:48.340479426Z at /app/node_modules/typesense/lib/Typesense/ApiCall.js:233:58
2024-10-04T18:06:48.340480690Z at step (/app/node_modules/typesense/lib/Typesense/ApiCall.js:33:23)
2024-10-04T18:06:48.340481938Z at Object.next (/app/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
2024-10-04T18:06:48.340483390Z at step (/app/node_modules/typesense/lib/Typesense/ApiCall.js:18:139)
2024-10-04T18:06:48.340484697Z at Object.next (/app/node_modules/typesense/lib/Typesense/ApiCall.js:14:53)
2024-10-04T18:06:48.340485960Z at fulfilled (/app/node_modules/typesense/lib/Typesense/ApiCall.js:5:58)
2024-10-04T18:06:48.340487221Z at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
2024-10-04T18:06:48.340488555Z httpStatus: 503
2024-10-04T18:06:48.340489810Z }
2024-10-04T18:06:48.340812323Z 📚 Connecting to database...
2024-10-04T18:06:48.370499776Z /app/node_modules/mongodb/lib/cmap/connection.js:281
2024-10-04T18:06:48.370505015Z throw new error_1.MongoServerError(document);
2024-10-04T18:06:48.370506844Z ^
2024-10-04T18:06:48.370508508Z
2024-10-04T18:06:48.370518193Z MongoServerError: Authentication failed.
2024-10-04T18:06:48.370520149Z at Connection.sendCommand (/app/node_modules/mongodb/lib/cmap/connection.js:281:27)
2024-10-04T18:06:48.370521896Z at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-10-04T18:06:48.370523547Z at async Connection.command (/app/node_modules/mongodb/lib/cmap/connection.js:304:26)
2024-10-04T18:06:48.370525249Z at async continueScramConversation (/app/node_modules/mongodb/lib/cmap/auth/scram.js:131:15)
2024-10-04T18:06:48.370527290Z at async performInitialHandshake (/app/node_modules/mongodb/lib/cmap/connect.js:101:13)
2024-10-04T18:06:48.370529099Z at async connect (/app/node_modules/mongodb/lib/cmap/connect.js:19:9) {
2024-10-04T18:06:48.370530801Z errorResponse: {
2024-10-04T18:06:48.370532364Z ok: 0,
2024-10-04T18:06:48.370534080Z errmsg: 'Authentication failed.',
2024-10-04T18:06:48.370535718Z code: 18,
2024-10-04T18:06:48.370537333Z codeName: 'AuthenticationFailed'
2024-10-04T18:06:48.370538983Z },
2024-10-04T18:06:48.370540516Z ok: 0,
2024-10-04T18:06:48.370542115Z code: 18,
2024-10-04T18:06:48.370543665Z codeName: 'AuthenticationFailed',
2024-10-04T18:06:48.370545255Z connectionGeneration: 0,
2024-10-04T18:06:48.370546897Z [Symbol(errorLabels)]: Set(2) { 'HandshakeError', 'ResetPool' }
2024-10-04T18:06:48.370548591Z }
2024-10-04T18:06:48.370550161Z
2024-10-04T18:06:48.370551710Z Node.js v21.7.3
2024-10-04T18:06:48.381422438Z npm notice
2024-10-04T18:06:48.381709817Z npm notice New minor version of npm available! 10.5.0 -> 10.9.0
2024-10-04T18:06:48.381746133Z npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.9.0>
2024-10-04T18:06:48.381796236Z npm notice Run
npm install -g npm@10.9.0to update!
2024-10-04T18:06:48.381820159Z npm notice

Just a little bit more....my mongodb log shows this....

2024-10-04T19:02:46.997730455Z | t={"$date":"2024-10-04T19:02:46.997+00:00"} s=I c=ACCESS id=5286307 ctx=conn6 msg=Failed to authenticate attr={"client":"172.21.0.6:53140","isSpeculative":true,"isClusterMember":false,"mechanism":"SCRAM-SHA-256","user":"root","db":"journey","error":"UserNotFound: Could not find user \"root\" for db \"journey\"","result":11,"metrics":{"conversation_duration":{"micros":267,"summary":{"0":{"step":1,"step_total":2,"duration_micros":253}}}},"extraInfo":{}}

Doesn't make much sense to me as I have it set to create the user, based on the docker compose file, unless I am missing something in my syntax.

MONGO_DB_URL: mongodb://user:password@journey-mongodb-service:27017/journey
Are you doing any changes here?
If yes i can tell you that is not possible because its hardcoded in the server image i cant tell you why it is but thats then your problem. I also stumbled upon it.
Best Greetings FlionkJ

9 months later

Hello! I've faced the same issue. But I did not understand: is there a solution and what?

    9 days later

    mixeme Hey, the solution is to leave this line as I wrote it above. They've given us the option to customize it in the server image they've delivered so far, but somewhere in other settings files they forgot to change it from a fixed, predefined value to a variable that we can change. Therefore, it only works if you leave the line as it is. As soon as they publish their server code and provide an update, I think we'll be able to change it, but unfortunately, as of now, it's not possible...
    Best Greetings FlionkJ