Discourse-app container starts then silently stops

installation
#23

Then you need to configure that nginx to proxy to discourse.

I recommend that you just spin up a fresh vm just for Discourse.

1 Like
#24

Sorry Stephen for the confusion, I just used the name of the tool which is referenced in the article. I understand that NPM and nginx (as a) proxy manager are different things, this is why I used capital letters…

#25

This is exactly what I’m trying to do and I understand you cannot support on this. However, any hint / link would be appreciated!

I just can’t Jay: I’m trying to help a friend deploying the app and can’t modify their server configuration. This is why I have to fix the nginx issue…

By the way, my understanding is:

  • Discourse is listening on ports 80/443.
  • nginx is playing the role of a switch, dispatching requests to different applications, base on their domain name:
    • netxcloud.mydomain.com trying to reach the port 80 → request is routed to server_IP:8000
    • crm.mydomain.com trying to reach the port 80 → request is routed to server_IP:9000
    • discourse.mydomain.com trying to reach the port 80 → request is routed to http://unix:/var/discourse/shared/standalone/nginx.http.sock: (hope the trailing colon is not a typo) as the setupo script has configured discourse to listen to this socket.

Am I right on this?

Thanks a lot for your help!

#26

That is rather annoying and confusing, but to be fair to @jlgarnier, that acronym was first used by either @tophee or @pfaffman in Using Nginx Proxy Manager to manage multiple sites with Discourse to refer to Nginx Proxy Manager. I don’t love it, but if it is ‘wrong’, that isn’t really OP’s fault.

For example, the topic has a section called Install NPM focusing entirely on Nginx Proxy Manager.

#27

Wow, that fooled me as well.
Annoying how that project hijacked an existing acronym eight years after the original.

2 Likes
#28

I’m not sure that it has; I’ve browsed their site & not seen them use the acronym themselves.

#29

They do use it in their Docker setups. nginx-proxy-manager/docker-compose.dev.yml at develop · NginxProxyManager/nginx-proxy-manager · GitHub

services:
  npm:
    image: nginxproxymanager:dev
    container_name: npm_core
1 Like
#30

Ah, oops! I hadn’t realised that. :slightly_smiling_face:

#31

Hi all,

I’ll try to setup nginx again this afternoon. Can anyone confirm the exact syntax for the socket: http://unix:/var/discourse/shared/standalone/nginx.http.sock:? I want to make sure that the trailing colon is not a typo…

Thanks in advance for any help!

#32

I don’t think that colon should be there, no.

#33

Indeed… I’ve applied in discourse.conf the modifications I proposed last Friday and Discourse now runs fine! At least I can reach the welcome page but I don’t receive the activation mail, which is not related to Discourse (I suspect my friend didn’t create the requested mail account :blush:).

I owe you a warm thank you for the help you provided and hope I won’t come back on this forum too soon! :wink:

2 Likes
#34

Finally, back sooner than expected but you’ll probably be able to kick me off with your great suggestions! :grin:

The situation is:

  • Discourse up and running, Docker (or Portainer) indicates the container is healthy and I can reach the welcome page forums.mydomain.com.
  • I don’t receive any activation mail, despite the technical mail account has been properly created (hosting provider = OVH).
  • I’ve tested sending an email from this technical account (with the config below) = OK.
  • The current mail config is:
DISCOURSE_SMTP_ADDRESS: ssl0.ovh.net
DISCOURSE_SMTP_PORT: 465
DISCOURSE_SMTP_USER_NAME: forums@mydomain.com
DISCOURSE_SMTP_PASSWORD: "Str0ngPassw0rd"
DISCOURSE_SMTP_ENABLE_START_TLS: false
DISCOURSE_SMTP_DOMAIN: mydomain.com
DISCOURSE_NOTIFICATION_EMAIL: noreply-forums@mydomain.com

I don’t really know where I should start investigating and would be happy with any advice!

Thanks in advance for your help!

#35

First thing I’ll check is that if forums@mydomain.com has been configured to send on behalf of noreply-forums@mydomain.com it needs to be checked at your email provider.

1 Like
#36

I’m not sure this address can send ‘on behalf on’, so I’ve updated app.yml to set the same address:

DISCOURSE_SMTP_ADDRESS: ssl0.ovh.net
DISCOURSE_SMTP_PORT: 465
DISCOURSE_SMTP_USER_NAME: forums@mydomain.com
DISCOURSE_SMTP_PASSWORD: "Str0ngPassw0rd"
DISCOURSE_SMTP_ENABLE_START_TLS: false
DISCOURSE_SMTP_DOMAIN: mydomain.com
DISCOURSE_NOTIFICATION_EMAIL: forums@mydomain.com

Tried to telnet ssl0.ovh.net 465 = OK

However discourse-doctor reports:

========================================
Discourse 2.9.0.beta9
Discourse version at forums.mydomain.com: Discourse 2.9.0.beta9
Discourse version at localhost: NOT FOUND
==================== DNS PROBLEM ====================
This server reports NOT FOUND, but forums.mydomain.com reports Discourse 2.9.0.beta9 .
This suggests that you have a DNS problem or that an intermediate proxy is to blame.

[...]

Testing sending to myprivatemail@yahoo.fr using ssl0.ovh.net:465, username:forums@mydomain.com with plain auth.
======================================== ERROR ========================================
                                    UNEXPECTED ERROR

Net::ReadTimeout

====================================== SOLUTION =======================================

Could the mail issue be linked to the alleged DNS issue? I don’t have an “intermediate proxy”, just running nginx as the proxy web server…

#37

This is probably your problem. Can you try a different port? I’ve seen best results with port 587 if that’s supported by your email provider.

You’ll need to comment this out or set it to true if you change port to 587

#38

No, my email provider (same as hosting provider) only allows port 465. By the way, I’ve read that I need to set SPF and DKIM record for the domain (is this subdomain?) and I didn’t set any of these yet: could this have any impact?

#39

See Troubleshoot email on a new Discourse install

1 Like
#40

I’m browsing the post but I’ve forgotten some information:

  • The DNS is managed by our hosting provider (for some services), let’s say on ServerA.
  • Discourse is running on another server (ServerB) which is hosted by a different provider.

My understanding is then: Discourse on ServerB connects to the mail server on ServerA, authenticating with email/password to use the SMTP service provided by ServerA hosting provider.

Is this a abnormal config or may I still use the normal app.yml email config here?

#41

Hurray! It seems my email provider finally accepts the port 587 and I’ve correctly received the activation mail! The whole app in now up and running and I’m gonna dig into all settings…

Thanks a lot to all of you, thanks for the helping hand!

2 Likes
#42

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.