Fixed: Setting up Argo tunnel to automatically run

Hey friends,

I’m new to Argo / Argo Tunnel and have (I believe) pretty much figured it out for the most part. For reference, I’m running an nginx server (on a pi) through openresty on my home network (before argo I’d just port forward the server on ports 80 and 443). I’ve since closed the ports and now have nginx listen on 8080 and 8443 for HTTP/S respectively.

I am able to run the “cloudflared” command and gain access to my site, but when I close the SSH session or reboot the server the argo connection dies and does not come back up. To “fix” this, I am yet again forced to ssh into the device, run the cloudflared command and have that ssh session be taken up. Ideally, I’d like this argo tunnel to start on boot and not occupy a full ssh terminal that I have to keep up 100% of the time. I’ve followed the official guide here and looked through this community post, but have gained 0 clarification and understand that this is all boiling down to user error. Would anyone be able to help me, please? Thanks for reading :slight_smile:

Edit: Here is a bit more information because I am dumb and forgot to provide it sooner:
The cloudflared.service daemon is running fine, I am now getting a 502 error and in the log, I’m being given the error of

HTTP request error: Error proxying request to origin: tls: first record does not look like a TLS handshake

FINAL EDIT: This has been resolved. My issue was that I was editting my .cloudflared/config.yml file and not my /etc/cloudflared/config.yml. Big surprise, in my /etc/cloudflared/config.yml file I accidentally had:

url: https://localhost:8080

when it should have been http://localhost:8080. Apologies for clogging the forum, I hope this may help those of you in the future who suffer the same issue.