diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/remote-management.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/remote-management.mdx
index 573f74699183735..41635b60684e43f 100644
--- a/src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/remote-management.mdx
+++ b/src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/remote-management.mdx
@@ -33,11 +33,37 @@ On Linux, Cloudflare Tunnel installs itself as a system service using `systemctl
    [Service]
    TimeoutStartSec=0
    Type=notify
-   ExecStart=/usr/local/bin/cloudflared tunnel --loglevel debug --logfile <PATH> run --token <TOKEN VALUE>
+   ExecStart=/usr/local/bin/cloudflared tunnel --loglevel debug --logfile /var/log/cloudflared/cloudflared.log run --token <TOKEN VALUE>
    Restart=on-failure
    RestartSec=5s
+
+   [Install]
+   WantedBy=multi-user.target
+   ```
+
+3. Restart `cloudflared.service`:
+
+   ```sh
+   sudo systemctl restart cloudflared
    ```
 
+4. To verify the new configuration, check the service status:
+
+	```sh
+	sudo systemctl status cloudflared
+	```
+	```sh output
+	● cloudflared.service - cloudflared
+     Loaded: loaded (/etc/systemd/system/cloudflared.service; enabled; preset: enabled)
+     Active: active (running) since Wed 2024-10-09 20:02:59 UTC; 2s ago
+   Main PID: 2157 (cloudflared)
+      Tasks: 8 (limit: 1136)
+     Memory: 16.3M
+        CPU: 136ms
+     CGroup: /system.slice/cloudflared.service
+             └─2157 /usr/bin/cloudflared tunnel --loglevel debug --logfile /var/log/cloudflared/cloudflared.log run --token eyJhIjoi...
+	```
+
 </TabItem> <TabItem label="macOS">
 
 On macOS, Cloudflare Tunnel installs itself as a launch agent using `launchctl`. By default, the agent will be called `com.cloudflare.cloudflared`. To configure your tunnel on macOS: