You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use gluetun with PIA and forwarding. I have seen many ways to read the forwarded port from gluetun (most of them using the fwd_port file, wich I read is being deprecated) but I think the best way would be gluetun that makes a web request by itself calling a user-configured webhook when the port is being changed and maybe at the start of gluetun too.
Making the web request entirely configurable with a template inside the docker compose file (or a separate config file) would be ideal.
I understand it can take some time to implement such a thing, so a simple GET or POST request with the forwarded port to a user-configurable endpoint it'd be nice too.
Closed issues are NOT monitored, so commenting here is likely to be not seen.
If you think this is still unresolved and have more information to bring, please create another issue.
This is an automated comment setup because @qdm12 is the sole maintainer of this project
which became too popular to monitor issues closed.
What's the feature 🧐
I use gluetun with PIA and forwarding. I have seen many ways to read the forwarded port from gluetun (most of them using the fwd_port file, wich I read is being deprecated) but I think the best way would be gluetun that makes a web request by itself calling a user-configured webhook when the port is being changed and maybe at the start of gluetun too.
Making the web request entirely configurable with a template inside the docker compose file (or a separate config file) would be ideal.
I understand it can take some time to implement such a thing, so a simple GET or POST request with the forwarded port to a user-configurable endpoint it'd be nice too.
I found a program (written in Go) that implement this, if you want to take a look
Thank you for your work!
Extra information and references
No response
The text was updated successfully, but these errors were encountered: