mirror of
https://github.com/mmatczuk/go-http-tunnel.git
synced 2026-05-15 14:16:17 -06:00
[GH-ISSUE #129] Feature request. I would like an option for the tunnel to never be cut. #77
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/go-http-tunnel#77
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @synaption on GitHub (Apr 17, 2021).
Original GitHub issue: https://github.com/mmatczuk/go-http-tunnel/issues/129
If I try to start a tunnel when a tunnel is already using that port on the server, the program exits with error "failed to start tunnels: connection is being cut". My use case is remote raspberry pies that I never want to lose contact with, so for me the ideal behavior would be to not exit when this error occurs. There are obviously several ways to go about this. I could obviously write a service for systemd or use cron, but it would be nice if go-http-tunnel handled this itself. I might poke around the code and figure it out myself, but I figured I'd ask first and maybe somebody already knows right where to make the change.
@1ubuntuuser commented on GitHub (Jan 20, 2022):
How did you solve this one?