You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When uploading an script with WireGuard, I can ping the board, but the web interface doesn't work. Changing the board and uploading the same script to an esp32 allows me to use the web interface through WireGuard without any issues.
The logs say that the peer is online, and on the server I can see traffic between the server and the client coming from the keepalive messages. I've tried using the public domain name to access the server, but also directly the local ip to test inside the network. Both things fail but work on the esp32
The text was updated successfully, but these errors were encountered:
Got the same issue. It looks like wireguard disables all the outgoing connections except allowed ones. Once I deactivate or before it's connected it works just fine. Worked around by adding SNTP server in local network and adding it in server list
time:
- platform: sntpid: sntp_timetimezone: Europe/Madridservers:
- 0.pool.ntp.org
- 1.pool.ntp.org
- 10.7.0.1 # deploy sntp server on this address
The problem
When uploading an script with WireGuard, I can ping the board, but the web interface doesn't work. Changing the board and uploading the same script to an esp32 allows me to use the web interface through WireGuard without any issues.
Which version of ESPHome has the issue?
2024.4.1
What type of installation are you using?
pip
Which version of Home Assistant has the issue?
No response
What platform are you using?
ESP8266
Board
4-relay board with esp-12f module
Component causing the issue
Wireguard
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
The logs say that the peer is online, and on the server I can see traffic between the server and the client coming from the keepalive messages. I've tried using the public domain name to access the server, but also directly the local ip to test inside the network. Both things fail but work on the esp32
The text was updated successfully, but these errors were encountered: