So hi, I’m having an issue with installing Discourse, everytime I try to connect to my website, I have an infinite 301 redirect Here is my HOST nginx configuration of the discourse instance server { server_name dis.ob**********ie.fr; access_log /var/log/nginx/dis_access.log; error_log /var/log/nginx/dis_error.log; location / { proxy_pass http://dis.ob**********ie.fr:8150; #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; } listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/dis.ob**********ie.fr/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/dis.ob**********ie.fr/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = dis.ob**********ie.fr) { return 301 https://$host$request_uri; } # managed by Certbo server_name dis.ob**********ie.fr; listen 80; return 404; # managed by Certbot } Here is my app.yml templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" - "templates/web.socketed.template.yml" ## Uncomment these two lines if you wish to add Lets Encrypt (https) - "templates/web.ssl.template.yml" - "templates/web.letsencrypt.ssl.template.yml" ## which TCP/IP ports should this container expose? ## If you want Discourse to share a port with another webserver like Apache or nginx, ## see https://meta.discourse.org/t/17247 for details expose: - "8150:80" # http params: db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to a max of 25% of the total memory. ## will be set automatically by bootstrap based on detected RAM, or you can override db_shared_buffers: "1024MB" ## can improve sorting performance, but adds memory usage per-connection #db_work_mem: "40MB" ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed env: LC_ALL: fr_FR.UTF-8 LANG: fr_FR.UTF-8 LANGUAGE: fr_FR.UTF-8 EMBER_CLI_PROD_ASSETS: 1 # DISCOURSE_DEFAULT_LOCALE: en ## How many concurrent web requests are supported? Depends on memory and CPU cores. ## will be set automatically by bootstrap based on detected CPUs, or you can override UNICORN_WORKERS: 4 ## TODO: The domain name this Discourse instance will respond to ## Required. Discourse will not work with a bare IP number. DISCOURSE_HOSTNAME: dis.ob**********ie.fr ## Uncomment if you want the container to be started with the same ## hostname (-h option) as specified above (default "$hostname-$config") DOCKER_USE_HOSTNAME: true ## TODO: List of comma delimited emails that will be made admin and developer ## on initial signup example 'user1@example.com,user2@example.com' DISCOURSE_DEVELOPER_EMAILS: 'admin@ob**********ie.fr ## TODO: The SMTP mail server used to validate new accounts and send notifications # SMTP ADDRESS, username, and password are required # WARNING the char '#' in SMTP password can cause problems! DISCOURSE_SMTP_ADDRESS: mail.ob**********ie.fr DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: discourse@ob**********ie.fr DISCOURSE_SMTP_PASSWORD: "*********************" #DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true) DISCOURSE_SMTP_DOMAIN: ob**********ie.fr DISCOURSE_NOTIFICATION_EMAIL: noreply@ob**********ie.fr ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate LETSENCRYPT_ACCOUNT_EMAIL: me@example.com ## The http or https CDN address for this Discourse instance (configured to pull) ## see https://meta.discourse.org/t/14857 for details #DISCOURSE_CDN_URL: https://discourse-cdn.example.com ## The maxmind geolocation IP address key for IP address lookup ## see https://meta.discourse.org/t/-/137387/23 for details #DISCOURSE_MAXMIND_LICENSE_KEY: 1234567890123456 ## The Docker container is stateless; all data is stored in /shared volumes: - volume: host: /var/discourse/shared/standalone guest: /shared - volume: host: /var/discourse/shared/standalone/log/var-log guest: /var/log ## Plugins go here ## see https://meta.discourse.org/t/19157 for details hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/discourse/docker_manager.git ## Any custom commands to run after building run: - exec: echo "Beginning of custom commands" ## If you want to set the 'From' email address for your first registration, uncomment and change: ## After getting the first signup email, re-comment the line. It only needs to run once. #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'" - exec: echo "End of custom commands" Thank you all for the support :heart:

C’est bon, j’ai trouvé ! Le Nginx guest écoutait sur la socket, j’ai mis mon host sur la socket aussi. Merciiii

Using a non standard port is not supported. You need to have ports 443 and 80 open. If you’ve rebuilt a bunch of times you’ve got rate limits with let’s encrypt and will need to wait a week or add a second hostname as described in Setting up Let’s Encrypt with Multiple Domains.

Do you mean non-standart port is not supported on host or guest? I was following this tutorial: [image] Run other websites on the same machine as Discourse Self-Hosting 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 tex… Where it says: 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 .

You didn’t mention the reverse proxy. The problem is likely there, not discourse. But, I think you’ll need to remove the ssl and let’s encrypt templates and handle that in the reverse proxy.

Thank you, I now have a 502 Bad Gateway when trying to connect. It tried to connect to 127.0.0.1:8150 locally, but got nothing Here my new discours app.yml: templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" - "templates/web.socketed.template.yml" ## Uncomment these two lines if you wish to add Lets Encrypt (https) #- "templates/web.ssl.template.yml" # - "templates/web.letsencrypt.ssl.template.yml" expose: - "8150:80" # http params: db_default_text_search_config: "pg_catalog.english" db_shared_buffers: "1024MB" env: LC_ALL: fr_FR.UTF-8 LANG: fr_FR.UTF-8 LANGUAGE: fr_FR.UTF-8 EMBER_CLI_PROD_ASSETS: 1 UNICORN_WORKERS: 4 DISCOURSE_HOSTNAME: dis.ob******ie.fr DOCKER_USE_HOSTNAME: true DISCOURSE_DEVELOPER_EMAILS: 'admin@ob******ie.fr' DISCOURSE_SMTP_ADDRESS: mail.ob******ie.fr DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: discourse@ob******ie.fr DISCOURSE_SMTP_PASSWORD: "Safe Password" DISCOURSE_SMTP_DOMAIN: ob******ie.fr DISCOURSE_NOTIFICATION_EMAIL: noreply@ob******ie.fr LETSENCRYPT_ACCOUNT_EMAIL: me@example.com 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" cd: $home/plugins

Infinite 301 redirect with reverse proxy setup

Product Support Self-hosting

powi March 18, 2022, 12:22pm 6

Okay, I found it! The Nginx guest was listening on the socket, so I put my host on the socket too. Thankssssss

Topic		Replies	Views
Can't get Discourse to work on different ports Self-hosting	2	1685	March 9, 2021
Run other websites on the same machine as Discourse Self-Hosting how-to , advanced-setup	66	141111	June 30, 2026
Installing Discourse Behind Reverse Proxy using recommended (supported) installation Self-hosting	7	4381	May 6, 2026
I want to install using a reverse proxy for Apache Self-hosting	13	4957	August 8, 2021
Trouble configuring discourse with reverse proxy Self-hosting	3	1767	September 16, 2022

Infinite 301 redirect with reverse proxy setup

Related topics