VPN through Network Manager GUI with Pulse Connect Secure host name problem

[Piotr Babiuch]

Release version: Ubuntu 20.04.1 LTS
Version of network-manager-openconnect: 1.2.6-1
Version of openconnect: 8.05-1

VPN connection created through Network Manager GUI with VPN Protocol: Pulse Connect Secure converts gateway host name to IP when making a connection. It results in getting HTTP 404 error in NetworkManager.service logs because of failed SSL certificate validation. Screenshot attached.
Gateway in Network Manager GUI is in URL format: https://xxx

When using openconnect command: sudo openconnect --protocol=pulse https://xxx all works fine.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1899156/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Koen Serneels (eskubu)]

Having the same problem since the upgrade from Ubuntu 21.04 to Ubuntu 22.04.1 LTS. SSL vpn does not connect with certificate error (Server certificate verify failed: signer not found) followed by a 404. Tried selecting root intermediate & appliance cert via the vpn config (next to the option 'CA certificate) as well as adding them to the system to no avail. NetworkManager version 1.36.6 & openconnection version v8.20-1. Usig the CLI as a work around also works for me