amazeballs 2 Posted ... (edited) I have tried deleting the app, restarting the Mac and then reinstalling, with no joy. I even tried the little 'First Aid' thing on the Eddie Client and the app moved to a non responsive state. I have since installed Tunnelblick and it worked fine. Any ideas? Log is below. . 2019.08.18 13:23:27 - Eddie version: 2.16.3 / macos_x64, System: MacOS, Name: 10.14.6, Version: Darwin captainplanet-MacBook-Pro.local 18.7.0 Darwin Kernel Version 18.7.0: Thu Jun 20 18:42:21 PDT 2019; root:xnu-4903.270.47~4/RELEASE_X86_64 x86_64, Mono/.Net: v4.0.30319 . 2019.08.18 13:23:27 - Reading options from /Users/captainplanet/.airvpn/default.xml . 2019.08.18 13:23:27 - Command line arguments (1): gui.osx.style="dark" . 2019.08.18 13:23:28 - Profile path: /Users/captainplanet/.airvpn/default.xml . 2019.08.18 13:23:29 - OpenVPN Driver - Expected . 2019.08.18 13:23:29 - OpenVPN - Version: 2.4.6 - OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10 (/Applications/AirVPN.app/Contents/MacOS/openvpn) . 2019.08.18 13:23:29 - SSH - Version: OpenSSH_7.9p1, LibreSSL 2.7.3 (/usr/bin/ssh) . 2019.08.18 13:23:29 - SSL - Version: stunnel 5.48 (/Applications/AirVPN.app/Contents/MacOS/stunnel) . 2019.08.18 13:23:29 - curl - Version: 7.54.0 (/usr/bin/curl) . 2019.08.18 13:23:29 - Certification Authorities: /Applications/AirVPN.app/Contents/MacOS/../Resources/cacert.pem . 2019.08.18 13:23:29 - Updating systems & servers data ... I 2019.08.18 13:23:30 - Ready . 2019.08.18 13:23:32 - Systems & servers data update completed I 2019.08.18 13:23:57 - Session starting. I 2019.08.18 13:23:57 - Checking authorization ... ! 2019.08.18 13:23:58 - Connecting to Leo (United States, Dallas, Texas) . 2019.08.18 13:23:58 - OpenVPN > OpenVPN 2.4.6 x86_64-apple-darwin17.6.0 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Jul 29 2018 . 2019.08.18 13:23:58 - OpenVPN > library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10 . 2019.08.18 13:23:58 - Connection to OpenVPN Management Interface . 2019.08.18 13:23:58 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3129 . 2019.08.18 13:23:58 - OpenVPN > Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key . 2019.08.18 13:23:58 - OpenVPN > Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication . 2019.08.18 13:23:58 - OpenVPN > Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key . 2019.08.18 13:23:58 - OpenVPN > Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication . 2019.08.18 13:23:58 - OpenVPN > TCP/UDP: Preserving recently used remote address: [AF_INET]199.249.230.24:443 . 2019.08.18 13:23:58 - OpenVPN > Socket Buffers: R=[786896->262144] S=[9216->262144] . 2019.08.18 13:23:58 - OpenVPN > UDP link local: (not bound) . 2019.08.18 13:23:58 - OpenVPN > UDP link remote: [AF_INET]199.249.230.24:443 . 2019.08.18 13:23:58 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3129 . 2019.08.18 13:23:58 - OpenVPN > TLS: Initial packet from [AF_INET]199.249.230.24:443, sid=3435b106 c901741e . 2019.08.18 13:23:58 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org . 2019.08.18 13:23:58 - OpenVPN > VERIFY KU OK . 2019.08.18 13:23:58 - OpenVPN > Validating certificate extended key usage . 2019.08.18 13:23:58 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication . 2019.08.18 13:23:58 - OpenVPN > VERIFY EKU OK . 2019.08.18 13:23:58 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Leo, emailAddress=info@airvpn.org . 2019.08.18 13:23:59 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA . 2019.08.18 13:23:59 - OpenVPN > [Leo] Peer Connection Initiated with [AF_INET]199.249.230.24:443 . 2019.08.18 13:24:00 - OpenVPN > SENT CONTROL [Leo]: 'PUSH_REQUEST' (status=1) . 2019.08.18 13:24:00 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.20.162.1,dhcp-option DNS6 fde6:7a:7d20:10a2::1,tun-ipv6,route-gateway 10.20.162.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:10a2::106e/64 fde6:7a:7d20:10a2::1,ifconfig 10.20.162.112 255.255.255.0,peer-id 3,cipher AES-256-GCM' . 2019.08.18 13:24:00 - OpenVPN > Pushed option removed by filter: 'redirect-gateway ipv6 def1 bypass-dhcp' . 2019.08.18 13:24:00 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified . 2019.08.18 13:24:00 - OpenVPN > OPTIONS IMPORT: compression parms modified . 2019.08.18 13:24:00 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified . 2019.08.18 13:24:00 - OpenVPN > OPTIONS IMPORT: route-related options modified . 2019.08.18 13:24:00 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified . 2019.08.18 13:24:00 - OpenVPN > OPTIONS IMPORT: peer-id set . 2019.08.18 13:24:00 - OpenVPN > OPTIONS IMPORT: adjusting link_mtu to 1625 . 2019.08.18 13:24:00 - OpenVPN > OPTIONS IMPORT: data channel crypto options modified . 2019.08.18 13:24:00 - OpenVPN > Data Channel: using negotiated cipher 'AES-256-GCM' . 2019.08.18 13:24:00 - OpenVPN > Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key . 2019.08.18 13:24:00 - OpenVPN > Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key . 2019.08.18 13:24:00 - OpenVPN > ROUTE_GATEWAY 192.168.1.254/255.255.255.0 IFACE=en0 HWADDR=f4:5c:89:9a:ec:03 . 2019.08.18 13:24:00 - OpenVPN > GDG6: remote_host_ipv6=n/a . 2019.08.18 13:24:00 - OpenVPN > ROUTE6_GATEWAY fe80::1 IFACE=en0 . 2019.08.18 13:24:00 - OpenVPN > Opening utun (connect(AF_SYS_CONTROL)): Resource busy (errno=16) . 2019.08.18 13:24:00 - OpenVPN > Opened utun device utun1 . 2019.08.18 13:24:00 - OpenVPN > do_ifconfig, tt->did_ifconfig_ipv6_setup=1 . 2019.08.18 13:24:00 - OpenVPN > /sbin/ifconfig utun1 delete . 2019.08.18 13:24:00 - OpenVPN > ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address . 2019.08.18 13:24:00 - OpenVPN > NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure . 2019.08.18 13:24:00 - OpenVPN > /sbin/ifconfig utun1 10.20.162.112 10.20.162.112 netmask 255.255.255.0 mtu 1500 up . 2019.08.18 13:24:00 - OpenVPN > /sbin/route add -net 10.20.162.0 10.20.162.112 255.255.255.0 . 2019.08.18 13:24:00 - OpenVPN > add net 10.20.162.0: gateway 10.20.162.112 . 2019.08.18 13:24:00 - OpenVPN > route: writing to routing socket: File exists . 2019.08.18 13:24:00 - OpenVPN > /sbin/ifconfig utun1 inet6 fde6:7a:7d20:10a2::106e/64 . 2019.08.18 13:24:00 - OpenVPN > add_route_ipv6(fde6:7a:7d20:10a2::/64 -> fde6:7a:7d20:10a2::106e metric 0) dev utun1 . 2019.08.18 13:24:00 - OpenVPN > /sbin/route add -inet6 fde6:7a:7d20:10a2:: -prefixlen 64 -iface utun1 . 2019.08.18 13:24:00 - OpenVPN > add net fde6:7a:7d20:10a2::: gateway utun1: File exists . 2019.08.18 13:24:00 - OpenVPN > /sbin/route add -net 199.249.230.24 192.168.1.254 255.255.255.255 . 2019.08.18 13:24:00 - OpenVPN > add net 199.249.230.24: gateway 192.168.1.254 . 2019.08.18 13:24:00 - OpenVPN > /sbin/route add -net 0.0.0.0 10.20.162.1 128.0.0.0 . 2019.08.18 13:24:00 - OpenVPN > add net 0.0.0.0: gateway 10.20.162.1 . 2019.08.18 13:24:00 - OpenVPN > /sbin/route add -net 128.0.0.0 10.20.162.1 128.0.0.0 . 2019.08.18 13:24:00 - OpenVPN > add net 128.0.0.0: gateway 10.20.162.1 . 2019.08.18 13:24:00 - OpenVPN > add_route_ipv6(::/3 -> fde6:7a:7d20:10a2::1 metric -1) dev utun1 . 2019.08.18 13:24:00 - OpenVPN > /sbin/route add -inet6 :: -prefixlen 3 -iface utun1 . 2019.08.18 13:24:00 - OpenVPN > add net ::: gateway utun1 . 2019.08.18 13:24:00 - OpenVPN > add_route_ipv6(2000::/4 -> fde6:7a:7d20:10a2::1 metric -1) dev utun1 . 2019.08.18 13:24:00 - OpenVPN > /sbin/route add -inet6 2000:: -prefixlen 4 -iface utun1 . 2019.08.18 13:24:00 - OpenVPN > add net 2000::: gateway utun1 . 2019.08.18 13:24:00 - OpenVPN > add_route_ipv6(3000::/4 -> fde6:7a:7d20:10a2::1 metric -1) dev utun1 . 2019.08.18 13:24:00 - OpenVPN > /sbin/route add -inet6 3000:: -prefixlen 4 -iface utun1 . 2019.08.18 13:24:00 - OpenVPN > add net 3000::: gateway utun1 . 2019.08.18 13:24:00 - OpenVPN > add_route_ipv6(fc00::/7 -> fde6:7a:7d20:10a2::1 metric -1) dev utun1 . 2019.08.18 13:24:00 - OpenVPN > /sbin/route add -inet6 fc00:: -prefixlen 7 -iface utun1 . 2019.08.18 13:24:00 - OpenVPN > add net fc00::: gateway utun1 . 2019.08.18 13:24:00 - DNS of a network adapter forced (Wi-Fi, from Automatic to 10.20.162.1, fde6:7a:7d20:10a2::1) . 2019.08.18 13:24:01 - DNS of a network adapter forced (Bluetooth PAN, from Automatic to 10.20.162.1, fde6:7a:7d20:10a2::1) . 2019.08.18 13:24:01 - DNS of a network adapter forced (Thunderbolt Bridge, from Automatic to 10.20.162.1, fde6:7a:7d20:10a2::1) . 2019.08.18 13:24:01 - Routes, added a new route, 199.249.230.22 for gateway 10.20.162.1 . 2019.08.18 13:24:01 - Routes, added a new route, 2620:7:6001:787e:eb0:baa4:8d47:2e19 for gateway fde6:7a:7d20:10a2::1 . 2019.08.18 13:24:01 - Flushing DNS I 2019.08.18 13:24:01 - Checking route IPv4 . 2019.08.18 13:24:01 - curl: (60) SSL certificate problem: certificate has expired . 2019.08.18 13:24:01 - More details here: https://curl.haxx.se/docs/sslcerts.html . 2019.08.18 13:24:01 - curl performs SSL certificate verification by default, using a "bundle" . 2019.08.18 13:24:01 - of Certificate Authority (CA) public keys (CA certs). If the default . 2019.08.18 13:24:01 - bundle file isn't adequate, you can specify an alternate file . 2019.08.18 13:24:01 - using the --cacert option. . 2019.08.18 13:24:01 - If this HTTPS server uses a certificate signed by a CA represented in . 2019.08.18 13:24:01 - the bundle, the certificate verification probably failed due to a . 2019.08.18 13:24:01 - problem with the certificate (it might be expired, or the name might . 2019.08.18 13:24:01 - not match the domain name in the URL). . 2019.08.18 13:24:01 - If you'd like to turn off curl's verification of the certificate, use . 2019.08.18 13:24:01 - the -k (or --insecure) option. . 2019.08.18 13:24:01 - HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure. . 2019.08.18 13:24:01 - Checking route (2° try) . 2019.08.18 13:24:03 - curl: (60) SSL certificate problem: certificate has expired . 2019.08.18 13:24:03 - More details here: https://curl.haxx.se/docs/sslcerts.html . 2019.08.18 13:24:03 - curl performs SSL certificate verification by default, using a "bundle" . 2019.08.18 13:24:03 - of Certificate Authority (CA) public keys (CA certs). If the default . 2019.08.18 13:24:03 - bundle file isn't adequate, you can specify an alternate file . 2019.08.18 13:24:03 - using the --cacert option. . 2019.08.18 13:24:03 - If this HTTPS server uses a certificate signed by a CA represented in . 2019.08.18 13:24:03 - the bundle, the certificate verification probably failed due to a . 2019.08.18 13:24:03 - problem with the certificate (it might be expired, or the name might . 2019.08.18 13:24:03 - not match the domain name in the URL). . 2019.08.18 13:24:03 - If you'd like to turn off curl's verification of the certificate, use . 2019.08.18 13:24:03 - the -k (or --insecure) option. . 2019.08.18 13:24:03 - HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure. . 2019.08.18 13:24:03 - Checking route (3° try) . 2019.08.18 13:24:05 - curl: (60) SSL certificate problem: certificate has expired . 2019.08.18 13:24:05 - More details here: https://curl.haxx.se/docs/sslcerts.html . 2019.08.18 13:24:05 - curl performs SSL certificate verification by default, using a "bundle" . 2019.08.18 13:24:05 - of Certificate Authority (CA) public keys (CA certs). If the default . 2019.08.18 13:24:05 - bundle file isn't adequate, you can specify an alternate file . 2019.08.18 13:24:05 - using the --cacert option. . 2019.08.18 13:24:05 - If this HTTPS server uses a certificate signed by a CA represented in . 2019.08.18 13:24:05 - the bundle, the certificate verification probably failed due to a . 2019.08.18 13:24:05 - problem with the certificate (it might be expired, or the name might . 2019.08.18 13:24:05 - not match the domain name in the URL). . 2019.08.18 13:24:05 - If you'd like to turn off curl's verification of the certificate, use . 2019.08.18 13:24:05 - the -k (or --insecure) option. . 2019.08.18 13:24:05 - HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure. E 2019.08.18 13:24:05 - Checking route IPv4 failed. . 2019.08.18 13:24:05 - OpenVPN > Initialization Sequence Completed ! 2019.08.18 13:24:05 - Disconnecting . 2019.08.18 13:24:05 - Routes, removed a route previously added, 199.249.230.22 for gateway 10.20.162.1 . 2019.08.18 13:24:05 - Routes, removed a route previously added, 2620:7:6001:787e:eb0:baa4:8d47:2e19 for gateway fde6:7a:7d20:10a2::1 . 2019.08.18 13:24:05 - Sending management termination signal . 2019.08.18 13:24:05 - Management - Send 'signal SIGTERM' . 2019.08.18 13:24:05 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM' . 2019.08.18 13:24:05 - OpenVPN > SIGTERM received, sending exit notification to peer . 2019.08.18 13:24:06 - OpenVpn Management > SUCCESS: signal SIGTERM thrown . 2019.08.18 13:24:10 - OpenVPN > /sbin/route delete -net 199.249.230.24 192.168.1.254 255.255.255.255 . 2019.08.18 13:24:10 - OpenVPN > delete net 199.249.230.24: gateway 192.168.1.254 . 2019.08.18 13:24:10 - OpenVPN > /sbin/route delete -net 0.0.0.0 10.20.162.1 128.0.0.0 . 2019.08.18 13:24:10 - OpenVPN > delete net 0.0.0.0: gateway 10.20.162.1 . 2019.08.18 13:24:10 - OpenVPN > /sbin/route delete -net 128.0.0.0 10.20.162.1 128.0.0.0 . 2019.08.18 13:24:10 - OpenVPN > delete net 128.0.0.0: gateway 10.20.162.1 . 2019.08.18 13:24:10 - OpenVPN > delete_route_ipv6(::/3) . 2019.08.18 13:24:10 - OpenVPN > /sbin/route delete -inet6 :: -prefixlen 3 -iface utun1 . 2019.08.18 13:24:10 - OpenVPN > delete net ::: gateway utun1 . 2019.08.18 13:24:10 - OpenVPN > delete_route_ipv6(2000::/4) . 2019.08.18 13:24:10 - OpenVPN > /sbin/route delete -inet6 2000:: -prefixlen 4 -iface utun1 . 2019.08.18 13:24:10 - OpenVPN > delete net 2000::: gateway utun1 . 2019.08.18 13:24:10 - OpenVPN > delete_route_ipv6(3000::/4) . 2019.08.18 13:24:10 - OpenVPN > /sbin/route delete -inet6 3000:: -prefixlen 4 -iface utun1 . 2019.08.18 13:24:10 - OpenVPN > delete net 3000::: gateway utun1 . 2019.08.18 13:24:10 - OpenVPN > delete_route_ipv6(fc00::/7) . 2019.08.18 13:24:10 - OpenVPN > /sbin/route delete -inet6 fc00:: -prefixlen 7 -iface utun1 . 2019.08.18 13:24:10 - OpenVPN > delete net fc00::: gateway utun1 . 2019.08.18 13:24:10 - OpenVPN > Closing TUN/TAP interface . 2019.08.18 13:24:10 - OpenVPN > /sbin/route delete -inet6 fde6:7a:7d20:10a2::106e . 2019.08.18 13:24:10 - OpenVPN > delete host fde6:7a:7d20:10a2::106e . 2019.08.18 13:24:10 - OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting . 2019.08.18 13:24:10 - Connection terminated. . 2019.08.18 13:24:10 - DNS of a network adapter restored to original settings (Wi-Fi, to Automatic) . 2019.08.18 13:24:10 - DNS of a network adapter restored to original settings (Bluetooth PAN, to Automatic) . 2019.08.18 13:24:10 - DNS of a network adapter restored to original settings (Thunderbolt Bridge, to Automatic) I 2019.08.18 13:24:11 - Cancel requested. ! 2019.08.18 13:24:11 - Session terminated. Edited ... by giganerd Applied LOG formatting to logs Quote Share this post Link to post
airveeper 0 Posted ... Getting same curl: (60) SSL certificate problem: certificate has expired error causing eddie to not connect Quote Share this post Link to post
pim6128 0 Posted ... (edited) I have the same problem: . 2019.08.18 05:21:41 - Flushing DNS I 2019.08.18 05:21:45 - Checking route IPv4 . 2019.08.18 05:21:45 - curl: (60) SSL certificate problem: certificate has expired . 2019.08.18 05:21:45 - More details here: https://curl.haxx.se/docs/sslcerts.html . 2019.08.18 05:21:45 - curl performs SSL certificate verification by default, using a "bundle" . 2019.08.18 05:21:45 - of Certificate Authority (CA) public keys (CA certs). If the default . 2019.08.18 05:21:45 - bundle file isn't adequate, you can specify an alternate file . 2019.08.18 05:21:45 - using the --cacert option. . 2019.08.18 05:21:45 - If this HTTPS server uses a certificate signed by a CA represented in . 2019.08.18 05:21:45 - the bundle, the certificate verification probably failed due to a . 2019.08.18 05:21:45 - problem with the certificate (it might be expired, or the name might . 2019.08.18 05:21:45 - not match the domain name in the URL). . 2019.08.18 05:21:45 - If you'd like to turn off curl's verification of the certificate, use . 2019.08.18 05:21:45 - the -k (or --insecure) option. . 2019.08.18 05:21:45 - HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure. . 2019.08.18 05:21:45 - Checking route (2° try) . 2019.08.18 05:21:46 - curl: (60) SSL certificate problem: certificate has expired . 2019.08.18 05:21:46 - More details here: https://curl.haxx.se/docs/sslcerts.html . 2019.08.18 05:21:46 - curl performs SSL certificate verification by default, using a "bundle" . 2019.08.18 05:21:46 - of Certificate Authority (CA) public keys (CA certs). If the default . 2019.08.18 05:21:46 - bundle file isn't adequate, you can specify an alternate file . 2019.08.18 05:21:46 - using the --cacert option. . 2019.08.18 05:21:46 - If this HTTPS server uses a certificate signed by a CA represented in . 2019.08.18 05:21:46 - the bundle, the certificate verification probably failed due to a . 2019.08.18 05:21:46 - problem with the certificate (it might be expired, or the name might . 2019.08.18 05:21:46 - not match the domain name in the URL). . 2019.08.18 05:21:46 - If you'd like to turn off curl's verification of the certificate, use . 2019.08.18 05:21:46 - the -k (or --insecure) option. . 2019.08.18 05:21:46 - HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure. . 2019.08.18 05:21:46 - Checking route (3° try) . 2019.08.18 05:21:49 - curl: (60) SSL certificate problem: certificate has expired . 2019.08.18 05:21:49 - More details here: https://curl.haxx.se/docs/sslcerts.html . 2019.08.18 05:21:49 - curl performs SSL certificate verification by default, using a "bundle" . 2019.08.18 05:21:49 - of Certificate Authority (CA) public keys (CA certs). If the default . 2019.08.18 05:21:49 - bundle file isn't adequate, you can specify an alternate file . 2019.08.18 05:21:49 - using the --cacert option. . 2019.08.18 05:21:49 - If this HTTPS server uses a certificate signed by a CA represented in . 2019.08.18 05:21:49 - the bundle, the certificate verification probably failed due to a . 2019.08.18 05:21:49 - problem with the certificate (it might be expired, or the name might . 2019.08.18 05:21:49 - not match the domain name in the URL). . 2019.08.18 05:21:49 - If you'd like to turn off curl's verification of the certificate, use . 2019.08.18 05:21:49 - the -k (or --insecure) option. . 2019.08.18 05:21:49 - HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure. E 2019.08.18 05:21:49 - Checking route IPv4 failed. I don't know if it's relevant but yesterday Microsoft decided to update my WIndows 10.. Current version is 1803 build 17134.950 Any ideas? Thanks! Edited ... by giganerd Apply LOG formatting to logs Quote Share this post Link to post
raksiam 0 Posted ... appears to be a widespread issue. I am using the Linux version Quote Share this post Link to post
romaninetkodi 0 Posted ... (edited) . 2019.08.17 22:30:14 - curl: (60) SSL certificate problem: certificate has expired . 2019.08.17 22:30:14 - More details here: https://curl.haxx.se/docs/sslcerts.html . 2019.08.17 22:30:14 - curl performs SSL certificate verification by default, using a "bundle" . 2019.08.17 22:30:14 - of Certificate Authority (CA) public keys (CA certs). If the default . 2019.08.17 22:30:14 - bundle file isn't adequate, you can specify an alternate file . 2019.08.17 22:30:14 - using the --cacert option. . 2019.08.17 22:30:14 - If this HTTPS server uses a certificate signed by a CA represented in . 2019.08.17 22:30:14 - the bundle, the certificate verification probably failed due to a . 2019.08.17 22:30:14 - problem with the certificate (it might be expired, or the name might . 2019.08.17 22:30:14 - not match the domain name in the URL). . 2019.08.17 22:30:14 - If you'd like to turn off curl's verification of the certificate, use . 2019.08.17 22:30:14 - the -k (or --insecure) option. . 2019.08.17 22:30:14 - HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure. Edited ... by giganerd LOG Quote Share this post Link to post
Pengxiao 0 Posted ... Not only mentioned issues, but also can't generate or renew key Quote Share this post Link to post
ps73 4 Posted ... Root cause of this issue appears to be an expired certificate. If you reset your system time to yesterday (I went back a week, so that my day of week will still be correct) or earlier, then I believe you should be able to connect. It works for me. And while I do work in support, I do not work for AirVPN support, so do not take this as an official answer from them. p Quote Share this post Link to post
kwolf 2 Posted ... I'm glad to see it's a widespread problem... more likely to get fixed correctly. A workaround for Mac (and probably Linux though not tested) is to add a ~/.curlrc file with a single line: --insecure -k Quote Share this post Link to post
tanujjane 0 Posted ... Facing the same issue curl: (60) SSL certificate problem: certificate has expired Quote Share this post Link to post
ps73 4 Posted ... Just now, tanujjane said: Facing the same issue curl: (60) SSL certificate problem: certificate has expired Just now, BNDKTQU said: Also broken here Did you try and set the date back? Another thread exists and several have reported success with that work around. Quote Share this post Link to post
tanujjane 0 Posted ... 15 minutes ago, ps73 said: Did you try and set the date back? Another thread exists and several have reported success with that work around. Yes I did, and it working. But its not solution every time you have to reset the date and connect. Quote Share this post Link to post
ps73 4 Posted ... 2 hours ago, tanujjane said: Yes I did, and it working. But its not solution every time you have to reset the date and connect. I agree, and I found a better solution based on this: 3 hours ago, kwolf said: ...A workaround for Mac (and probably Linux though not tested) is to add a ~/.curlrc file with a single line: --insecure -k So for Windows, the default config file is named: _curlrc and it can be in a number of places (see https://ec.haxx.se/cmdline-configfile.html) But a quick and easy way to correct this without needing to do anything with admin rights is to open a command prompt and execute this command: echo --insecure> %APPDATA%\_curlrc Please note that you cannot have (based on my testing) a space before the '>' symbol. just copy and paste that into a command prompt (windows key, release windows key, type 'cmd', hit enter) and it will create a default config file for curl. If you want to see exactly where it created the file, you can use this command: dir %APPDATA%\_curlrc If/When someone tries this, please let me know how it works. Quote Share this post Link to post
tanujjane 0 Posted ... 1 minute ago, ps73 said: I agree, and I found a better solution cased on this: So for Windows, the default config file is named: _curlrc and it can be in a number of places (see https://ec.haxx.se/cmdline-configfile.html) But a quick and easy way to correct this without needing to do anything with admin rights is to open a command prompt and execute this command: echo --insecure> %APPDATA%\_curlrc Please note that you cannot have (based on my testing) a space before the '>' symbol. just copy and paste that into a command prompt (windows key, release windows key, type 'cmd', hit enter) and it will create a default config file for curl. If you want to see exactly where it created the file, you can use this command: dir %APPDATA%\_curlrc If/When someone tries this, please let me know how it works. I am using MAC Quote Share this post Link to post
colorman 26 Posted ... same problem on openSUSE Linux with 2.13.6 😩 and 2.17.2 to. On linux have a network lock now 😡 (solved) Quote Share this post Link to post
monstrocity 31 Posted ... 2.17.2 beta has the same issue. Set your system clock back or try @Slackjawed Cletus' suggestion from another thread: Under the "DNS" settings tab, deselect "Check AirVPN DNS", then go to the "Advanced" tab and deselect "Check if the Tunnel Works". Quote Share this post Link to post
LionOfOrange 0 Posted ... MacOS. Same problem. Reinstalled Eddie to no effect. Certificate problem. Quote Share this post Link to post
ps73 4 Posted ... 1 hour ago, tanujjane said: 1 hour ago, ps73 said: I agree, and I found a better solution cased on this: So for Windows, the default config file is named: _curlrc and it can be in a number of places (see https://ec.haxx.se/cmdline-configfile.html) But a quick and easy way to correct this without needing to do anything with admin rights is to open a command prompt and execute this command: echo --insecure> %APPDATA%\_curlrc Please note that you cannot have (based on my testing) a space before the '>' symbol. just copy and paste that into a command prompt (windows key, release windows key, type 'cmd', hit enter) and it will create a default config file for curl. If you want to see exactly where it created the file, you can use this command: dir %APPDATA%\_curlrc If/When someone tries this, please let me know how it works. I am using MAC On a Mac, you can use the original fix that kwolf described. Quote Share this post Link to post
ps73 4 Posted ... 10 minutes ago, LionOfOrange said: MacOS. Same problem. Reinstalled Eddie to no effect. Certificate problem. You can use the fix that kwolf described here: 3 hours ago, kwolf said: I'm glad to see it's a widespread problem... more likely to get fixed correctly. A workaround for Mac (and probably Linux though not tested) is to add a ~/.curlrc file with a single line: --insecure -k Quote Share this post Link to post
toporvpn 0 Posted ... At my end it says something about ipv4, i can't connect, it keeps disconnecting. I have never had this problem.... Probably its related to the same problem that everyone is having? Quote Share this post Link to post
LionOfOrange 0 Posted ... 1 minute ago, ps73 said: You can use the fix that kwolf described here: I can imagine that it works but imho it defeats the purpose of a VPN. As an alternative I have installed Tunnelblick; this works fine. Quote Share this post Link to post
gizurr 1 Posted ... This seems to only affect Eddie. Configuration files are probably outdated Quote Share this post Link to post
ps73 4 Posted ... 26 minutes ago, LionOfOrange said: I can imagine that it works but imho it defeats the purpose of a VPN. As an alternative I have installed Tunnelblick; this works fine. How does it defeat the purpose? The server that they are using for testing to see if the tunnel is up has an expired certificate. Telling the one utility that they are using to test the connection to accept expired or otherwise problematic certs only affects the single test connection. If you are doing this on Linux or Mac, it is a global setting for that user, but you can modify it, start the VPN and then revert the change. On windows, if you go and find the AirVPN executable, there is a curl executable in the same folder. If you create the _curlrc file in the same place, then it only applies when that version of curl is invoked. I didn't mention it in my post as it requires you to assume admin rights. Otherwise, you can create the file in the appdata folder and then delete it once you are connected in a manner similar to Mac and Linux. Quote Share this post Link to post
Staff 9973 Posted ... Hello, we have experienced a problem with VPN server LetsEncrypt certificates deployment. The system procedure got stuck and failed to deploy updated certificates. In turn, such a failure caused "route check" failures on Eddie desktop editions, and ONLY on them, due to expired certificates verified by cURL during the route check phase. The problem has been affecting a wide amount of VPN servers for about 8 hours and has been resolved completely now. We deeply apologize for any inconvenience. Kind regards 1 alswell reacted to this Quote Share this post Link to post
tanujjane 0 Posted ... 12 minutes ago, Staff said: Hello, we have experienced a problem with VPN server LetsEncrypt certificates deployment. The system procedure got stuck and failed to deploy updated certificates. In turn, such a failure caused "route check" failures on Eddie desktop editions, and ONLY on them, due to expired certificates verified by cURL during the route check phase. The problem has been affecting a wide amount of VPN servers for about 8 hours and has been resolved completely now. We deeply apologize for any inconvenience. Kind regards Now I am unable to login on Android Eddie. Please check Quote Share this post Link to post
Not connected, Your IP: 3.139.87.113
Online: 25171 users - 300752 Mbit/s total BW