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

Is this repo maintained? #101

Open
chrisjohnson00 opened this issue Jul 10, 2021 · 7 comments
Open

Is this repo maintained? #101

chrisjohnson00 opened this issue Jul 10, 2021 · 7 comments

Comments

@chrisjohnson00
Copy link

chrisjohnson00 commented Jul 10, 2021

Commit history shows only README.md updates since 2018.

There's been lots of changes implemented by users, myself included, but no PR merges from @MarkusMcNugen

Any suggestions on moving forward with a location where collaboration occurs?
In my fork I've added ARM support.
#96 adds automatic restart on VPN failure.
Both of these were hot topics and it would be great to get them out to everyone, from a central location.

I am not interested in being the sole maintainer, but would be willing to contribute my github action changes (ARM support) and help in other ways.

@Altycoder
Copy link

Altycoder commented Jul 19, 2021

Well, the oldest pull request is Jan 2019 and the oldest unresolved issue is Oct 2018...

Over the weekend I discovered gluetun by chance (https://github.com/qdm12/gluetun) so I may give that a go and then set up a torrent client only container rather than having them bundled together.

I still have issues with this container not re-establishing openvpn connections if they fail after 2-3 days of running. It's been an open issue for a while now.

@chrisjohnson00
Copy link
Author

Well, the oldest pull request is Jan 2019 and the oldest unresolved issue is Oct 2018...

Over the weekend I discovered gluten by chance (https://github.com/qdm12/gluetun) so I may give that a go and then set up a torrent client only container rather than having them bundled together.

I still have issues with this container not re-establishing openvpn connections if they fail after 2-3 days of running. It's been an open issue for a while now.

Depending on how you are running your container, the work done in #96 seems to be helping some people. Unfortunately it's not been too helpful for me, running in Kubernetes, but does make me feel more secure... knowing that it isn't reconnecting w/o VPN.

@Altycoder
Copy link

Well I'm now using gluetun and qbittorrent from linuxserver and all seems to be working fine.

The additional advantage being that I can also route other containers over gluetun as well

@chrisjohnson00
Copy link
Author

Well I'm now using gluetun and qbittorrent from linuxserver and all seems to be working fine.

The additional advantage being that I can also route other containers over gluetun as well

Sounds cool, I'm going to look into it later!

@1RandomDev
Copy link

Well I'm now using gluetun and qbittorrent from linuxserver and all seems to be working fine.

The additional advantage being that I can also route other containers over gluetun as well

Is this combination 100% secure so that there's never sent any request with my real IP? What if the VPN or gluetun fails?

@Altycoder
Copy link

Yes, I've set up qbittorrent to only use tun0 interface so if gluetun goes down, then qbittorrent has no network connection

@chrisjohnson00
Copy link
Author

Seems this isn't maintained... and I've moved on from using this as well. Following the suggestions provided here I'm now using a Docker Compose deployment with Gluten and qbittorrent with great success.

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

3 participants