Documentation about restoring a backup is incomplete
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 39
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
the documentation about restoring a backup is incomplete: https://docs.pivpn.io/wireguard/#migrating-pivpn-wireguard
After setting up a new pivpn instance and restoring the backup the following issues arise:
- The
pivpnNETin/etc/pivpn/wireguard/setupVars.confseems to be chosen randomly during initial setup. So it will differ from the one that is used in the backup in/etc/wireguard/wg0.conf. You need to edit/etc/pivpn/wireguard/setupVars.confto set it to the value, that is used in the backup. - Also the iptables rules contain this network and must be changed. On Alpine Linux you have to edit
/etc/iptables/rules-saveand change it to the one from backup. - Restart wg-quick and iptables services or reboot.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the migrating PiVPN WireGuard page at https://docs.pivpn.io/wireguard/#migrating-pivpn-wireguard and compare its restore steps with the reported setupVars.conf and Alpine /etc/iptables/rules-save changes. Update the page to cover matching the backup network values and restarting wg-quick and iptables services or rebooting; done means the restore procedure includes all reported steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100