Instructions for Obscure CloudFlare Tunnel Configuration

[bgordley]

Feature description

Hello! I have been reading through the various reverse proxy and CloudFlare tunnel issues here and across the internet and was not able to find anything regarding how to resolve the "missing login prompt" websocket issue specifically for CloudFlare tunnel setups.

I did however manage to resolve the issue and wanted to share here at the very least to help someone else searching for a solution.

Essentially a CloudFlare page rule is required that accomplishes the following for your domain/sub-domain.

• Disable all auto-minify tasks. (required for JS)
• Security level doesn't seem to affect the outcome so I set this to "HIgh".
• Cache Level needs to be set to "bypass". (required)
• Add the "Disable Performance" rule (required).

This worked for me as soon as I applied the ruleset. Here is an image as well.

Happy to make a PR with a short mention of this if that's preferred.

Want to say thank you for this fantastic docker image and all the support provided. I read through a lot of issues, felddy is AWESOME!

Motivation

• Based on all information I have gathered and my own experience, CloudFlare tunnels do support websockets just fine, it's just difficult to make the logical connection right away between page rules and Foundry.
• Easy to sink several hours, even days into this issue when it's such a simple configuration change in CloudFlare.

Example

• It would be amazing if this could be included in the readme but I understand if that's not ideal.

Pitch

• May prevent future bugs from being filed if there were at least a mention of page rules for CloudFlare tunnels.

Code of Conduct

• I agree to follow this project's Code of Conduct

[ghost]

There is a docker compose setup for cloudflared which utilizes this project here:

https://adventurermonthly.com/docs/self-host/cloudflare-docker-compose

maybe it will be of assistance?