nordvpn
cloudflare-ddns
Our great sponsors
nordvpn | cloudflare-ddns | |
---|---|---|
50 | 39 | |
695 | 2,677 | |
- | - | |
3.5 | 2.8 | |
22 days ago | 10 days ago | |
Shell | Python | |
GNU Affero General Public License v3.0 | GNU General Public License v3.0 only |
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
cloudflare-ddns
- Dynamic DNS
-
HTTPS connections complain they're insecure as grocy is using self-signed LSIO cert instead of that provisioned by LE.
For anyone following, this was due to user error in that DDNS was not up to date. For reference, https://github.com/timothymiller/cloudflare-ddns
-
Setting up a new domain with YunoHost
If you want to reach them online, think about using something like this: https://github.com/timothymiller/cloudflare-ddns, this will automaticly update your A records. Or try Cloudflare Tunneling: https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
-
Raspberry Pi services on the internet
Try using this container instead. You can update the A record of your domain to your IP dynamically and use a CNAME for each subdomain so you don’t have to worry about them not resolving when your IP changes.
-
ClouDDNS: Turn your CloudFlare-powered site into a DDNS.
Can you explain the difference between that and this? https://github.com/timothymiller/cloudflare-ddns
- Remote Access
-
Problems with cloudflare tunnels (502 Bad Gateway) + alternatives?
I'm out of ideas on this one, I especially don't understand why the nginx container works and others dont. Besides that I'm interested in other solutions that don't route my whole traffic over one company and limit my traffic/what I am allowed to do and what not. Would a dynamic dns updater also work for my use case? Something like cloudflare-ddns?
-
New to home servers
My recommended roadmap for thing to host is: 1. ssh access * with certificates only and fail2ban config 2. local pihole DNS server * learn how to set up your router and devices to use pihole as DNS 3. local jellyfin * no encryption, no external access, just a simple local network service * Create a domain in pihole, that points to your local jellyfin service 4. a ddns-service like cloudflare-ddns * buy a domain and use ddns to point it to your IP 5. nginx-proxy-manager * enable port-forwarding in your router and obtain a lets-encrypt wildcard-cert for your domain * Create a docker network and add npm, jellyfin, and all other web services that you want to access via your domain * Create a proxy host for each service, give every service a unique subdomain, and use your wildcard cert to enable SSL/TLS for all your services * add all those subdomains to your ddns * use pihhole to point the subdomains to your local IP
- if I buy a domain name can I point it at my homelab that has a dynamic IP?
-
Public File Sharing through Tailscale?
Tailscale recently introduced funnel which is currently in beta and has bandwidth limits so it might work, but personally I'd use a dynamic DNS service like cloudflare-ddns
What are some alternatives?
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
proxmox-scripts
docker-wireguard
docker-cloudflare-ddns - A small amd64/ARM/ARM64 Docker image that allows you to use CloudFlare as a DDNS / DynDNS Provider.
synology-wireguard - WireGuard support for some Synology NAS drives
no-ip - A shell script that works as Dynamic Update Client (DUC) for noip.com
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.
docker-traefik-cloudflare-companion - Automatically Create CNAME records for containers served by Traefik
nordlynx
alpine-qbittorrent-openvpn - qBittorrent docker container with OpenVPN client running as unprivileged user on alpine linux
docker-wireguard-socks-proxy - Expose a WireGuard tunnel as a SOCKS5 proxy
alpine-mariadb - MariaDB running on Alpine Linux [Docker]