I do not think so. Most likely there is something wrong with your wireguard configs. Do you configure it manually or do you import config files generated from Windscribe?
I would start with this one. That means that config file is good but credentials has expired or there is something other wrong with config file. I would try to generate the new config file and import. Should it connect it will work.
@kan_ibal Thanks for the hint. A reboot was needed for me to get wireguard in the VPN menu.
@247 My connection also did not work at first, and I needed to set the public IP of my server in the “server address” field instead of its name (that previously worked with the openrepos package), if it is of any help.
Hey, I also was not able to connect via the dns name but via ip address it works nicely. I have a pivpn setup and I’m using dy.fi as the dns provider. Does someone have an idea why the dns name would not work?
Localhost in the /var/run/connman/resolv.conf is very wrong. There should be a local router DNS address or VPN provider DNS. I have local router DNS addresses. No change after wireguard connection.
Could you check if you have DNS address in your wireguard VPN provider config file and what is the address?
/etc/resolv.conf is a symlink to /run/connman-resolv.conf so the content will be the same. As I mentioned in Wireguard in SailfishOS 5.0 - #14 by adekker, I can see nothing wrong with 127.0.0.1. You might see other values by using your DNS alternative.
DNS Alternative has nothing in common with /run/connman/resolv.conf. This file is managed by connmand and provides DNS addresses for system.
Localhost address in /etc/resolv.conf is inherently wrong, because in default setup, it redirects all DNS requests to connmand DNS proxy that is running at localhost that uses DNS’es from /var/run/connman/resolv.conf and you are in the dead loop.
DNS Alternative disables connmand DNS proxy and provides its own(dnsmasq+dnsxcrypt-proxy).