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

**URL:** https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170
**Category:** Support
**Tags:** email, bug
**Created:** [November 20, 2025, 9:10am UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170 "2025-11-20T09:10:58Z")
**Posts on this page:** 12
**Page:** 1

<div class="post-metadata">

### Author: ![tom\_eric](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tom_eric/32/527845_2.png) [@tom\_eric](https://meta.discourse.org/u/tom_eric)
#### Post date: [November 20, 2025, 9:10am UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/1 "2025-11-20T09:10:58Z")

</div>

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

---

<div class="post-metadata">

### Author: ![tom\_eric](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tom_eric/32/527845_2.png) [@tom\_eric](https://meta.discourse.org/u/tom_eric)
#### Post date: [November 20, 2025, 9:28am UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/2 "2025-11-20T09:28:52Z")

</div>

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](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](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

---

<div class="post-metadata">

### Author: ![tom\_eric](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tom_eric/32/527845_2.png) [@tom\_eric](https://meta.discourse.org/u/tom_eric)
#### Post date: [November 20, 2025, 9:40am UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/3 "2025-11-20T09:40:36Z")

</div>

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

DISCOURSE\_EXTERNAL\_BASE\_URL: “[https://domain:3443](https://domain:3443)”

---

<div class="post-metadata">

### Author: ![tom\_eric](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tom_eric/32/527845_2.png) [@tom\_eric](https://meta.discourse.org/u/tom_eric)
#### Post date: [November 20, 2025, 9:58am UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/4 "2025-11-20T09:58:13Z")

</div>

Moreover, I found that after users log in, they are automatically redirected to [https://domain/latest](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](https://domain:3443/latest).

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 20, 2025, 3:02pm UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/5 "2025-11-20T15:02:52Z")

</div>

Discourse won’t work on port 3443. You have to use 443.

Is this a [standard install](https://meta.discourse.org/t/142537?silent=true)?

---

<div class="post-metadata">

### Author: ![tom\_eric](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tom_eric/32/527845_2.png) [@tom\_eric](https://meta.discourse.org/u/tom_eric)
#### Post date: [November 20, 2025, 3:12pm UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/6 "2025-11-20T15:12:32Z")

</div>

🫣

Thank you for your reply

Yes, I know there are many components hardcoded to port 443. My port 443 is not usable, so I had to switch to port 3443. Currently, many functions are not working. I thought someone had studied this issue

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 20, 2025, 3:37pm UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/7 "2025-11-20T15:37:51Z")

</div>

Those who have studied the issue know that it won’t work on a non-standard port. I promise.

It’s pretty well documented, or so I thought.

---

<div class="post-metadata">

### Author: ![tom\_eric](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tom_eric/32/527845_2.png) [@tom\_eric](https://meta.discourse.org/u/tom_eric)
#### Post date: [November 20, 2025, 3:46pm UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/8 "2025-11-20T15:46:28Z")

</div>

It seems I have to give up on this huge project

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 20, 2025, 4:07pm UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/9 "2025-11-20T16:07:01Z")

</div>

If it’s not worth a $12/month VM or configuring a reverse proxy, then I think you’re right.

---

<div class="post-metadata">

### Author: ![tom\_eric](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tom_eric/32/527845_2.png) [@tom\_eric](https://meta.discourse.org/u/tom_eric)
#### Post date: [November 20, 2025, 4:08pm UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/10 "2025-11-20T16:08:40Z")

</div>

Not about cost. Maybe I want to push it a bit further, like installing multiple Discourse instances on one big server

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 20, 2025, 6:46pm UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/11 "2025-11-20T18:46:33Z")

</div>

If you want multiple sites then you either need multisite or a reverse proxy. I usually use traefik, but [nginxproxy/nginx-proxy - Docker Image](https://hub.docker.com/r/nginxproxy/nginx-proxy) is a little easier. Just add some docker labels and it works.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [December 20, 2025, 6:46pm UTC](https://meta.discourse.org/t/what-adjustments-are-needed-when-discourse-uses-a-non-443-port/389170/12 "2025-12-20T18:46:34Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
