Hello everyone– Summary New user invite links give a ERR_SSL_PROTOCOL_ERROR even though the rest of the site works fine. Context I’ve been running a completely stock Discourse Docker image for about 5 years with no troubles. About a year ago I moved to https with Let’s Encrypt using this guide . S…

Try to clear it please: #everything above and then SiteSetting.port = '' exit exit ./launcher restart app

More info! The invites get sent out with a link like forum.mysite.com:80/invites/... but when one removes the :80 the links don’t have the auth error. So why are we getting :80 in the links? Thanks!

Sounds like you have a bad configuration? What is in your app.yml as far as domain name? Discourse does not support being run on alternate ports.

Well, DISCOURSE_HOSTNAME is exactly the name of the site as it should be. The only place that 80 appears is in this block: ## which TCP/IP ports should this container expose? expose: - "80:80" # fwd host port 80 to container port 80 (http) - "2222:22" # fwd host port 2222 to container port…

I found that https://www.phylobabble.org/latest.rss has the :80s in the links, and then looking at the relevant Discourse source code I see that it’s being directly put in the RSS via <link><%= @link %></link> so Discourse definitely thinks that my site ends with :80 as suggested, and it’s not…

I think you may have the wrong line @ematsen . I think the broken link is on a line a bit lower down (#15): app/views/posts/latest.rss.erb acd1693da <% site_email = SiteSetting.find_by_name('contact_email').try(:value) %> <title><%= @title %></…

You should not be explicitly setting a port anywhere, that is for sure.

I can’t find anywhere that we might be explicitly setting the port anywhere. And to clarify from Erick’s post above, DISCOURSE_HOSTNAME: www.phylobabble.org, which seems as it should be. I thought for a while that maybe one of the templates getting loaded might be causing the issue, but these shoul…

You are following our official install guide to the letter, yes? This isn’t a problem we see often (or at all, honestly). Did you do a developer type install where you explicitly overrode the port? That’s only done on developer installs to my knowledge.

I did follow the install guide to the letter, and the site’s been running beautifully for many years now (thanks!). I did the most vanilla type install I could do-- definitely not a developer install. As a crutch, can you think of a way to forward the problematic phylobabble.org:80 requests to jus…

I nuovi link di invito per gli utenti restituiscono solo ERR_SSL_PROTOCOL_ERROR

Supporto

Falco (Falco) 7 Dicembre 2018, 1:35am 11

Can you share the output of:

cd /var/discourse
./launcher enter app
rails c
SiteSetting.port

Argomento		Risposte	Visualizzazioni
Uploads paths have 80 port but protocol is https Support	1	174	Ottobre 27, 2025
ERR_SSL_PROTOCOL_ERROR with Letsencrypt Self-hosting letsencrypt	3	6629	Febbraio 26, 2018
Installed without error but site wont come up Self-hosting	12	1951	Febbraio 13, 2017
No connection accepted on http / https after fresh installation on Ubuntu 22.04 LTS Self-hosting	5	2490	Dicembre 16, 2022
Error SSL after installation Self-hosting unsupported-install	13	1496	Agosto 30, 2020

I nuovi link di invito per gli utenti restituiscono solo ERR_SSL_PROTOCOL_ERROR

Argomenti correlati