Authentication URL failed to load. The operation couldn’t be completed

Got a problem with Viscosity or need help? Ask here!

justinv

Posts: 1
Joined: Sat Dec 03, 2022 8:56 pm

Post by justinv » Sat Dec 03, 2022 9:06 pm
Hi,
Today, I can't connect to the VPN. The error message show that 'Authentication URL failed to load. The operation couldn’t be completed'. But when I copy and paste it to the browser, it is `Authentication Is Successful`.

Anyone can help me. Thanks in advance.

full log:
2022-12-03 16:51:21: Viscosity Mac 1.10.4 (1611)
2022-12-03 16:51:21: Viscosity OpenVPN Engine Started
2022-12-03 16:51:21: Running on macOS 13.0.1
2022-12-03 16:51:21: ---------
2022-12-03 16:51:21: State changed to Connecting
2022-12-03 16:51:21: Checking reachability status of connection...
2022-12-03 16:51:21: Connection is reachable. Starting connection attempt.
2022-12-03 16:51:21: OpenVPN 2.5.7 aarch64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Nov 2 2022
2022-12-03 16:51:21: library versions: OpenSSL 1.1.1s 1 Nov 2022, LZO 2.10
2022-12-03 16:51:22: Resolving address: sg-sin.gw.openvpn.com
2022-12-03 16:51:22: Valid endpoint found: 172.107.213.77:1194:udp
2022-12-03 16:51:22: Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
2022-12-03 16:51:22: Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
2022-12-03 16:51:22: TCP/UDP: Preserving recently used remote address: [AF_INET]172.107.213.77:1194
2022-12-03 16:51:22: Socket Buffers: R=[786896->786896] S=[9216->9216]
2022-12-03 16:51:22: NOTE: setsockopt TCP_NODELAY=1 failed
2022-12-03 16:51:22: UDP link local: (not bound)
2022-12-03 16:51:22: UDP link remote: [AF_INET]172.107.213.77:1194
2022-12-03 16:51:22: State changed to Authenticating
2022-12-03 16:51:22: TLS: Initial packet from [AF_INET]172.107.213.77:1194, sid=3e5feabd cf080d8b
2022-12-03 16:51:22: VERIFY OK: depth=1, CN=CloudVPN Prod CA
2022-12-03 16:51:22: VERIFY KU OK
2022-12-03 16:51:22: Validating certificate extended key usage
2022-12-03 16:51:22: ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2022-12-03 16:51:22: VERIFY EKU OK
2022-12-03 16:51:22: VERIFY OK: depth=0, CN=sg-sin-dc2-b1.cloud.openvpn.net
2022-12-03 16:51:22: Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
2022-12-03 16:51:22: [sg-sin-dc2-b1.cloud.openvpn.net] Peer Connection Initiated with [AF_INET]172.107.213.77:1194
2022-12-03 16:51:22: SENT CONTROL [sg-sin-dc2-b1.cloud.openvpn.net]: 'PUSH_REQUEST' (status=1)
2022-12-03 16:51:22: AUTH_PENDING received, extending handshake timeout from 60s to 900s
2022-12-03 16:51:22: Info command was pushed by server ('OPEN_URL:<masked_url>')
2022-12-03 16:51:22: URL authentication request received from server. Attempting to load URL...
2022-12-03 16:51:23: Error: Authentication URL failed to load. The operation couldn’t be completed. (NSURLErrorDomain error -999.)
2022-12-03 16:51:23: State changed to Disconnecting (Open URL Failed)
2022-12-03 16:51:23: SIGTERM[hard,] received, process exiting
2022-12-03 16:51:23: State changed to Disconnected (Process Terminated)
2022-12-03 16:51:23: Error: Authentication URL failed to load. The operation couldn’t be completed. (NSURLErrorDomain error -999.)
open masked_url from browser:
2022-12-03 at 17.01.52@2x.png
2022-12-03 at [email protected] (51.67 KiB) Viewed 314 times

James

User avatar
Posts: 2214
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Mon Dec 05, 2022 12:04 pm
Hi justinv,

Please try quitting and re-opening Viscosity and see if the issue persists. Viscosity's web view does cache assets, and if something has just recently changed server-side and old cached asset could cause issues.

Please also try re-importing your connection into Viscosity. If the remote web authentication server changed its TLS certificate, and your connection comes bundled with a CA to use for web validation, it's possible it may be out of date and need updating.

If you're still stuck please let us know.

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts Page 1 of 1