github-starred/go-http-tunnel
2
0
Fork 0
mirror of https://github.com/mmatczuk/go-http-tunnel.git synced 2026-05-15 14:16:17 -06:00
Code Issues 61 Projects Packages Wiki Activity Actions

[GH-ISSUE #90] Running tunneld as a daemon #48

New issue
Closed
opened 2026-05-05 10:58:36 -06:00 by gitea-mirror · 3 comments
gitea-mirror commented 2026-05-05 10:58:36 -06:00
Owner
Copy link

Originally created by @lbajsarowicz on GitHub (Mar 23, 2019).
Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/90

Currently running tunneld needs to get certification and key files provided.
I'd like to run tunneld as a service, so it would be awesome if there's a way to run the binary without passing extra attributes.

Originally created by @lbajsarowicz on GitHub (Mar 23, 2019). Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/90 Currently running `tunneld` needs to get certification and key files provided. I'd like to run `tunneld` as a service, so it would be awesome if there's a way to run the binary without passing extra attributes.
gitea-mirror commented 2026-05-05 10:58:40 -06:00
Author
Owner
Copy link

@bmcgonag commented on GitHub (Mar 31, 2019):

@lbajsarowicz i just added some documentation to the Readme file on the main github page about running the tunneld server as a service using systemd.

It's pretty easy to setup (at least on ubuntu and debian, haven't tried other distros), and just passing the full path to the service of your certificate locations works fine.

I also did the same for a couple of my clients that I run headless so they'll just startup and connect again on reboot. Again, I just pass the -config flag and the full path to the config.yml, and make sure the cert files for the client are in the .tunnel directory with the .yml file...and have that placed in the same directory as the tunnel binary.

Hope it helps,

<!-- gh-comment-id:478371669 --> @bmcgonag commented on GitHub (Mar 31, 2019): @lbajsarowicz i just added some documentation to the Readme file on the main github page about running the tunneld server as a service using systemd. It's pretty easy to setup (at least on ubuntu and debian, haven't tried other distros), and just passing the full path to the service of your certificate locations works fine. I also did the same for a couple of my clients that I run headless so they'll just startup and connect again on reboot. Again, I just pass the -config flag and the full path to the config.yml, and make sure the cert files for the client are in the .tunnel directory with the .yml file...and have that placed in the same directory as the tunnel binary. Hope it helps,
gitea-mirror commented 2026-05-05 10:58:42 -06:00
Author
Owner
Copy link

@lbajsarowicz commented on GitHub (Apr 3, 2019):

@bmcgonag Line

###Run Server as a Service on Ubuntu using Systemd:

Misses a single space after ###

<!-- gh-comment-id:479577672 --> @lbajsarowicz commented on GitHub (Apr 3, 2019): @bmcgonag Line ``` ###Run Server as a Service on Ubuntu using Systemd: ``` Misses a single space after `###`
gitea-mirror commented 2026-05-05 10:58:44 -06:00
Author
Owner
Copy link

@bmcgonag commented on GitHub (Apr 3, 2019):

Updated, and pull request made. Thank you @lbajsarowicz

<!-- gh-comment-id:479593284 --> @bmcgonag commented on GitHub (Apr 3, 2019): Updated, and pull request made. Thank you @lbajsarowicz
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dependabot/go_modules/golang.org/x/net-0.38.0
revert-110-hotfix/dependency
mmt/websocket
mmt/old-websocket
2.1
v.2.0
v.1.2
v.1.1
v.1.0
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/go-http-tunnel#48
No description provided.
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?