docker-qBittorrentvpn
The Lounge
docker-qBittorrentvpn | The Lounge | |
---|---|---|
35 | 61 | |
163 | 5,391 | |
- | 0.7% | |
0.0 | 9.3 | |
6 months ago | 5 days ago | |
Shell | TypeScript | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-qBittorrentvpn
-
Need help with WebUI on Qbittorent
Looking at the Github issues for the container many seem to be in the same situation as you: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/issues There doesn't seem to be any activity from the developer either.
-
What am I doing wrong? Can't get container to spin up
I'm trying to deploy the markusmcnugen/qbittorrentvpn image but I'm having issues.
-
How much better would my torrenting experience be with port forwarding?
- Docker container https://github.com/MarkusMcNugen/docker-qBittorrentvpn
-
Titles are hard but collecting your favourite shows shouldn't be
In terms of downloading your "Linux ISO's" automatically, I highly recommend setting up a qbittorent/vpn combo docker container, such as this one. There's also an entire set of programs with docker containers youll see referred to as the "*arr" stack, which help to manage your collection, as well as automatically download your selected media as it becomes available. These are a bit trickier to set up, but once you have everything configured and running, they are a godsend.
-
Docker linuxserver.io/qbittorrent: can't find how to attach a vpn network interface
why not use qbittorrentvpn. Auto kill switch, etc. https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/
-
Set Allow Rule to Access Docker Container WebUI
Hey all, I'm pretty decent with normal networking on routers and switches, etc. but I know very VERY little about iptables. I am trying to fix an issue with a qBittorrent + VPN container. The VPN includes a script setting up a bunch of iptables rules to prevent leaks outside of the VPN. Script is located here: https://github.com/MarkusMcNugen/docker-qBittorrentvpn/blob/focal/qbittorrent/iptables.sh
-
Losing my mind over docker networking.
Been having issues with docker ever since I first tried it, I can't for the life of me access it on the supposedly open ports. Tried setting up this docker for usage in my home plex server with arr services.
-
VPN and Qbittorrent containers
I went with the qbittorrentvpn container.
-
Issue - Cannot access qbittorrent WebUI from outside local network. Using a docker image that automatically puts it on a VPN. Any ideas?
So here's the situation. I have a seedbox at home. It is currently running this docker image: https://hub.docker.com/r/markusmcnugen/qbittorrentvpn/ Which runs qBittorrent and OpenVPN. It's set up so that all of the torrenting traffic goes through the VPN while the rest of my seedbox can be used for other things without having to worry about the VPN. I access this seedbox using the WebUI, which works fine whenever I'm on the local network.
-
Apple Mac Plex Servers
Have Sonarr, Radarr, Sabnzbd, qBittorrent/VPN (NordVPN just for qBittorrent, not on Usenet connections) running in containers on the NAS using Docker Compose. Had OMBI also connected, but has been troublesome as of late for me. Newshosting as my usenet provider, NZBGeek for usenet indexing, Rargb and Nyaa for torrents. Just joined a few private trackers, but those are manually managed and seeding day and night.
The Lounge
-
Simplicity of IRC
IRC as a protocol is indeed incredibly simple and easy to get started with. Years ago did discover this when I was able to make [this atrocity](https://github.com/creesch/discordIRCd) bridging IRC and discord where for IRC I effectively did a simple server implementation.
There is a caveat, though. Like many older protocols (ftp) there is a lot that was not initially written down or left up to clients and server implementations. This, does lead to a lot of edge cases you need to be aware of once you want to actually support a wider user group.
Also, as this is apparently is still a discussion. IRC is not simple from a modern user UX perception. Registration can be complex and confusing, though hidden a bit through clients. Managing channels with various flags is a whole other thing. Then there is also the fact that these days people are no longer used to the fact that they can't see messages from periods where they were not connected. Of course, the latter can be easily handled by a BNC or fancy clients like https://thelounge.chat . But, that is only easy for technically inclined folks.
-
Posthog is closing their Slack community in favor of forum
> It’s 2024, people aren’t going to go out of their way to setup “bouncers” to keep up with conversation that happens when they’re not online or leave their computer running 24/7.
You can just set up something like The Lounge [0].
[0] https://thelounge.chat/
-
Show HN: GodotOS: A Fake Operating System Interface Made in the Godot Engine
Excellent idea! You'll have a mature, open standard protocol under the hood, with no vendor lock-in, excellent extensibility, and great modern frontends like The Lounge (https://thelounge.chat/) or Convos (https://convos.chat/) to choose from (and you can choose).
- IRC Is the Only Viable Chat Protocol
- Show HN: Halloy – A GUI Application in Rust for IRC
- New thelounge Theme: iAnon
- The Lounge 4.4.0 released - the self-hosted web IRC client
-
Matrix 2.0: How we’re making Matrix go voom
For the other layers one can front-end IRC with TheLounge [1][2] or Convos [3][4]. TheLounge only persists history in private mode meaning that users are created in that front-end and chat messages are in Redis. For small networks or groups of friends this is probably fine.
Notably missing is voice chat. I use the Mumble client [5] with the Murmur or uMurmur [6] server which is light-weight enough to run on ones home router. I use it on Alpine Linux, works great. It's not a shiny and attention grabbing as Discord but probably fine for everyone else. For people to create their own voice channels would require the full-blown Murmur server.
[1] - https://github.com/thelounge
[2] - https://thelounge.chat/
[3] - https://github.com/convos-chat/convos/
[4] - https://convos.chat/
[5] - https://www.mumble.info/
[6] - https://github.com/umurmur/umurmur/wiki/Configuration
-
I'm trying to set up a client device that will remain connected to a server that I can remotely log into
As another self-hosted solution, I quite like TheLounge (https://thelounge.chat)
-
Most used selfhosted services in 2022?
TheLounge (https://github.com/thelounge/thelounge) - web IRC client that I set to listen on my vpn/mesh. Works great on desktop and mobile, and supports push notifications.
What are some alternatives?
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
ZNC - Official repository for the ZNC IRC bouncer
gluetun - VPN client in a thin Docker container for multiple VPN providers, written in Go, and using OpenVPN or Wireguard, DNS over TLS, with a few proxy servers built-in.
Kiwi IRC - 🥝 Next generation of the Kiwi IRC web client
YoutubeDL-Material - Self-hosted YouTube downloader built on Material Design
Convos - Convos :busts_in_silhouette: is the simplest way to use IRC in your browser [Moved to: https://github.com/convos-chat/convos]
arch-delugevpn - Docker build script for Arch Linux base with Deluge, Privoxy and OpenVPN
Quassel IRC - Quassel IRC: Chat comfortably. Everywhere.
Portainer - Making Docker and Kubernetes management easy.
Weechat - The extensible chat client.
arch-rtorrentvpn - Docker build script for Arch Linux base with ruTorrent, rTorrent, autodl-irssi, Privoxy and OpenVPN
InspIRCd - A modular C++ IRC server (ircd).