I need to implement the server so that it listens to port 80 but gives links in https. How can I solve this problem? my configuration now works like this and all the links are in http: expose: # - “443:443” # https - “80:80” # https I try rename in 443 but fail.

You should be able to achieve that by enabling force_https site setting of Discourse.

LetsEncrypt is quite strict and so I do not think they will provide SSL certs for any port other than 443, for security reasons.

Maybe turn on the force https site setting?

Could you explain why you need to do this?

There is an internal server on which Dicsoure stands and is open for listening on port 80, when a visitor asks for a site, it always opens in https (redirects), but all the links are in http. I do not control this infrastructure, but besides port 80 I have no way out

I’m afraid in my case this will not work because I do not work with https actually

I can turn it off, but it seems to me that this will not solve the problem, since enabling HTTPS on port 80 is impossible because of the SSL

Discourse doesn’t support running on non-standard ports. That includes running https on port 80.

[image] anton21m: I need to implement the server so that it listens to port 80 but gives links in https. How can I solve this problem? [image] anton21m: There is an internal server on which Dicsoure stands and is open for listening on port 80, when a visitor asks for a site, it always opens in https (redirects) Do you mean that you have a reverse proxy setup elsewhere that is handling SSL for all your sites, including Discourse?

Did you try it? Then what are you trying to do? [image] anton21m: I need to implement the server so that it listens to port 80 but gives links in https. How can I solve this problem? Doesn’t that mean that you want links on pages that are served to be https and that you are handling https some other way?

[image] anton21m: I can turn it off, but it seems to me that this will not solve the problem, since enabling HTTPS on port 80 is impossible because of the SSL Sorry, I’m not following (fully understanding) your posts. You said, I need to implement the server so that it listens to port 80 but gives links in https. How can I solve this problem? If I understand you directly, you want all port 80 HTTP traffic to redirect to port 443 HTTPS and you do not want to send HTTPS traffic on port 80, but only redirect port 80 to port 443. If so, this is how most every web server is set up; and for example, if you use LetsEncrypt to set up your port 443 traffic using Apache2 or ngnix, LetsEncrypt will ask you if you want to set up this redirect and will do it for you. As @Falco asked, what is your exact configuration? Are you running a web server like nginx or Apache2 in front of Discourse as a reverse proxy? If so, when you set up LetsEncrypt on nginx or Apache2, the LetsEncrypt setup software will set up the “redirect all HTTP to HTTPS” for you (if you select “yes” when the configuration dialog asks).

Generate https links in port 80

Product Support Self-hosting

anton21m (Anton21m) June 3, 2020, 8:02am 13

Yes, they understood me correctly

I can no longer open any other ports, and there is a reverse proxy that makes the site https but not links in the inside Discourse

Topic		Replies	Views
Running on different port than 443: Disable redirect to nonport URL Self-hosting unsupported-install	7	1190	July 18, 2023
Http logo urls after enabling LetsEncrypt Self-hosting	12	1890	April 16, 2020
Uploads paths have 80 port but protocol is https Product Support	1	230	October 27, 2025
Hyperlink with port number not working Product Support	7	772	April 3, 2022
SSL discourse site is not working Self-hosting	1	932	September 26, 2020

Generate https links in port 80

Related topics