• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Install docker image (RocketChat), on a domain / webhotel.

I have opened the firewall ports incoming/outgoing as advised.
I think that, @Hangover2 suggests to open the 27018 port because it is used in mongo DB config in manual port mapping.
But on your screenshot I see that you are using mapping 27017 -> 27017. In that case I think you need to open the 27017 port, not the 27018. Probably that's the reason of connection timeout.
1729522205098.png
 
I think that, @Hangover2 suggests to open the 27018 port because it is used in mongo DB config in manual port mapping.
But on your screenshot I see that you are using mapping 27017 -> 27017. In that case I think you need to open the 27017 port, not the 27018. Probably that's the reason of connection timeout.
View attachment 27228
I tested that and opened the firewall port too, but too no avail. Same annoying error: MongoServerSelectionError: Server selection timed out after 30000 ms.
I've run out of ideas of what to do. I'm soon at the point where I think I'll just setup a new separate server at our company instead because that would be much faster.
 
@LionKing
Is it really necessary with such high permissions on the those folders?
I mean 777 opens for the whole internet in theory... (Although it is not really a internet served directory)
Why not just 755 instead for example?
"777" permissions are required; otherwise, the MongoDB startup script cannot create its own data structure as the mongodb user, which is created during the image build process.

Regarding your problems: I think you might have a firewall or network issue. However, you could try using the standard port and localhost if you only have one Rocket.Chat instance on the server. In that case, the external port does not need to be opened (Manual mapping 2017 => 2017).

Code:
MONGODB_ADVERTISED_HOSTNAME: 127.0.0.1
MONGODB_ADVERTISED_PORT_NUMBER: 27017
MONGODB_INITIAL_PRIMARY_PORT_NUMBER: 27017
MONGODB_PORT_NUMBER: 27017

Of course, also change the connection strings of Rocket.Chat to use this new port and localhost.
 
Back
Top