nordvpn
synology-wireguard
Our great sponsors
nordvpn | synology-wireguard | |
---|---|---|
50 | 49 | |
695 | 900 | |
- | - | |
3.5 | 0.0 | |
24 days ago | 24 days ago | |
Shell | Shell | |
GNU Affero General Public License v3.0 | 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.
nordvpn
- [Self Hosted] VPN Mullvad pour les conteneurs Docker
- [Nord Vpn] Après la mise à jour: /run/nordvpn/nordvpnd.sock introuvable
-
Nordlynx, qbittorrent, sonarr, radarr, jellyfin, and jellyseer
version: "3.8" services: nordlynx: image: ghcr.io/bubuntux/nordlynx cap_add: - NET_ADMIN # Required environment: # Review https://github.com/bubuntux/nordvpn#environment-variables - PRIVATE_KEY=mykey # Required - CONNECT=United_States - NET_LOCAL=10.20.30.40/24 # So it can be accessed within the local network - ALLOWED_IPS=10.20.30.40/24 ports: - "6881:6881" #qbittorent - "6881:6881/udp" #qbittorrent - "8080:8080" #qbittorrent - "7878:7878" #radarr - "8989:8989" #sonarr - "9696:9696" #prowlarr - "8097:8096" #jellyfin - "5055:5055" #jellyseer sysctls: - net.ipv6.conf.all.disable_ipv6=1 # Recomended if using ipv4 only qbittorrent: image: linuxserver/qbittorrent container_name: qbittorrent network_mode: service:nordlynx environment: volumes: - /path/to/qbittorrent/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped radarr: image: linuxserver/radarr container_name: radarr network_mode: service:nordlynx environment: volumes: - /path/to/radarr/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped sonarr: image: linuxserver/sonarr container_name: sonarr network_mode: service:nordlynx environment: volumes: - /path/to/sonarr/config:/config - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped prowlarr: image: linuxserver/prowlarr container_name: prowlarr network_mode: service:nordlynx environment: volumes: - /path/to/prowlarr/config:/config depends_on: - nordlynx restart: unless-stopped jellyfin: image: linuxserver/jellyfin container_name: jellyfin network_mode: service:nordlynx environment: - JELLYFIN_PublishedServerUrl=http://10.20.30.184:8097/ volumes: - /path/to/jellyfin/config:/config - /path/to/jellyfin/cache:/cache - /mnt/share_media:/data depends_on: - nordlynx restart: unless-stopped jellyseer: image: fallenbagel/jellyseerr:latest container_name: jellyseer network_mode: service:nordlynx environment: volumes: - /path/to/jellyseer/config:/app/config depends_on: - nordlynx restart: unless-stopped
-
KASM with VPN?
All the infos you need are on the github page > https://github.com/bubuntux/nordvpn
-
NordLynx with docker for torrenting | Transmission and QbitTorrent
Issues · bubuntux/nordvpn (github.com)
-
Docker Image - Invalid Username or Password Bug
On https://github.com/bubuntux/nordvpn it mentions that token login is also supported (Nord v3.15.0+). I've used the token login and it works well for me.
- NordVPN bittorrent contaner inside openmediavault
-
Extremely Slow Torrenting Speed
There has been an issue reported on github: https://github.com/bubuntux/nordvpn/issues/367
-
Meshnet on opnsense router
Two of the popular containers are https://github.com/qdm12/gluetun and https://github.com/bubuntux/nordvpn but it's not clear if either of them can use meshnet.
-
VPN gateway on home server VM
A ubuntu/debian vm with nordvpn official client, use iptables to forward this connection to the vm IP. I've seen a similar approach using docker here https://github.com/bubuntux/nordvpn but this only shares connection to other dockers ct's in the same setup
synology-wireguard
-
VPN + Mapped Drive in Windows?
Try here: https://github.com/runfalk/synology-wireguard
- [Synology] Quelqu'un a-t-il réussi à exécuter Wireguard avec une interface utilisateur dans Docker sur sa boîte de synologie?
- DSM 7.2-64551 RC is now available
-
qBittorrent on Windows won't upload when data is coming through Synology via SMB/NFS/CIFS
It seems like your model is based out of the v1000 platform. See if this can help: https://github.com/runfalk/synology-wireguard/issues/61
- Kernel version of DfSM that comes with the latest DiskStation models
-
Using Synology NAS as VPN server to send the traffic to the internet
Anyone knows how to do this. I installed runfalk/synology-wireguard with complied .spk file, I managed setup macOS client and hand shake is successful. I added /etc/sysctl.conf with net.ipv4.ip_forward=1 as stated in this. But no success, the Synology is reachable via wireguard tunnel but not internet,
-
Wireguard
But you could try this, if your NAS is supported: https://github.com/runfalk/synology-wireguard
not native but this has worked well for me for creating a server endpoint
- VPN solution with static ip assigments ?
- Can't get wireguard to start on Synology NAS
What are some alternatives?
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
synology-docker - An Unofficial Script to Update or Restore Docker Engine and Docker Compose on Synology
docker-wireguard
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.
synology-tailscale - Synology packages for tailscale.com
nordlynx
docker-wireguard-socks-proxy - Expose a WireGuard tunnel as a SOCKS5 proxy
docker - Moby Project - a collaborative project for the container ecosystem to assemble container-based systems [Moved to: https://github.com/moby/moby]
arch-sabnzbdvpn - Docker build script for Arch Linux base with SABnzbd, Privoxy and OpenVPN
homebridge-syno-spk - Homebridge Package for Synology DSM 7.