לא מצליח לגרום ל-Discourse לעבוד על פורטים שונים

סיכום מבוסס בינה מלאכותית

The user wants to run Discourse on different ports (10080 and 10443) alongside a WordPress server using an NGINX reverse proxy. They’ve configured Discourse with a custom Docker setup, specifying the ports in the expose section of the configuration file. The forum is running and listening on the correct ports, but when accessing via curl, they receive a 301 Moved permanently response. firewire10000 notes the issue, and schleifer suggests this is likely due to HTTP redirecting to HTTPS. pfaffman recommends checking the Discourse documentation on running other websites on the same machine.

I want to run my Discourse forum alongside my WordPress server but of course these both run on ports 80 and 443 natively. To get around this I’m planning on using a NGINX reverse proxy to translate front facing sub-domains to my applications running on different ports in the back-end. Below are the steps I have taken to install Discourse:

mkdir /var/discourse
git clone https://github.com/discourse/discourse_docker.git /var/discourse
cd /var/discourse

# Make configuration file
cat <<-"EOF" > /var/discourse/containers/discourse
## this is the all-in-one, standalone Discourse Docker container template
##
## After making changes to this file, you MUST rebuild
## /var/discourse/launcher rebuild app
##
## BE *VERY* CAREFUL WHEN EDITING!
## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT!
## visit http://www.yamllint.com/ to validate this file as needed

templates:
- "templates/postgres.template.yml"
- "templates/redis.template.yml"
- "templates/web.template.yml"
- "templates/web.ratelimited.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:
- "10080:80"   # http
- "10443:443" # https

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: "256MB"

## 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: en_GB.UTF-8
LANG: en_GB.UTF-8
LANGUAGE: en_GB.UTF-8
# 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: 3

## TODO: The domain name this Discourse instance will respond to
## Required. Discourse will not work with a bare IP number.
DISCOURSE_HOSTNAME: 'forum.example.com'

## 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: 'webmaster@example.com'

## 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: smtp-relay.example.com
DISCOURSE_SMTP_PORT: 587
DISCOURSE_SMTP_USER_NAME: info@example.com
DISCOURSE_SMTP_PASSWORD: password
DISCOURSE_SMTP_ENABLE_START_TLS: true           # (optional, default true)
#DISCOURSE_SMTP_DOMAIN: discourse.example.com    # (required by some providers)
DISCOURSE_NOTIFICATION_EMAIL: no-reply@example.com    # (address to send notifications from)

## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate
LETSENCRYPT_ACCOUNT_EMAIL: webmaster@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"
EOF

# Setup discourse with configuration file
./launcher bootstrap discourse

I can confirm Discourse is listening on the correct ports:

root@ubuntu-server:~# netstat -tlnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:10080           0.0.0.0:*               LISTEN      185948/docker-proxy
tcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      150667/docker-proxy
tcp        0      0 0.0.0.0:9000            0.0.0.0:*               LISTEN      150655/docker-proxy
tcp        0      0 0.0.0.0:10443           0.0.0.0:*               LISTEN      185937/docker-proxy
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      169991/nginx: maste
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      519/systemd-resolve
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1465/sshd: /usr/sbi
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      169991/nginx: maste
tcp6       0      0 :::22                   :::*                    LISTEN      1465/sshd: /usr/sbi

If I curl the URL and port number I get 301 Moved permanently:

root@ubuntu-server:~# curl forum.example.com:10080
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.18.0</center>
</body>
</html>

That’s probably the HTTP port redirecting to the HTTPS port. (Using the -I flag to curl will show you the redirection target.)

Running curl forum.example.com:10443 should load the site as you expect.

Did you look at Running other websites on the same machine as Discourse?