Closed thebalaa closed 9 months ago
I'm interested in helping fix this, without being able to reboot my cloud VPS it seems like this isn't production ready. Seems like a coin toss between your possible solutions, how difficult is something like this to implement?
Has there been any progress made on this issue?
(FWIW, I started using BoringProxy instead)
I'd rather keep using selfhosted-gateway but this issue is concerning indeed... Not using random ports would help ?
Two fairly annoying issues with the current implementation:
1) Random port assignments from docker do not persist after reboot. 2) Gateway link container overwrites WireGuard keys in entrypoint
Possible solutions:
1) Generate random port number in create-link.sh and set it explicitly on the gateway's link container so it will persist on reboot 2) Add a check in gateway link's entrypoint for existing WireGuard private key, if it exists do not overwrite it