cloudflare-ddns
pivpn
cloudflare-ddns | pivpn | |
---|---|---|
39 | 311 | |
2,707 | 6,892 | |
- | 2.5% | |
2.3 | 6.9 | |
5 days ago | 21 days ago | |
Python | Shell | |
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.
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
pivpn
- PiVPN v4.6.0: The End
-
Network setup for remote access
PiVPN for classic VPN software https://pivpn.io - Wireguard would be my choice
-
Can't get it to run after installation, although running vpn from this pi before
Linux retropie 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
-
Easy VPN install on Debian
Wondering what people are using these days to get a VPN (Wireguard?) up and running easily. Is Wireguard itself simple enough that one can just ... do this? I'm thinking of something like PiVPN which does appear to still exist but I'm unsure of how up-to-date it is. Specifically, I like terminal commands just fine, but would prefer not to have to manually configure a basic VPN (internet gateway) and its associated profiles/certificates.
- LAN-to-LAN VPN
-
setting up remote access for homelab
A real simple way is pivpn in a vm. Super easy to set up and manage users. https://github.com/pivpn/pivpn
- Festplatten / NAS die sich via Cloud synchronisieren?
- Wireguard without VPS?
-
Remote Access
They're easily set up via the guided PiVPN installation script. Should work on everything that's Debian-based, not just on Rasbian running on a Pi.
-
Build your own private WireGuard VPN with PiVPN
under Features in [1]:
* Doesn't need to be a Raspberry Pi™, It runs on any x86_64 system
[1] https://pivpn.io/
What are some alternatives?
proxmox-scripts
tailscale - The easiest, most secure way to use WireGuard and 2FA.
docker-cloudflare-ddns - A small amd64/ARM/ARM64 Docker image that allows you to use CloudFlare as a DDNS / DynDNS Provider.
docker-wireguard
no-ip - A shell script that works as Dynamic Update Client (DUC) for noip.com
wg-easy - The easiest way to run WireGuard VPN + Web-based Admin UI. [Moved to: https://github.com/wg-easy/wg-easy]
nordvpn - NordVpn Docker Client
wg-easy - The easiest way to run WireGuard VPN + Web-based Admin UI.
docker-traefik-cloudflare-companion - Automatically Create CNAME records for containers served by Traefik
wireguard-windows - Download WireGuard for Windows at https://www.wireguard.com/install . This repo is a mirror only. Official repository is at https://git.zx2c4.com/wireguard-windows
alpine-qbittorrent-openvpn - qBittorrent docker container with OpenVPN client running as unprivileged user on alpine linux
dnscrypt-proxy - dnscrypt-proxy 2 - A flexible DNS proxy, with support for encrypted DNS protocols.