This is without a doubt one of the worst ‘updates’ I’ve ever done on any device or across any software, broke my pi’s internet connection, had to reflash OS and reinstall pihole from scratch. Now it looks like Pivpn doesn’t work with v6? What are the vpn options?
**SOLUTION
Run sudo touch /etc/pihole/setupVars.conf before using pivpn install script
Was able to EASILY set up wireguard, add client and connect like I used to be able to before having to jump thru all these hoops with this basically still in beta ‘update.’
I’ve noticed people updating to v6, with PiVPN, without issues & others having problems. The solution has been referenced in a few other locations previously.
As I have 2 devices that use gravity-sync, and 1 device with PiVPN, I plan to do backups & testing prior to making changes to my network.
Ill just wait for a stable version for v6. Current mines is working properly on v5
Pihole unbound
Pivpn running wireguard server with 5 client
All is running on rpi zero 2 W. Though my wireguard connection is max out as 80mbps up and down
To be able to connect to my pi & home network while away, same reason pretty much anyone used pivpn. Not sure why I want it is relevant to how to set it up with v6.
Hello again, this is a copy of my docker-compose.yml file. You will have to replace the **** with the password for your web client. You will also have to look in the wireguard documentation to generate the key for the PASSWORD_HASH field. You will have to put the domain you have pihole running on in WG_HOST to be able to access it from the outside with wireguard.
Then, in the DNS configuration you will have to set the custom server as “10.8.1.30#5053”
services:
pihole:
container_name: pihole
image: pihole/pihole:latest
ports:
# DNS Ports
- "53:53/tcp"
- "53:53/udp"
# Default HTTP Port
- "80:80/tcp"
# Default HTTPs Port. FTL will generate a self-signed certificate
- "443:443/tcp"
# Uncomment the below if using Pi-hole as your DHCP Server
#- "67:67/udp"
environment:
# Set the appropriate timezone for your location (https://en.wikipedia.org/wiki/List_of_tz_database_time_zones), e.g:
TZ: 'Europe/Madrid'
# Set a password to access the web interface. Not setting one will result in a random password being assigned
FTLCONF_webserver_api_password: '*****'
# Volumes store your data between container upgrades
volumes:
# For persisting Pi-hole's databases and common configuration file
- './etc-pihole:/etc/pihole'
# Uncomment the below if you have custom dnsmasq config files that you want to persist. Not needed for most starting fresh with Pi-hole v6. If you're upgrading from v5 you and have used this directory before, you should keep it enabled for the first v6 container start to allow for a complete migration. It can be removed afterwards
- './etc-dnsmasq.d:/etc/dnsmasq.d'
cap_add:
#See https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
# Required if you are using Pi-hole as your DHCP server, else not needed
-NET_ADMIN
restart: unless-stopped
hostname: "pi.hole"
networks:
wg-easy:
ipv4_address: 10.8.1.3
dnscrypt:
container_name: dnscrypt-proxy
image: klutchell/dnscrypt-proxy
restart: unless-stopped
networks:
wg-easy:
ipv4_address: 10.8.1.30
wg-easy:
container_name: wg-easy
image: ghcr.io/wg-easy/wg-easy
environment:
- PASSWORD_HASH=***************************
- WG_DEFAULT_DNS=10.8.1.3
- WG_HOST=home.domain.com
- LANG=en
volumes:
- ./config:/etc/wireguard
- /lib/modules:/lib/modules
ports:
- "51820:51820/udp"
- "51821:51821/tcp"
restart: unless-stopped
cap_add:
-NET_ADMIN
- SYS_MODULE
sysctls:
- net.ipv4.ip_forward=1
- net.ipv4.conf.all.src_valid_mark=1
networks:
wg-easy:
ipv4_address: 10.8.1.2
networks:
wg-easy:
ipam:
config:
- subnet: 10.8.1.0/24
volumes:
keys:```
Because you asked for options so why wouldn’t i ask for your use case? I didn’t ask why you want it. I asked what you used it for. Anyway i would recommend Tailscale.
Right, I’m frustrated with how sh** this ‘update’ is and all the issues, I apologize. Tailscale looks like it’s paid, is wireguard not an option anymore?