Feature Request: [Allow use of Cloudflare Tunnels & Access on OpenSign server]

[usshauler]

Feature Title

Add ability for OpenSign to work using Cloudflare Tunnels and Cloudflare Access

Feature Description

There are some users who utilize Cloudflare Tunnels as a means to proxy their traffic versus utilizing a separate reverse proxy as NPM or Traeffik. The proxy functionality is currently working but not all data is passed through when Cloudflare Access is enabled on the OpenSign domain. Specifically, when creating a new user upon building OpenSign, the server reports back errors and cannot create the account. There may be other hidden issues while using this means of security when sending, receiving PDF sign requests or other embedded features. I believe this is due to the fact that not all data can pass through to Cloudflare but not entirely sure how this functions. Thank you for your time.

What type of feature are you requesting?

Security / Compliance

Importance

Critical

Additional Context

Code of Conduct

• I agree to follow this project's Code of Conduct
• I have searched the existing issues & discussions to make sure that this is not a duplicate.

[Zathiel]

Hey @usshauler

I will discuss with the team concerning this request

Will keep you posted here if we plann to do it.

Regards

[nxglabs]

The issue in the screenshot seems more like a setup issue. It might not have anything to do with cloudflare.

[allandalton]

I'm not sure how you configured it on your side, but on our end we got it working using the official .env file. We set the BASE_URL to the public domain, removed Caddy, and routed everything through NGINX—including the server API.

We initially had issues with PDFs, but after adjusting the headers, that was resolved. After that, we applied the Cloudflare proxy and blocked all bot traffic.

Everything has been running fine since then. If you'd like, we can help you configure it properly, or feel free to close the ticket if it's no longer needed.

[usshauler]

I would appreciate it if you could help in configuring the entirety of the compose and env as I’ve tried many different ways and still cannot get it to work on first try. I can join Discord and reach out.

…

On Thu, Apr 24, 2025 at 6:22 PM Allan Dalton ***@***.***> wrote: *allandalton* left a comment (OpenSignLabs/OpenSign#692) <#692 (comment)> I'm not sure how you configured it on your side, but on our end we got it working using the official .env file. We set the BASE_URL to the public domain, removed Caddy, and routed everything through NGINX—including the server API. We initially had issues with PDFs, but after adjusting the headers, that was resolved. After that, we applied the Cloudflare proxy and blocked all bot traffic. Everything has been running fine since then. If you'd like, we can help you configure it properly, or feel free to close the ticket if it's no longer needed. — Reply to this email directly, view it on GitHub <#692 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALZ6SKN2AFUAVAUS7L5AHDT23FW2LAVCNFSM6AAAAAB32ISMPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMRZGA2TSMRWGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>