CloudFlare Tunnels Connecter not showing up
Im using Cloudflare tunnels to try and connect a dashboard to my domain. Im using a ubuntu server. Im using the pre generated command to install everything. Im getting this error
If i run
and if i run it with sudo everything works
Then if i run
2023-09-05T07:33:02Z INF Using Systemd
2023-09-05T07:33:02Z ERR error generating service template error="cloudflared service is already installed at /etc/systemd/system/cloudflared-update.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-update.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
2023-09-05T07:33:02Z INF Using Systemd
2023-09-05T07:33:02Z ERR error generating service template error="cloudflared service is already installed at /etc/systemd/system/cloudflared-update.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-update.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 uninstall
2023-09-05T07:33:50Z ERR systemctl daemon-reload error error="systemctl [daemon-reload] returned with error code exit status 1 due to: Failed to reload daemon: Interactive authentication required.\n"
systemctl [daemon-reload] returned with error code exit status 1 due to: Failed to reload daemon: Interactive authentication required.
2023-09-05T07:33:50Z ERR systemctl daemon-reload error error="systemctl [daemon-reload] returned with error code exit status 1 due to: Failed to reload daemon: Interactive authentication required.\n"
systemctl [daemon-reload] returned with error code exit status 1 due to: Failed to reload daemon: Interactive authentication required.
2023-09-05T07:34:49Z INF Linux service for cloudflared uninstalled successfully
2023-09-05T07:34:49Z INF Linux service for cloudflared uninstalled successfully
sudo cloudflared service install xxxx i get the error i started with saying its already installed? There is no connecter showing up when it refreshes?
I Think im stuck in a loop26 Replies
cloudflared service is already installed at /etc/systemd/system/cloudflared-update.service;This name (
cloudflared-update.service) isn't the normal name this service has. If you are sure no other cloudflared should be running on the server, could you delete that file and try again?uhh I might have it installed coz i folled a dif doc guide when installing the first time. Can you please tell me the best way to check
sudo systemctl status cloudflared-update ?○ cloudflared-update.service - Update cloudflared
Loaded: loaded (/etc/systemd/system/cloudflared-update.service; static)
Active: inactive (dead)
○ cloudflared-update.service - Update cloudflared
Loaded: loaded (/etc/systemd/system/cloudflared-update.service; static)
Active: inactive (dead)
inactive (dead) so its not in use
I would be curious what it's supposed to be doing though, would you mind doing sudo cat /etc/systemd/system/cloudflared-update.service as well?Description=Update cloudflared
After=network.target
[Service]
ExecStart=/bin/bash -c '/usr/bin/cloudflared update; code=$?; if [ $code -eq 11 ]; then systemctl restart cloudflared; exit 0; fi; exit $code'
Description=Update cloudflared
After=network.target
[Service]
ExecStart=/bin/bash -c '/usr/bin/cloudflared update; code=$?; if [ $code -eq 11 ]; then systemctl restart cloudflared; exit 0; fi; exit $code'
Fascinating
Okay so, you can add that back later if you need it, for now try
sudo rm /etc/systemd/system/cloudflared-update.service and then try installing cloudflared service againkath@funny-kath-server:~/a$ sudo cloudflared service install no
2023-09-05T08:47:19Z INF Using Systemd
2023-09-05T08:47:19Z 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
kath@funny-kath-server:~/a$ sudo cloudflared service install no
2023-09-05T08:47:19Z INF Using Systemd
2023-09-05T08:47:19Z 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
run
sudo cloudflared service uninstall again
last time it was complaining about cloudflared-update.service so now thats gone, the uninstall + reinstall should workRunning the uninstall
2023-09-05T08:49:44Z INF Linux service for cloudflared uninstalled successfully as normal. Running the install script
2023-09-05T08:50:20Z 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
2023-09-05T08:50:20Z 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
🤔 that's very strange
Since uninstall isn't working, try cleaning it manually with
sudo rm /etc/systemd/system/cloudflared.service and rerun the install command?worth rming everything with cloudflared?
Just that for now
2023-09-05T08:56:50Z ERR error generating service template error="cloudflared service is already installed at /etc/systemd/system/cloudflared-update.timer; 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-update.timer; 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
2023-09-05T08:56:50Z ERR error generating service template error="cloudflared service is already installed at /etc/systemd/system/cloudflared-update.timer; 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-update.timer; 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
Delete that file and try again :/
/etc/systemd/system/cloudflared-update.timer this timekath@funny-kath-server:~/a$ sudo rm /etc/systemd/system/cloudflared-update.timer
kath@funny-kath-server:~/a$ curl -L --output cloudflared.deb https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb && sudo dpkg -i cloudflared.deb && sudo cloudflared service install xxx
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
100 16.8M 100 16.8M 0 0 2783k 0 0:00:06 0:00:06 --:--:-- 4768k
(Reading database ... 121320 files and directories currently installed.)
Preparing to unpack cloudflared.deb ...
Unpacking cloudflared (2023.8.2) over (2023.8.2) ...
Setting up cloudflared (2023.8.2) ...
Processing triggers for man-db (2.10.2-1) ...
2023-09-05T09:01:06Z INF Using Systemd
2023-09-05T09:01:06Z 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
kath@funny-kath-server:~/a$ sudo rm /etc/systemd/system/cloudflared-update.timer
kath@funny-kath-server:~/a$ curl -L --output cloudflared.deb https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb && sudo dpkg -i cloudflared.deb && sudo cloudflared service install xxx
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
100 16.8M 100 16.8M 0 0 2783k 0 0:00:06 0:00:06 --:--:-- 4768k
(Reading database ... 121320 files and directories currently installed.)
Preparing to unpack cloudflared.deb ...
Unpacking cloudflared (2023.8.2) over (2023.8.2) ...
Setting up cloudflared (2023.8.2) ...
Processing triggers for man-db (2.10.2-1) ...
2023-09-05T09:01:06Z INF Using Systemd
2023-09-05T09:01:06Z 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
Well thats annoying
regardless of the error does it then work? check
sudo systemctl status cloudflared● funny-kath-server
State: degraded
Jobs: 0 queued
Failed: 1 units
Since: Tue 2023-09-05 05:51:47 UTC; 3h 12min ago
CGroup: /
├─user.slice
│ └─user-1000.slice
│ ├─[email protected] …
│ │ └─init.scope
│ │ ├─1302 /lib/systemd/systemd --user
│ │ └─1303 (sd-pam)
│ └─session-1.scope
│ ├─ 1290 sshd: kath [priv]
│ ├─ 1415 sshd: kath@pts/0
│ ├─ 1416 -bash
│ ├─ 1785 PM2 v5.3.0: God Daemon (/home/kath/.pm2)
│ ├─ 1799 PM2 Agent v2.0.3: (/home/kath/.pm2)
│ ├─18231 sudo systemctl status
│ ├─18232 sudo systemctl status
│ ├─18233 systemctl status
│ └─18234 less
├─init.scope
│ └─1 /sbin/init
└─system.slice
├─irqbalance.service
│ └─820 /usr/sbin/irqbalance --foreground
├─netplan-wpa-wlp1s0.service
│ └─712 /sbin/wpa_supplicant -c /run/netplan/wpa-wlp1s0.conf -iwlp1s0 -Dnl80211,wext
├─containerd.service …
│ └─902 /usr/bin/containerd
├─packagekit.service
│ └─2413 /usr/libexec/packagekitd
├─systemd-networkd.service
│ └─802 /lib/systemd/systemd-networkd
├─systemd-udevd.service
lines 1-36
● funny-kath-server
State: degraded
Jobs: 0 queued
Failed: 1 units
Since: Tue 2023-09-05 05:51:47 UTC; 3h 12min ago
CGroup: /
├─user.slice
│ └─user-1000.slice
│ ├─[email protected] …
│ │ └─init.scope
│ │ ├─1302 /lib/systemd/systemd --user
│ │ └─1303 (sd-pam)
│ └─session-1.scope
│ ├─ 1290 sshd: kath [priv]
│ ├─ 1415 sshd: kath@pts/0
│ ├─ 1416 -bash
│ ├─ 1785 PM2 v5.3.0: God Daemon (/home/kath/.pm2)
│ ├─ 1799 PM2 Agent v2.0.3: (/home/kath/.pm2)
│ ├─18231 sudo systemctl status
│ ├─18232 sudo systemctl status
│ ├─18233 systemctl status
│ └─18234 less
├─init.scope
│ └─1 /sbin/init
└─system.slice
├─irqbalance.service
│ └─820 /usr/sbin/irqbalance --foreground
├─netplan-wpa-wlp1s0.service
│ └─712 /sbin/wpa_supplicant -c /run/netplan/wpa-wlp1s0.conf -iwlp1s0 -Dnl80211,wext
├─containerd.service …
│ └─902 /usr/bin/containerd
├─packagekit.service
│ └─2413 /usr/libexec/packagekitd
├─systemd-networkd.service
│ └─802 /lib/systemd/systemd-networkd
├─systemd-udevd.service
lines 1-36
wait
and
sudo journalctl -u cloudflared --no-pager ?sudo systemctl status cloudflared returns
○ cloudflared.service - cloudflared
Loaded: loaded (/etc/systemd/system/cloudflared.service; disabled; vendor preset: enabled)
Active: inactive (dead)
○ cloudflared.service - cloudflared
Loaded: loaded (/etc/systemd/system/cloudflared.service; disabled; vendor preset: enabled)
Active: inactive (dead)
sudo systemctl enable --now cloudflared?too many results to let me view everything in my terminal 💀
kath@funny-kath-server:~/a$ sudo systemctl enable --now cloudflared
Created symlink /etc/systemd/system/multi-user.target.wants/cloudflared.service → /etc/systemd/system/cloudflared.service.
kath@funny-kath-server:~/a$ sudo systemctl enable --now cloudflared
Created symlink /etc/systemd/system/multi-user.target.wants/cloudflared.service → /etc/systemd/system/cloudflared.service.
okay now check the status again
kath@funny-kath-server:~/a$ sudo systemctl status cloudflared
● cloudflared.service - cloudflared
Loaded: loaded (/etc/systemd/system/cloudflared.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2023-09-05 09:08:27 UTC; 1min 45s ago
Main PID: 18354 (cloudflared)
Tasks: 13 (limit: 9288)
Memory: 18.5M
CPU: 1.615s
CGroup: /system.slice/cloudflared.service
└─18354 /usr/bin/cloudflared --no-autoupdate tunnel run --token eyJhIjoiNWE2OWE2YjVlMGVjZWM0MTljMjI2Mzc5MTI0NzFiNjMiLC>
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:27Z INF ICMP proxy will use 192.168.0.228 as source for IPv4
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:27Z INF ICMP proxy will use 2001:8003:9023:d800:f26e:bff:fed>
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:27Z INF Starting metrics server on 127.0.0.1:44575/metrics
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023/09/05 09:08:27 failed to sufficiently increase receive buffer size (was:>
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:27Z INF Registered tunnel connection connIndex=0 connection=>
Sep 05 09:08:27 funny-kath-server systemd[1]: Started cloudflared.
Sep 05 09:08:28 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:28Z INF Registered tunnel connection connIndex=1 connection=>
Sep 05 09:08:28 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:28Z INF Updated to new configuration config=null version=0
Sep 05 09:08:29 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:29Z INF Registered tunnel connection connIndex=2 connection=>
Sep 05 09:08:30 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:30Z INF Registered tunnel connection connIndex=3 connection=>
lines 1-20/20 (END)
kath@funny-kath-server:~/a$ sudo systemctl status cloudflared
● cloudflared.service - cloudflared
Loaded: loaded (/etc/systemd/system/cloudflared.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2023-09-05 09:08:27 UTC; 1min 45s ago
Main PID: 18354 (cloudflared)
Tasks: 13 (limit: 9288)
Memory: 18.5M
CPU: 1.615s
CGroup: /system.slice/cloudflared.service
└─18354 /usr/bin/cloudflared --no-autoupdate tunnel run --token eyJhIjoiNWE2OWE2YjVlMGVjZWM0MTljMjI2Mzc5MTI0NzFiNjMiLC>
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:27Z INF ICMP proxy will use 192.168.0.228 as source for IPv4
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:27Z INF ICMP proxy will use 2001:8003:9023:d800:f26e:bff:fed>
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:27Z INF Starting metrics server on 127.0.0.1:44575/metrics
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023/09/05 09:08:27 failed to sufficiently increase receive buffer size (was:>
Sep 05 09:08:27 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:27Z INF Registered tunnel connection connIndex=0 connection=>
Sep 05 09:08:27 funny-kath-server systemd[1]: Started cloudflared.
Sep 05 09:08:28 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:28Z INF Registered tunnel connection connIndex=1 connection=>
Sep 05 09:08:28 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:28Z INF Updated to new configuration config=null version=0
Sep 05 09:08:29 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:29Z INF Registered tunnel connection connIndex=2 connection=>
Sep 05 09:08:30 funny-kath-server cloudflared[18354]: 2023-09-05T09:08:30Z INF Registered tunnel connection connIndex=3 connection=>
lines 1-20/20 (END)
look like that worked
@Erisa | Out of office ❤️ everything is now working for me