Issue Accessing HedgeDoc via Public URL with Cloudflare Tunnel

Support
1

My version of HedgeDoc is: latest

What I expected to happen:

I expected to access my HedgeDoc instance via the public URL https://hedgedoc.mydomain.site/ without any issues, allowing me to use the application seamlessly with all resources (scripts, stylesheets, and images) loading securely over HTTPS.

What actually happened:

When I attempted to access the URL, I encountered mixed content errors indicating that some resources were being loaded over an insecure HTTP connection. Specifically, images and scripts were blocked due to being requested over http://192.168.1.24:3000, even though the initial page was served over HTTPS.

Additional Information:

Blocked Resources:

  • font-pack.4362583c9249021b5028.css
  • 2.15c517ea2148f55c8206.css
  • 3.ec6e7d6280fcd73e729d.css
  • cover-styles-pack.b648f312ee4d780e4818.css
  • cover.e6dcfddabfc3aa3af727.css
  • config (script)
  • vendors~common.0252483117be96f00e28.js
  • common.0c0667a7b004f0fcfd13.js
  • vendors~cover~cover-pack~index~index-pack~pretty~pretty-pack~slide~slide-pack.89ccd89a09f629d94d5c.js
  • vendors~cover~cover-pack.1a03d088607537a1c006.js
  • cover-pack.ad576c7fbe7f714da842.js
  • banner_vertical_color.svg
  • screenshot.png
2

Hi @MHD_29 and welcome to the HedgeDoc community!

As the Cloudflare tunnel acts like a reverse-proxy, did you follow all configuration hints
in our docs here: https://docs.hedgedoc.org/guides/reverse-proxy/?

Also ensure, that the auto-minification of assets in Cloudflare is disabled, since this breaks HedgeDoc.