# Uploads paths have 80 port but protocol is https
**URL:** https://meta.discourse.org/t/uploads-paths-have-80-port-but-protocol-is-https/386793
**Category:** Support
**Created:** [October 27, 2025, 8:00am UTC](https://meta.discourse.org/t/uploads-paths-have-80-port-but-protocol-is-https/386793 "2025-10-27T08:00:54Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@adopilot](https://meta.discourse.org/u/adopilot)
#### Post date: [October 27, 2025, 8:00am UTC](https://meta.discourse.org/t/uploads-paths-have-80-port-but-protocol-is-https/386793/1 "2025-10-27T08:00:54Z")
Recently I restored my long running discource instance to new one.
My discource version are 3.6.0.beta2-latest.
Now I have problem that uploads do not works .
When I look into browser console i see lot of net::ERR\_SSL\_PROTOCOL\_ERROR errors.
When I take look at network tab i see that chrome trying to fetch url
`https://forum.robot.ba:80/uploads/default/optimized/4X/7/2/b/72be8d09005292d2f7ac37158b6d728a063f79ed_2_32x32.png`
If I manually remove port 80 or change protocol from https to http and I can open link manually in new browser window.
Any idea why my discource instance adding :80 to upload paths ?
I did search site settings for force https but seems that that is not tuned on or that settings does not exist anymore.
Is is something wrong inside my app.yml file i have following templates:
(I want to use letsencrypt since i do not have my SSL cert)
```plaintext
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”
```
---
### Author:  [@jahan\_gagan](https://meta.discourse.org/u/jahan_gagan)
#### Post date: [October 27, 2025, 9:15am UTC](https://meta.discourse.org/t/uploads-paths-have-80-port-but-protocol-is-https/386793/2 "2025-10-27T09:15:36Z")
You can check out this guide for setting up HTTPS with Let’s Encrypt:
> [@Set up HTTPS support with Let's Encrypt](https://meta.discourse.org/t/set-up-https-support-with-lets-encrypt/40709):
>
> bookmark This is a guide for enabling HTTPS on an existing Discourse installation using Let’s Encrypt. It assumes prior installation without HTTPS enabled. person_raising_hand Required user level: System Administrator exclamation This guide is only for existing installs where HTTPS is not enabled. Following the [official setup guide](https://github.com/discourse/discourse/blob/main/docs/INSTALL-cloud.md) automatically enables HTTPS by default. So you’d like to add https to your Discourse absolutely free, courtesy of our friends at [Let’s Encrypt?](https://letsencrypt.org/)bell I…
### Possible Cause: Hidden “Port” Setting
Sometimes a hidden `port` site setting remains in the database after migration or restore.
This can cause Discourse to append an incorrect port (like `:80`) to HTTPS URLs.
To check and fix it:
1. Enter your container:
```plaintext
./launcher enter app
```
1. Open the Rails console:
```plaintext
rails c
```
1. Check the current value:
```plaintext
SiteSetting.port
```
1. If it returns `80`, clear it:
```plaintext
SiteSetting.port = ""
```
1. Then rebake all posts and assets to update links:
```plaintext
Jobs.enqueue(:rebake_all_posts)
```
---
### Author:  [@system](https://meta.discourse.org/u/system)
#### Post date: [November 26, 2025, 9:16am UTC](https://meta.discourse.org/t/uploads-paths-have-80-port-but-protocol-is-https/386793/3 "2025-11-26T09:16:05Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.