I’ve change app.yml to expose: - "20632:80" # http #- "443:443" # https - "20633:443" and want to open discourse via https://mydomain.com:20633 , but then it tries to redirect to https://mydomain.com which won’t work. When using expose: - "20632:20632" # http #- "443:443" # https …

We don’t support running on non-standard ports. If the 80/443 ports are already occupied, you will need to use a separate server where they aren’t or run a reverse proxy to from your other services and Discourse.

Sometimes “we don’t support” means “that’s beyond the help you can expect here”, but this time it means “you’re wasting your time even trying”.

The ports aren’t “occupied” in the usual way. Discourse can grab port 80 and 443 on that system, it is already running on a separate server on its own. Im stuck at the step to disable the redirection/removing the port in the URL and everything would work as expected.

You cant prevent that redirect. If you can’t publish on the standard ports, then it won’t work at all. Your choices here are to use a server where :80/443 are available, or to pick an alternative discussion platform.

Can you help me with the nginx reverse proxy configuration? I’ve tried various options without success server { listen 20633 ssl; server_name mydomain.com; ssl_certificate /etc/letsencrypt/live/mensa.myftp.org/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/mensa.myftp.org/pri…

See the guide at Run other websites on the same machine as Discourse .

That tutorial is for running on the same server via unix socket. Is there also configuration for running the reverse proxy on a different system with different port? I think it should be since this case might occur more often. On the other host I already have a certificate. Just to be clear: This s…

Работа на порте, отличном от 443: отключить перенаправление на URL без порта

Поддержка Самостоятельное хостинг

Falco (Falco) 17.Июль.2023 21:36:46 7

Смотрите руководство по адресу Запуск других веб-сайтов на том же компьютере, что и Discourse.

Тема		Ответов	Просм.
Can't get Discourse to work on different ports Self-hosting	2	1558	09.03.2021
Is there a way to specify DISCOURSE_PORT next to DISCOURSE_HOSTNAME? Self-hosting	1	864	23.07.2021
Generate https links in port 80 Self-hosting	21	1263	05.06.2020
Using other ports than 80 and 443 - HowTo? Self-hosting hosting	5	2308	11.02.2022
Hyperlink with port number not working Support	10	699	18.04.2022

Работа на порте, отличном от 443: отключить перенаправление на URL без порта

Связанные темы