Running other websites on the same machine as Discourse

If you want to run other websites on the same machine as Discourse, you need to set up an extra NGINX or HAProxy proxy in front of the Docker container.

NOTE: This is for advanced admins

This guide assumes you already have Discourse working - if you don’t, it may be hard to tell whether or not the configuration is working.

You cannot use ./discourse-setup to set up Discourse if another server is using port 80 or 443. You will need to copy and edit samples/standalone.yml with your favorite text editor.

Install nginx outside the container

First, make sure the container is not running:

cd /var/discourse
./launcher stop app

Then install nginx:

sudo apt-get update && sudo apt-get install nginx

Change the container definition

This is where we change how Discourse actually gets set up. We don’t want the container listening on ports - instead, we’ll tell it to listen on a special file.

Change your /var/discourse/containers/app.yml to look like this:

# base templates used; can cut down to include less functionality per container templates:
  # - "templates/cron.template.yml" # cron is now included in base image
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/sshd.template.yml"
  - "templates/web.template.yml"
  # - "templates/web.ssl.template.yml" # remove - https will be handled by outer nginx
  - "templates/web.ratelimited.template.yml"
  - "templates/web.socketed.template.yml"  # <-- Added

Be sure to remove or comment out the exposed ports by putting a # in front.

# which ports to expose?
# expose: comment out entire section by putting a # in front of each line
# - "80:80"   # http
# - "443:443" # https

If you are using some other reverse proxy that cannot use a web socket, you can instead expose a different port in the section above like - 8080:80.

Create an NGINX ‘site’ for the outer nginx

For an HTTPS site, put this in /etc/nginx/sites-enabled/discourse.conf, making sure to change the server_name:

server {
    listen 80; listen [::]:80;
    server_name forum.example.com;  # <-- change this

    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;  listen [::]:443 ssl http2;
    server_name forum.example.com;  # <-- change this

    ssl_certificate      /var/discourse/shared/standalone/ssl/ssl.crt;
    ssl_certificate_key  /var/discourse/shared/standalone/ssl/ssl.key;
    ssl_dhparam          /var/discourse/shared/standalone/ssl/dhparams.pem;
    ssl_session_tickets off;
    ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA;

    http2_idle_timeout 5m; # up from 3m default

    location / {
        proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

For an HTTP-only site (not recommended, but left here for historical purposes):

server {
	listen 80; listen [::]:80;
	server_name forum.example.com;  # <-- change this

	location / {
		proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:;
		proxy_set_header Host $http_host;
		proxy_http_version 1.1;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_set_header X-Forwarded-Proto $scheme;
		proxy_set_header X-Real-IP $remote_addr;
	}
}

Make sure that the default site is either disabled or has the correct server_name set.

Then, in a shell:

# Make sure that Discourse isn't running
/var/discourse/launcher stop app || true

# test configuration
sudo nginx -t
# Important: If nginx -t comes back with an error, correct the config before reloading!
sudo service nginx reload

# Rebuild the container to apply changes
/var/discourse/launcher rebuild app

Create your other sites

You’re done with the Discourse section!

Make other NGINX “sites”, then link and enable them, as in the last step above.

Tips

  • sudo netstat -tulpn : This will tell you what ports are being used
  • /var/log/nginx/error.log : Is the location of the nginx log on ubuntu. This will tell you what the error is when you get a 502 Bad Gateway error.
107 Likes
Port already in use, what to do?
Best way to install Discourse on my server?
Multisite configuration with Docker
Installing Discourse Under Nginx
Nginx configuration for discourse
[Solved] Help setting other websites on the same DigitalOcean droplet
Setting up nginx for use with Discourse
Discourse + Nginx reverse Proxy
Nginx + discourse
Can't make Discourse accessible through Apache
Using Multiple Websites with Nginx + Discourse
Faster rebuilds?
Adding an offline page when rebuilding
Nginx configuration for discourse
A better "site not available" page
Wordpress and Discourse in a single droplet
Discourse not working through separate nginx docker
Wordpress and discourse on the same server
NGINX proxy in front of the Docker container.errors
Using Discourse With Other Sites on Same Droplet
Disable direct access with port (nginx)
Discourse doesn't deliver webpages, fresh install on Linode Ubuntu 14.04
Installing docker on an already running web server?
Which performance is better if discourse or phpbb hosts on a same vps?
403 forbidden after installation
Launcher rebuild app failing: repository name must be lowercase [SOLVED]
Nginx configuration for discourse
Port already in use, what to do?
Problem with discourse in a subfolder
NGINX proxy in front of the Docker container.errors
Custom Intro page for discourse
Setting up Discourse on a VPS with other sites
Starting a second Discourse forum on the same VPS
Broken images inside posts
Multiple container setup problems
Bad gateway when trying to use SSL
Wrong sending domain used
Wordpress integration with mini forums
How can one install a panel with discourse?
Backup uploads terribly slow
Adding an offline page when rebuilding
Accessing to the database from outside the container
How to change the port from docker - help
Discourse stopped working after installing Plesk
Discourse blocking with password reset
Difference between socket- and port-based connection to outer NGINX?
429 error when opening multiple topics
Nginx configuration for discourse
Discourse with zpanel
Custom Layouts Plugin
Setting up HTTPS support with Let's Encrypt
Setting up HTTPS support with Let's Encrypt
Setting up Discourse on a VPS with other sites
Put forum under sub-domain and have website
What is the best way to install Discourse Forum on a Proxmox VM and expose it on the internet
Can Discourse ship frequent Docker images that do not need to be bootstrapped?
Can Discourse ship frequent Docker images that do not need to be bootstrapped?
IP Spoofing Attack
Error while doing discourse setup
Nginx + discourse
Run other php script
Where to put custom content?
Domain names pointing with shared AWS instance
How to install discourse on hosting?
Can not visit forum.abc.com again after port change to container/app/yml
Error connecting to Redis
Advice on integrating into a Docker-Compose setup?
WARNING: Port 443 of computer does not appear to be accessible using hostname
Installation on v-server as a subfolder with other services in subfolders using apache
Installation on v-server as a subfolder with other services in subfolders using apache
Installation on v-server as a subfolder with other services in subfolders using apache
Wanting to run Discourse alongside apache
Install Order on CentOS
Add subdomain exception to nginx to host another site on same host
Docker0 Missing (OpenVZ)
[SOLVED] How do you install Discourse and Ghost on the same server using Nginx?
Domain names pointing with shared AWS instance
Nginx rate limiting outside of container - any tips?
Sandbox and test discourse on host?
Best approach for test and production instance of discourse
How should I enable letsencrypt while discourse is beside other websites
Redirecting old forum URLs to new Discourse URLs
Mixed content for icon using http on https setup
How do I do what I did in htaccess in nginx?
How do I do what I did in htaccess in nginx?
Address already in use during setup
CDN causes white screen
What is the recommended practice for WordPress and Discourse on the same server?
Discouse passes localhost uri as oauth redirect_uri
Webhooks/Sidekiq issue on dev instance
[SOLVED] How do you install Discourse and Ghost on the same server using Nginx?
Using a certificate when Discourse is installed behind a reverse proxy
Can I run wordpress in the same VPS with a second IP?
Can't get Discourse to work on different ports
ERR_SSL_PROTOCOL_ERROR with Letsencrypt
Using a certificate when Discourse is installed behind a reverse proxy
Generals Subfolder recommendations and tips
Wordpress + Discourse using Digital Ocean and Serverpilot
Unsure About How to Start a Website Project
Installation on Ubuntu 14.04 LTS + Apache 2 + Plesk 12
Install on vps problem?
Install discourse alongside WordPress in a dedicated server
Installation Help required
Installed OK. Working fine for one day. Suddenly stopped working
SSL received a record that exceeded the maximum permissible length
Changing Max Attachment Size
Moved from PluXml and phpBB to Wordpress and Discourse, my all-new experience :tada:
Discourse site loads via IP but via domain only header
Configuring Website with Discourse and Wordpress?!
Looking for a tutorial on discourse/wordpress 1 machine install
[Solved] Dev instance with nginx: topic preview not working
Setting up Discourse on a machine with existing Nginx
Regenerating LetsEncrypt keys from behind nginx
Blank pages, 500 errors and no logs
Remote users IPV6 address shows as localhost
I have a VPS and it nginx installed and now i want install discourse in subdomain how i can do that
Not able to send email Net::ReadTimeout
Adding an offline page when rebuilding
[SOLVED] 502 Gateway Error on Nginx?
URLs for avatars & emoticons adding :80 to the end of the domain
OpenID Connect extension not creating new Discourse users
Install Problem on a Custom Server with Nginx
Address already in use during setup
Discourse socketed: Nginx in front of discourse: no IP adresses
Installed discourse on a server that already runs a webserver, domain just redirects to subdomain
Installation fails on my Debian server
After upgrade, Connection refused while connecting to upstream
Error in installing
Discourse new Base Image
FAILED to rebuild discourse -- OpenURI::HTTPError: 401 Error: Invalid license key
How to install Discourse on Plesk?
Direct-delivery incoming email for self-hosted sites
Discourse with Traefik 2.0
Can I install Discourse on existing server that uses Nginx?
How to add a subdomain on a different droplet/server?
More than one site as different container running on the same do server
Can I have two domains pointing towards the same IP address without redirect?
Postgres already running
Install Discourse on a droplet with WordPress served by Apache?
Multiple Standalone containers instead of multisite?
Success - New Multisite Install on Dedicated server using ServerPilot, Nginx and Apache
Discourse not showing up at specified hostname
OpenID Connect Authentication Plugin
How to collect all static assets (js, css) used by discourse
Avatar, Site Logos, and Cert Errors
Runing Discourse Along a Wordpress Website
Discourse and WordPress installation on one ubuntu desktop
Can I Host More Than 1 Thing On My VPS?
Discourse won't start because port 80 is in use
How to make Discourse coexist with nginx on a Debian 9 server?
Is it possible the certbot inside the container can affect new certbot outside it?
Prometheus exporter plugin for Discourse
Multisite configuration with Docker
Discourse + web server. Possible or better to avoid?
Help for installing Discourse alongside Apache2
502 Gateway Error: Discourse Installation with SSL form Cloudflare
Installation of Wordpress and Discourse same domain same server?
I can't set nginx: [emerg] cannot load certificate "/var/discourse/shared/standalone/ssl/ssl.crt": BIO_new_file() failed
Discourse with other websites, SMTP issue: End of file reached
Error: Slow down, too Many Requests from this IP Address
Links in emails are using http instead of https
Google auth error
Anything else on same Digital Ocean droplet as Discourse?
Multiple discourse installation on single droplet
Global rate limits and throttling in Discourse
Help understanding the structure of using discourse + static website
Multiple discourse installation on single droplet
Checking domain name fails behind NGINX proxy
OpenID Connect Authentication Plugin
How to Docker+Discourse and Apache too?
Changing force_https does not update the url of uploaded images causing a mixed content warning
Running Discourse alongside LAMP
Moving to subdomain
Deploying discourse on server already running another rails app
How do I install multiple discourse forums on a root server?
How to upload files in root directory?
How should I enable letsencrypt while discourse is beside other websites
WordPress, Discourse and Local SMTP Server
Default app.yml file anywhere?
How to install wordpress in the Secondary directory?
Oauth2 redirect_uri uses HTTP when my forum is using HTTPS
502 Bad gateway error after switching to SSL
Wrong sending domain used

The guide in the first post is great and, on the whole, still works just fine :sunny:

There are three things worth noting:

  1. I initially missed some of the app.yml changes. There are 3 things you need to change in your app.yml. If you miss any of these things it won’t work:

    1. Comment out all ssl templates in the templates. If you are using letsencrypt you will have two:
      # - "templates/web.ssl.template.yml"
      # - "templates/web.letsencrypt.ssl.template.yml"
      
    2. Add a socket template:
      - "templates/web.socketed.template.yml" 
      
    3. Comment out all exposed ports:
      # - "80:80"   # http
      # - "443:443" # https
      
  2. As others mentioned, I had to change the ssl cert and key names in the discourse.conf:

    ssl_certificate      /var/discourse/shared/standalone/ssl/discourse.angusmcleod.com.au.cer;
    ssl_certificate_key  /var/discourse/shared/standalone/ssl/discourse.angusmcleod.com.au.key;
    
  3. Turns out my site didn’t have a dhparams.pem key (dh stands for Diffie Hellman, there’s some good explanations of what this is here). You can generate this yourself:

    openssl dhparam -out /var/discourse/shared/standalone/ssl/dhparams.pem 2048
    

Some other things you may find useful:

  • sudo netstat -tulpn: This will tell you what ports are being used

  • /var/log/nginx/error.log: Is the location of the nginx log on ubuntu. This will tell you what the error is when you get a 502 Bad Gateway error.

  • You may finish a ./launcher rebuild app, excitedly go to your domain to see if it worked and be greeted with a depressing 502 Bad Gateway error. Before giving up in frustration, try restarting nginx one more time:

    sudo service nginx restart

    This clinched it for me.

Now my sandbox is using nginx outside the container (although I haven’t added the extra website yet).

30 Likes

Hi,

I am just doing a fresh install of Discourse.
I am very surprised that :

  • The setup script does not simply allow to setup on a different port, disabling SSL support, and then it’s up to us to do reverse proxy as we want (Apache, Nging) : It seems such a common setup, it would save hundreds of hours of life to humanity
  • I am even more surprised that the setup redirects us to an outdated forum topic, in which we need to dig for the proper information, instead of a proper documentation page, kept up to date.

Thanks guys anyway for your work, but I think there is room for improvement here.
Cheers

5 Likes

Just wanted to share how I accomplished this, it was a little easier than I first thought.

From an already running machine, with Caddy acting as a reverse proxy for a number of existing Docker containers already.

  1. Clone discourse as per the official instructions
  2. Copy /var/discourse/samples/standalone.yml -> /var/discourse/containers/app.yml
  3. Fill in SMTP settings and website address
  4. Comment out 443:443 from the expose: section
  5. Replace 80:80 -> 3001:80, 3001 being the port I’m serving via Caddy
  6. Run ./launcher rebuild app
  7. Done

Whop!

7 Likes

@TheBestPessimist I swapped the order of the HTTP/HTTPS sections, it works better than adding a “don’t do this!” notice :slight_smile:

6 Likes

I would recommend just doing double NGINX, it is far more complex to set it up direct and has virtually no performance cost. Getting it right would be very hard cause we serve some files direct and have a layer of caching that is tricky to configure.

Note, customizing NGINX is easy with mixin templates have a look at the various example templates here: discourse_docker/templates at master · discourse/discourse_docker · GitHub

6 Likes

PSA: If you want to allow uploads larger than 1MB to your site, you’ll also have to set client_max_body_size 100M in any nginx config that sits in front of your site.

For reference, here’s the full nginx config I use:

nginx config for other sites on same host
server {
    if ($host = discourse.mysite.org) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


    if ($host = backupname.mysite.org) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80; listen [::]:80;
    server_name discourse.mysite.org;
    server_name backupname.mysite.org;

    location / {
        proxy_pass http://unix:/var/discourse/shared/mysite/nginx.http.sock:;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

# nginx 1.14.1 | intermediate profile | OpenSSL 1.1.0f | link

server {
    listen 443 ssl http2;  listen [::]:443 ssl http2;
    server_name discourse.mysite.org;
    server_name backupname.mysite.org;

    # from discourse examples
    http2_idle_timeout 5m; # up from 3m default
    client_max_body_size 50M; # allow 50M uploads

    location / {
        proxy_pass http://unix:/var/discourse/shared/mysite/nginx.http.sock:;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
        proxy_set_header X-Real-IP $remote_addr;
    }
    ssl_certificate /etc/letsencrypt/live/backupname.mysite.org/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/backupname.mysite.org/privkey.pem; # managed by Certbot

    ###### https://mozilla.github.io/server-side-tls/ssl-config-generator/ ####

    ssl_session_timeout 1d;
    ssl_session_cache shared:SSL:50m;
    ssl_session_tickets off;

    # modern configuration. tweak to your needs.
    ssl_protocols TLSv1.2;
    ssl_ciphers 'ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256';
    ssl_prefer_server_ciphers on;

    # HSTS (ngx_http_headers_module is required) (15768000 seconds = 6 months)
    add_header Strict-Transport-Security max-age=15768000;

    # OCSP Stapling ---
    # fetch OCSP records from URL in ssl_certificate and cache them
    ssl_stapling on;
    ssl_stapling_verify on;

    ## verify chain of trust of OCSP response using Root CA and Intermediate certs
    ssl_trusted_certificate /etc/letsencrypt/live/backupname.mysite.org/chain.pem;

    resolver 1.1.1.1;

}
9 Likes

Hey, Having the exact same issue as you… Did you find any help?

Thank you

1 Like

The easiest thing to do will be to spin up a new server and see how it works, then copy your working yml files to your existing server.

1 Like

I’m following these instructions but it’s ending up with this error message.

docker: Error response from daemon: driver failed programming external connectivity on endpoint app (6ab29aff53412854ab35ebf44295c9017bfd6b6909841d977ab7490be8a9c0f7): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use.

I ran this to build the app.

/var/discourse/launcher rebuild app

Here’s my app.yml file.

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"
  - "templates/web.socketed.template.yml"  # <-- Added

expose:
  - "80:80"   # http
  - "443:443" # https

params:
  db_default_text_search_config: "pg_catalog.english"

env:
  LC_ALL: en_US.UTF-8
  LANG: en_US.UTF-8
  LANGUAGE: en_US.UTF-8

  DISCOURSE_HOSTNAME: 'forum.*******.net'
  DISCOURSE_DEVELOPER_EMAILS: 'support@******.net'
  DISCOURSE_SMTP_ADDRESS: smtp.eu.mailgun.org
  DISCOURSE_SMTP_PORT: 587
  DISCOURSE_SMTP_USER_NAME: postmaster@mailer.**********.net
  DISCOURSE_SMTP_PASSWORD: 73e57****************fef-21430d9f

volumes:
  - volume:
      host: /var/discourse/shared/standalone
      guest: /shared
  - volume:
      host: /var/discourse/shared/standalone/log/var-log
      guest: /var/log

hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git

run:
  - exec: echo "Beginning of custom commands"
  - exec: echo "End of custom commands"

…and the server is:

server {
    listen 80; listen [::]:80;
    server_name support.*********.net;  

    return 301 https://$host$request_uri;
}

server {
    listen 443 ssl http2;  listen [::]:443 ssl http2;
    server_name support.*********.net;  

    ssl_certificate      /var/discourse/shared/standalone/ssl/ssl.crt;
    ssl_certificate_key  /var/discourse/shared/standalone/ssl/ssl.key;
    ssl_dhparam          /var/discourse/shared/standalone/ssl/dhparams.pem;
    ssl_session_tickets off;
    ssl_ciphers ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:ECDHE-RSA-DES-CBC3-SHA:ECDHE-ECDSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA;

    http2_idle_timeout 5m; # up from 3m default

    location / {
        proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:;
        proxy_set_header Host $http_host;
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto https;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

What I’m missing here or what’s wrong? :thinking:

BTW, I did run the syntax error command, and here’s the output. I ignored this warning because was expecting that the setup will install the certificate?

nginx -t
nginx: [emerg] cannot load certificate “/var/discourse/shared/standalone/ssl/ssl.crt”: BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen(’/var/discourse/shared/standalone/ssl/ssl.crt’,‘r’) error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

You need not to expose port 443,and if you’re using the socket, you don’t need port 80 either.

Thanks, I have commented ports in app and then ran the rebuilt app again, now it ended without any errors but when I’m checking the URL that’s still showing up the NGINX holding page. Where I can see what’s going on or how it went?

yes, with the appropriate templates in the app.yml I believe.
But

There it’s saying that I need to expose ports but I just had removed them as @pfaffman suggested. How do I go with this?

I think that, as you are using the web.socketed.template.yml, you should be using a let’s Encrypt client on your host system (and not expose the ports as Jay said)

Thanks, I have the template block and env as below;

templates:
  - "templates/postgres.template.yml"
  - "templates/redis.template.yml"
  - "templates/web.template.yml"
  - "templates/web.ratelimited.template.yml"
  - "templates/web.socketed.template.yml"  # <-- Added
  - "templates/web.ssl.template.yml"
  - "templates/web.letsencrypt.ssl.template.yml"

env:
  LC_ALL: en_US.UTF-8
  LANG: en_US.UTF-8
  LANGUAGE: en_US.UTF-8
  LETSENCRYPT_ACCOUNT_EMAIL: 's*****@*******.net'

Then rebuilt the app and but no luck and still the default holding page even when I load that with HTTPS with certification warning ignored.

If you’re using the socketed template, then you certainly don’t need the ssl or letsencrypt templates since you’re doing that outside of the container. I recommend that you spin up a new VM and start with a simple install and then go about adding the reverse proxy once you’ve got that going.

2 Likes

Please tell what to do, When using Cloudflare,
I uses Cloudflare SSL in my all sites.

See the instructions and warnings here: Full site CDN acceleration for Discourse

1 Like

cloudflare.template.yml

# - "templates/web.cloudflare.ssl.template.yml

I have to write both or only 2nd one in app.yml or is there anything to edit???

I am sorry for silly question please tell me I am beginner