Convoluted cloudflare tunnel instructions (No insult intended just curious). #1091

New Issue

MrUnknownDE · 2026-04-06T01:34:21+02:00

MrUnknownDE commented

2026-04-06 01:34:21 +02:00

Originally created by @blackstormlab on 6/19/2024

Discussed in https://github.com/dani-garcia/vaultwarden/discussions/4620

^{Originally posted by StinkyTACO June 5, 2024}
is there any reason to follow the convoluted setup for a cloudflare tunnel with making the .yml and .json files and base64 decoding it instead of just using an environment variable with the tunnel token instead ?

somethig like this instead:

cloudflare-tunnel:
image: cloudflare/cloudflared:latest
restart: always
environment:
- TUNNEL_TOKEN=tokenhere
command: tunnel --no-autoupdate run

*Originally created by @blackstormlab on 6/19/2024* ### Discussed in https://github.com/dani-garcia/vaultwarden/discussions/4620 <div type='discussions-op-text'> <sup>Originally posted by **StinkyTACO** June 5, 2024</sup> is there any reason to follow the convoluted setup for a cloudflare tunnel with making the .yml and .json files and base64 decoding it instead of just using an environment variable with the tunnel token instead ? somethig like this instead: cloudflare-tunnel: image: cloudflare/cloudflared:latest restart: always environment: - TUNNEL_TOKEN=tokenhere command: tunnel --no-autoupdate run</div>

MrUnknownDE closed this issue

2026-04-06 01:34:21 +02:00

Sign in to join this conversation.

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/vaultwarden#1091