-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reboot host or restart services leads to network unavailability #241
Comments
Hi, So you are using the host's WireGuard interface, which becomes functional once you restart the Docker container? You could also test whether the interface still works while the container is stopped and check whether the connections break due to the startup process. |
seems it's all ok. In logs of wg-portal service I alse didn't find anything suspicious (errors). In UI I see status "connected". I will try to add more information. Could I send my docker-compose.yaml file? |
Just post the contents of the docker-compose.yml file here and remove any sensitive information like passwords, hostnames or public IP addresses. |
I think I solved it. The problem was that, wg-portal ups wg0 interface and wireguard service could not up it one more time (because it was already started). In config.yaml I changed option |
For some reason it works only on Ubuntu 22.04 lts. On CentOS7 it doesn't take any effect. |
@h44z Docker Run
|
Hello. I continue testing v2.0.0-alpha.2. Many bugs are fixed, thanks. Then wireguard is up, it works stable. But i found one problem. Rebooting host, or restarting containers by
docker compose down && docker compose up -d
leads wireguard to network unavailability (although no changes have been made to the config files. Even the external IP does not change). There is no traffic via clients and server (even icmp packets don't get through). Restarting services doesn't take any effect. The only way is to log in web, to go to server config (chapter Peer Defaults) and, without making any changes, to press buttonAPPLY PEER Defauts
. Аfter that, everything is work normal (until the next reboot host or restart services). What is it that causes such incorrect behavior of services???The text was updated successfully, but these errors were encountered: