Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Scraping Port Forward number from logs #2343

Closed
minicoz opened this issue Jul 2, 2024 · 5 comments
Closed

Feature request: Scraping Port Forward number from logs #2343

minicoz opened this issue Jul 2, 2024 · 5 comments

Comments

@minicoz
Copy link

minicoz commented Jul 2, 2024

What's the feature 🧐

Im using Proton VPN. Whenever I connect, I seem to be assigned a random PortForward number that then I have to set on my torrent/soulseek provider manually. If I restart gluetun after a week, a new random number is assigned.

I want to see if there is a way to scrape the logs to get the number, then set that as an env variable so that whatever app can just ask what the portforward number is as a docker-compose stack.

Does this make any sense?

Extra information and references

No response

Copy link
Contributor

github-actions bot commented Jul 2, 2024

@qdm12 is more or less the only maintainer of this project and works on it in his free time.
Please:

@minicoz minicoz changed the title Feature request: Scraping Portforward number from logs Feature request: Scraping Port Forward number from logs Jul 2, 2024
@xtinct101
Copy link

cant you just use the
- VPN_PORT_FORWARDING_STATUS_FILE=/gluetun/port.txt

@jagaimoworks
Copy link

According to Gluetun's wiki Gluetun will write the obtained forwarded port into /tmp/gluetun/forwarded_port within the container, which is the default value of the VPN_PORT_FORWARDING_STATUS_FILE option that @xtinct101 mentioned.

There is also the arguably better suited approach by using the built-in control server which is a simple http-server that can also tell you your forwarded port.

@qdm12
Copy link
Owner

qdm12 commented Aug 4, 2024

Thanks @xtinct101 and @jagaimoworks exactly on point. Closing this since it's pretty already done.
Although I'm working (locally for now) on integrations with qbitorrent/transmission/deluge to update the clients on a port forward port obtention/change 😉 Stay tuned (subscribe to #1751)

@qdm12 qdm12 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 4, 2024
Copy link
Contributor

github-actions bot commented Aug 4, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants