starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Cloudflared LXC, service 'tunnel run' not starting up upon restart/reboot #2442

New Issue
Closed
opened 2026-02-05 04:52:45 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 04:52:45 +03:00
Owner
Copy Link

Originally created by @andilge on GitHub (Feb 3, 2026).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

No (this issue will likely be closed automatically)

📜 What is the name of the script you are using?

id=cloudflared

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/cloudflared.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

📈 Which Proxmox version are you on?

pve 9.1.4

📝 Provide a clear and concise description of the issue.

installation with 'bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/cloudflared.sh)"'.

I get it up and running with the command 'tunnel run [my_tunel_ID]'., all fine up to there. When I restart the container or reboot my pve node, the service won't kick in and start the tunnel.

The service appears being installed. Entering command 'cloudflared service install' informs this:
root@cloudflared:~# cloudflared service install
2026-02-03T13:01:28Z INF Using Systemd
2026-02-03T13:01:28Z ERR error generating service template error="cloudflared service is already installed at /etc/systemd/system/cloudflared.service; if you are running a cloudflared tunnel, you can point it to multiple origins, avoiding the need to run more than one cloudflared service in the same machine; otherwise if you are really sure, you can do cloudflared service uninstall to clean up the existing service and then try again this command"
cloudflared service is already installed at /etc/systemd/system/cloudflared.service; if you are running a cloudflared tunnel, you can point it to multiple origins, avoiding the need to run more than one cloudflared service in the same machine; otherwise if you are really sure, you can do cloudflared service uninstall to clean up the existing service and then try again this command

Here I do a 'systemctl status cloudflared' some sec after restarting the container. It shows all enabled and active:
● cloudflared.service - cloudflared DNS-over-HTTPS (DoH) proxy
Loaded: loaded (/etc/systemd/system/cloudflared.service; enabled; preset: enabled)
Active: active (running) since Tue 2026-02-03 13:57:03 CET; 48s ago
Invocation: c1e0d94ce8af4f18a48b7c1f23776486
Main PID: 85 (cloudflared)
Tasks: 5 (limit: 76797)
Memory: 50.3M (peak: 50.3M)
CPU: 147ms
CGroup: /system.slice/cloudflared.service
└─85 /usr/local/bin/cloudflared --config /usr/local/etc/cloudflared/config.yml

Feb 03 13:57:03 cloudflared systemd[1]: Started cloudflared.service - cloudflared DNS-over-HTTPS (DoH) proxy.
Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Version 2026.1.2 (Checksum e157c54e929cc289cbd53860453168c2fe3439eb55e2e965a56579252585d9>
Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF GOOS: linux, GOVersion: go1.24.11, GoArch: amd64
Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Settings: map[config:/usr/local/etc/cloudflared/config.yml proxy-dns:true proxy-dns-addre>
Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Adding DNS upstream url=https://1.1.1.1/dns-query
Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Adding DNS upstream url=https://1.0.0.1/dns-query
Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Starting DNS over HTTPS proxy server address=dns://0.0.0.0:53
Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF cloudflared will not automatically update if installed by a package manager.

The cannonical tunnel is not working though, my service remain unavailable on my sub domains. I can work around this by entering the command 'cloudflared tunnel run [my_tunnel_id]', but that's cumbersome. My goal here is restatring the container or rebooting the node will also restart the service and make my services available on my sub domains, eg. no manual interaction is needed.

Am I doing something wrong, only me having this problem?

🔄 Steps to reproduce the issue.

  1. install cloudflared with the helper scrip
  2. get your sub domains up and running with the CNAMEs
  3. restart LXC cloudflred or reboot node
  4. check, if your sub domains are still availble in the wide net.

❌ Paste the full error output (if available).

not avl

🖼️ Additional context (optional).

setup made following the tutorial on
https://bobcares.com/blog/cloudflare-tunnel-proxmox/

Originally created by @andilge on GitHub (Feb 3, 2026). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? No (this issue will likely be closed automatically) ### 📜 What is the name of the script you are using? id=cloudflared ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/cloudflared.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 📈 Which Proxmox version are you on? pve 9.1.4 ### 📝 Provide a clear and concise description of the issue. installation with 'bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/cloudflared.sh)"'. I get it up and running with the command 'tunnel run [my_tunel_ID]'., all fine up to there. When I restart the container or reboot my pve node, the service won't kick in and start the tunnel. The service appears being installed. Entering command 'cloudflared service install' informs this: root@cloudflared:~# cloudflared service install 2026-02-03T13:01:28Z INF Using Systemd 2026-02-03T13:01:28Z ERR error generating service template error="cloudflared service is already installed at /etc/systemd/system/cloudflared.service; if you are running a cloudflared tunnel, you can point it to multiple origins, avoiding the need to run more than one cloudflared service in the same machine; otherwise if you are really sure, you can do `cloudflared service uninstall` to clean up the existing service and then try again this command" cloudflared service is already installed at /etc/systemd/system/cloudflared.service; if you are running a cloudflared tunnel, you can point it to multiple origins, avoiding the need to run more than one cloudflared service in the same machine; otherwise if you are really sure, you can do `cloudflared service uninstall` to clean up the existing service and then try again this command Here I do a 'systemctl status cloudflared' some sec after restarting the container. It shows all enabled and active: ● cloudflared.service - cloudflared DNS-over-HTTPS (DoH) proxy Loaded: loaded (/etc/systemd/system/cloudflared.service; enabled; preset: enabled) Active: active (running) since Tue 2026-02-03 13:57:03 CET; 48s ago Invocation: c1e0d94ce8af4f18a48b7c1f23776486 Main PID: 85 (cloudflared) Tasks: 5 (limit: 76797) Memory: 50.3M (peak: 50.3M) CPU: 147ms CGroup: /system.slice/cloudflared.service └─85 /usr/local/bin/cloudflared --config /usr/local/etc/cloudflared/config.yml Feb 03 13:57:03 cloudflared systemd[1]: Started cloudflared.service - cloudflared DNS-over-HTTPS (DoH) proxy. Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Version 2026.1.2 (Checksum e157c54e929cc289cbd53860453168c2fe3439eb55e2e965a56579252585d9> Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF GOOS: linux, GOVersion: go1.24.11, GoArch: amd64 Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Settings: map[config:/usr/local/etc/cloudflared/config.yml proxy-dns:true proxy-dns-addre> Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Adding DNS upstream url=https://1.1.1.1/dns-query Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Adding DNS upstream url=https://1.0.0.1/dns-query Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF Starting DNS over HTTPS proxy server address=dns://0.0.0.0:53 Feb 03 13:57:04 cloudflared cloudflared[85]: 2026-02-03T12:57:04Z INF cloudflared will not automatically update if installed by a package manager. The cannonical tunnel is not working though, my service remain unavailable on my sub domains. I can work around this by entering the command 'cloudflared tunnel run [my_tunnel_id]', but that's cumbersome. My goal here is restatring the container or rebooting the node will also restart the service and make my services available on my sub domains, eg. no manual interaction is needed. Am I doing something wrong, only me having this problem? ### 🔄 Steps to reproduce the issue. 1. install cloudflared with the helper scrip 2. get your sub domains up and running with the CNAMEs 3. restart LXC cloudflred or reboot node 4. check, if your sub domains are still availble in the wide net. ### ❌ Paste the full error output (if available). not avl ### 🖼️ Additional context (optional). setup made following the tutorial on https://bobcares.com/blog/cloudflare-tunnel-proxmox/
OVERLORD added the bug label 2026-02-05 04:52:45 +03:00
OVERLORD commented 2026-02-05 04:52:57 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 3, 2026):

This is expected behavior, not a bug.

The helper script only installs the cloudflared package. The default systemd service provided by Cloudflare does not start a tunnel, it just starts cloudflared in its default mode.
A Cloudflare Tunnel only runs if it is explicitly configured (via config.yml) or started with cloudflared tunnel run <TUNNEL_id>.

To have the tunnel start automatically after reboot, you need to configure a tunnel and run it via a dedicated systemd service or a proper config.yml. The installer intentionally does not create or manage tunnels, as this requires user-specific Cloudflare credentials and domain setup.

@MickLesk commented on GitHub (Feb 3, 2026): This is expected behavior, not a bug. The helper script only installs the cloudflared package. The default systemd service provided by Cloudflare does not start a tunnel, it just starts cloudflared in its default mode. A Cloudflare Tunnel only runs if it is explicitly configured (via config.yml) or started with cloudflared tunnel run <TUNNEL_id>. To have the tunnel start automatically after reboot, you need to configure a tunnel and run it via a dedicated systemd service or a proper config.yml. The installer intentionally does not create or manage tunnels, as this requires user-specific Cloudflare credentials and domain setup.
OVERLORD commented 2026-02-05 04:53:01 +03:00
Author
Owner
Copy Link

@andilge commented on GitHub (Feb 3, 2026):

1000 thanks for this swift reply.
As you see above, I try to install the systemd service in the LXC and it says 'already installed'. so it appeared to be a part of the helper script.

I'll track this down and go for the proper config.yml to get it up and running as needed, tnx for the hint in this direction. Closing this tkt here.

@andilge commented on GitHub (Feb 3, 2026): 1000 thanks for this swift reply. As you see above, I try to install the systemd service in the LXC and it says 'already installed'. so it appeared to be a part of the helper script. I'll track this down and go for the proper config.yml to get it up and running as needed, tnx for the hint in this direction. Closing this tkt here.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2442
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?