The WG profile does not work with WireSock on Windows 11.
It works with the official WireGuard.
The competitors WG profile works with both.
WG Profile from competitor
[Interface]
PrivateKey = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Address = 1X.1X.5X.1X/32, fdXX:1X:1X::1XXX/128
DNS = 1X.3X.3X.8, 20XX:dXX::8
[Peer]
PublicKey = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
PresharedKey = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = xxx.domain.tld:443
PersistentKeepalive = 25WG Profile for xeovo.com
[Interface]
PrivateKey = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Address = 1X.1XX.1XX.1XX/32, fdXX:eXX:6XXX::X:9fXX/128
DNS = 1X.X.X.2X
[Peer]
PublicKey = XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = xx.domain.tld:443
6 Comments
Hi,
We don't officially support this client, however we just tested it out and it seems to work with our configuration files. We also tested configuration files with port 443.
It shows “Connected,” but the webpage won't open.
The following errors appear on the web page:
DNS_PROBE_STARTED
DNS_PROBE_FINISHED_BAD_CONFIG
I believe this is because the WG profile for xeovo.com does not include an IPv6 DNS address.
Could be an issue on WireSock side and how they implemented DNS, IPv6 or both.
For the test try using public DNS such as Quad9 or CloudFlare. Simply modify DNS address in configuration file to (this is Quad9):
DNS = 9.9.9.9, 2620:fe::feIf this solves the issue, you can add next IPv6 to original configuration file:
fd00:1234::20I will pass this to our technical team and we will implement IPv6 DNS in generator.
I implemented the proposed solution but was unable to resolve the issue.
I will send feedback to WireSock.
Thank you for your assistance.
By contacting the WireSock developer and enabling virtual adapter mode, we were able to resolve the issue.