I’m using following setup, which ran for about 2 year without issues. Virtual machine, dedicated for default docker/discourse installation. My firewall forwards port 17601 towards 80 for external use. Today, I’ve update to 2.4.0.beta10. Now, it still works from internall ( http://hostname.localdo…

Indeed. When I disable this, it seems to work. :+1: The same is for local use. I noticed that it was working with the hostname ( http://hostname ), but not with the IP ( http://localip ). After disabling CSP, it works with IP as well. Guess I’ll need to read a bit more about this Content-Security-Poli…

Port forwarding?

Ondersteuning

itsbhanusharma (Bhanu Sharma) 30 januari 2020 om 18:12 2

Do you see any errors in the browser console? It could be related to CSP.

IP does not redirect to domain, domain shows white page

Topic		Antwoorden	Weergaven
Content Security Policy: The settings of the page have blocked the loading of a resource ("script-src") Self-hosting unsupported-install	27	2120	3 mei 2023
Fresh Discourse install on digitalocean, cannot activate account Self-hosting	15	1527	21 januari 2019
IP does not redirect to domain, domain shows white page Self-hosting unsupported-install	7	1600	31 januari 2020
How to relax Content Security Policy Development	5	2538	11 november 2022
External nginx pagespeed module causes Security Policy violation Self-hosting	13	1866	30 juli 2019

Port forwarding?

Gerelateerde topics