Hi, I have set up discourse via Docker, but the error mentioned in the title only appears.

[image] Jay Pfaffman: I don’t know. You clearly do not have a standard install, and haven’t explained how you installed. I dont’ know what is forcing what on port 80 and 443. If you want good help, you should use a standard install. If you want any help, you will need to say more about how you installed. Well, I use the standard installation, which forces port 80 and 443.

[image] Justman10000: I have once set up the images individually and via docker-compose! So you didn’t use docker-compose? Yes, the standard install requires ports 80 and 443 and turns on https and force_https. You shouldn’t have the problem that you describe if you did a standard install. You ran discourse-setup to install?

The thing is, I want to run discourse on other ports and include it in my Apache2 via reverse proy…

Perhaps if you will say how you installed, someone else can help you. Maybe you want Set up Discourse on a server with existing Apache sites.

I have already said! About the standard installation!!!

[image] Justman10000: include it in my Apache2 via reverse proy… Of course you can. You should expose for example - "83:80" on app.yml, or what ever port your reverse proxy uses to send traffic to backend. Or you can use websocket. [image] Justman10000: I have already said! About the standard installation!!! You want to use a reverse proxy that is not a standard install.

[image] Jakke Flemming: Of course you can. On app.yml you should expose for example - "83:80" or what ever port your backen uses. Or you can use websocket. I have, but the site is not accessible

Then your settings are wrong. What is an issue is close to impossible guess. Don’t use CSP, that would be the first move. But are both, Apache2 and Discourse, on same server? Is your conf of Apache2 right? Etc, etc. Again as said — you don’t use standard install.

I cannot use the standard install! Sorry, but what’s so hard to understand about that? I already have Apache2 running, and I don’t see the point of shutting it down just because Discourse doesn’t think it’s flexible enough to use other ports

That is the problem with the whole thing

Content Security Policy: The settings of the page have blocked the loading of a resource ("script-src")

Product Support Self-hosting

Jagster (Jakke Flemming) May 3, 2023, 3:43pm 29

Then you are on wrong forum. But you should check your cinfiguration of postfix, firewall etc.

Topic		Replies	Views
⚠ Port 443 of this computer does not appear to be accessible using hostname: metabolism.logophilia.eu ---- Product Support	8	334	June 6, 2026
Fresh install returning 502 Bad Gateway Self-hosting unsupported-install	27	1364	March 12, 2024
Set up Discourse on a server with existing Apache sites Sysadmins how-to	16	23470	September 18, 2020
I want to install using a reverse proxy for Apache Self-hosting	13	4953	August 8, 2021
Discourse behind reverse proxy and https Self-hosting	18	7771	March 13, 2022

Content Security Policy: The settings of the page have blocked the loading of a resource ("script-src")

Related topics