mongo Connection not authenticating #132

New Issue

2026-02-16T12:51:35-05:00

yindo commented

2026-02-16 12:51:35 -05:00

Originally created by @seva-luchianov on GitHub (Feb 12, 2026).

running docker compose up has everything firing up, but seeing many instances of this message looping in the logs:

database-1       | {"t":{"$date":"2026-02-12T18:37:37.630+00:00"},"s":"I",  "c":"ACCESS",   "id":10483900,"ctx":"conn39","msg":"Connection not authenticating","attr":{"client":"127.0.0.1:37542","doc":{"application":{"name":"mongosh 2.6.0"},"driver":{"name":"nodejs|mongosh","version":"6.19.0|2.6.0"},"platform":"Node.js v20.20.0, LE","os":{"name":"linux","architecture":"x64","version":"3.10.0-327.22.2.el7.x86_64","type":"Linux"},"env":{"container":{"runtime":"docker"}}}}}

Maybe a similar issue to https://github.com/stoatchat/self-hosted/issues/186, as I am also able to create an account but then am hit with an error trying to log in.

I DID update the nginx conf to handle the ws route properly as detailed in the linked issue, which got rid of a caddy error from the docker logs when I was seeing on login (detailed in https://github.com/stoatchat/self-hosted/issues/162#issuecomment-3887148863)
Sadly I still have the same "An error occured, see console" popup even with the nginx fixes. I assume it's related to this mongo connection issue since I do not see any other errors in the docker logs.

Originally created by @seva-luchianov on GitHub (Feb 12, 2026). running docker compose up has everything firing up, but seeing many instances of this message looping in the logs: ``` database-1 | {"t":{"$date":"2026-02-12T18:37:37.630+00:00"},"s":"I", "c":"ACCESS", "id":10483900,"ctx":"conn39","msg":"Connection not authenticating","attr":{"client":"127.0.0.1:37542","doc":{"application":{"name":"mongosh 2.6.0"},"driver":{"name":"nodejs|mongosh","version":"6.19.0|2.6.0"},"platform":"Node.js v20.20.0, LE","os":{"name":"linux","architecture":"x64","version":"3.10.0-327.22.2.el7.x86_64","type":"Linux"},"env":{"container":{"runtime":"docker"}}}}} ``` Maybe a similar issue to https://github.com/stoatchat/self-hosted/issues/186, as I am also able to create an account but then am hit with an error trying to log in. I _DID_ update the nginx conf to handle the ws route properly as detailed in the linked issue, which got rid of a **caddy** error from the docker logs when I was seeing on login (detailed in https://github.com/stoatchat/self-hosted/issues/162#issuecomment-3887148863) Sadly I still have the same "An error occured, see console" popup even with the nginx fixes. I assume it's related to this mongo connection issue since I do not see any other errors in the docker logs.

yindo referenced this issue

2026-02-16 12:51:42 -05:00

[PR #132] [MERGED] readme: fix link for GHSA-8684-rvfj-v3jq advisory #170

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: stoatchat/self-hosted#132