You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Unable to connect to MongoDB Atlas Cluster.
2026-08-17T08:49:29 ERROR --- MongoDB Connection Error Details ---
2026-08-17T08:49:29 ERROR Target Host: somecluster-shard-00-00.tnoyu.azure.mongodb.net:27017
2026-08-17T08:49:29 ERROR Error Kind: ServerSelection { message: "Server selection timeout: No available servers. Topology: { Type: Unknown, Servers: [ { Address: somecluster-shard-00-00.tnoyu.azure.mongodb.net:27017, Type: Unknown, Error: Kind: I/O error: unexpected end of file, labels: {}, source: None, server response: None } ] }" }
2026-08-17T08:49:29 ERROR Full Error: Kind: Server selection timeout: No available servers. Topology: { Type: Unknown, Servers: [ { Address: somecluster-shard-00-00.tnoyu.azure.mongodb.net:27017, Type: Unknown, Error: Kind: I/O error: unexpected end of file, labels: {}, source: None, server response: None } ] }, labels: {}, source: None, server response: None
2026-08-17T08:49:29 ERROR Check you database network connectivity
To Reproduce
Create a free MongoDB Cluster at mongodb.com and create a databases.json with the provided connection details
Expected behavior
A working database connection.
It would be nice if we can pass in some additional connection parameters. At the moment the only connection parameter is authSource=admin and there seems no option to provide additional parameters
Thanks for that issue. There was an issue with cloud MongoDB databases, and a fix is currently in progress: Portabase/agent#96
Regarding custom options, they will be available soon. We have already started implementing this for PostgreSQL through the options key in database.json, and more options will come once we release the ability to configure databases directly from the dashboard for those who do not want to use database.json.
Both methods will be supported and compatible: databases configured through database.json and databases configured directly from the dashboard.
It's woking fine for me. Can I suggest to also update the docs so it's clear for everyone that for the MongoDB settings you can drop the port number and it will use the MongoDB SRV connection string.
Activity
RambokDev commentedon Aug 17, 2026
Hi @mikevdberge,
Thanks for that issue. There was an issue with cloud MongoDB databases, and a fix is currently in progress: Portabase/agent#96
Regarding custom options, they will be available soon. We have already started implementing this for PostgreSQL through the
optionskey indatabase.json, and more options will come once we release the ability to configure databases directly from the dashboard for those who do not want to usedatabase.json.Both methods will be supported and compatible: databases configured through
database.jsonand databases configured directly from the dashboard.I’ll keep you updated once it is released.
{ "name": "MongoDB Cluster Cloud", "database": "xxxxxxx", "type": "mongodb", "username": "xxxxx", "password": "xxxxxx", "host": "xxxx.xxxx.mongodb.net", "generated_id": "xxxxx" }Feel free to test it once released and provide feedback.
Regards,
[-]Unable to connect to MongoDB Atlas clustere[/-][+]Unable to connect to MongoDB Atlas Cluster[/+]RambokDev commentedon Aug 17, 2026
The fix is available in agent version 1.18.6. If the issue still persists, feel free to ask for it to be reopened.
Regards,
mikevdberge commentedon Aug 17, 2026
It's woking fine for me. Can I suggest to also update the docs so it's clear for everyone that for the MongoDB settings you can drop the port number and it will use the MongoDB SRV connection string.
RambokDev commentedon Aug 17, 2026
Yes, I will update the documentation accordingly. I was waiting for your feedback.
Regards,