What adjustments are needed when discourse uses a non-443 port?

Support
,
1

Some of the issues I found include email failure, and users are also redirected to an unreachable interface after registration.

Additionally, the default post image wall is also disabled, and none of the uploaded images can be loaded.

Even after changing it to port 3443, I found that the Discourse logo cannot be loaded.

It seems that many problems have occurred

Is there a way to fix it with one click? Thank youSome of the issues I found include email failure, and users are also redirected to an unreachable interface after registration.

Additionally, the default post image wall is also disabled, and none of the uploaded images can be loaded.

Even after changing it to port 3443, I found that the Discourse logo cannot be loaded.

It seems that many problems have occurred

Is there a way to fix it with one click? Thanks

2

I haven’t tried adding these in env yet

DISCOURSE_PORT: 3443
DISCOURSE_FORCE_HTTPS: true

Don’t know if it will be useful after adding

After changing the port, many images fail to load properly, for example https://mydomain/uploads/default/optimized/1X/_129430568242d1b7f853bb13ebea28b3f6af4e7_2_32x32.png fails to load
But when I manually change it to https://mydomain:3443/uploads/default/optimized/1X/_129430568242d1b7f853bb13ebea28b3f6af4e7_2_32x32.png it can load
But there are too many places where 3443 needs to be added. Is there a quick way to modify it? 443 is not availableI haven’t tried adding these in env yet

3

Can I use the following operation when I have disabled nginx inside the container?

DISCOURSE_EXTERNAL_BASE_URL: “https://domain:3443”

4

Moreover, I found that after users log in, they are automatically redirected to https://domain/latest, and the default port 3443 is not added, causing it to fail to load. At this point, you must manually add https://domain:3443/latest.