curl certificate error in Eddie while trying to connect to AirVPN

[Barbatos 1]

Just now, Zultan said:

I''ve got same problem

Try Lalande , its working for now

[ps73 4]

29 minutes ago, Anonymousvpnuser1 said:

Wouldn't that mean that our local DNS would be open to be seen? I am not all that educated on this subject.

I'm not really enjoying the setting the clock back fix either. Some things are not working with my clock set back. Tradingview isnt working, google isnt working etc.

I don't think that is what it means.  It sounds to me like it is just trying to check to see if the tunnel is working before it starts using it.  But the server that they are connecting to for testing has a bad (expired) cert.  That means that the check is failing, even though the tunnel is up.  This is probably the best work around so far as it is done completely in the application settings.  

[nestegg101 3]

Just to confirm. This has been happening since around 7 hours ago. Only VPN access through Eddie is affected.

[DigitalHoarder 0]

Add me to the list now too 😕

[weeezy 0]

Can't connect either

[jeuia3e9x74uxu6wk0r2u9kdos 30]

Hey three-letters-agency! , yes I'm talking with you BBC, FBI, NFL, DNA, WWW, BIC, FOX, USB could you stop messing with AIRvpn please? Thanks!

/s

[RobertM 0]

Same issue here. No problems when connecting on my Samsung.

[mecdeva 11]

56 minutes ago, pwolverine said:

From the other thread Slackjawed Cletus posted:

This worked for me, so I put my clock back to normal.

I didn't see Slackjawed Cletus's post... but thanks for copying his solution here. It worked for me without changing any clock settings or anything. And it will be easy to reverse once AIRVPN fixes the issue. 🙂

[WJJ 0]

Same problem. Quite annoying.

[ShadeVPN 0]

I have the same problem, but with Windows 7 only.
Windows 10 and my android phone worked as well

[jeberlo 2]

Same problem in my Linux Mint. However I can bypass using network manager - openvpn directly.

Regards.

[dschubba 0]

I confirm the issue. Setting the date to yesterday (august 17th) in Windows 7 is working. Waiting for a permanent fix.

[kezzas1 0]

I also have the same problem. 😕 no idea how to fix it at the moment

[messy 0]

I was connected to my Dutch server, I was logged out and now I can only log in lalande brazil why this? Any other server that I enter is logged out, and I noticed that this server always has about 10 users and got over 50 users is a bug? or was hacked? Why is lalande the only server running now? this server looks good but why can I just log in?

[YesGem 2]

Quote

From the other thread Slackjawed Cletus posted:
 

Quote

Under the "DNS" settings tab, deselect "Check AirVPN DNS", then go to the "Advanced" tab and deselect "Check if the Tunnel Works".  Worked for me on v2.17.2.  Just a very temporary fix.

This has worked for me as well with the most current version.

[hyperfixerad 0]

Hi,

So as many it seems has experienced, I too get stuck trying to connect, having the client check routes, then immediately disconnect. 

I have tried most suggested fixes, turning off DNS, turning off Network lock, restarting the client, computer, and reinstalling the client. 

This seems to be where it goes wrong: 

I 2019.08.18 10:13:41 - Session starting.
I 2019.08.18 10:13:41 - Checking authorization ...
! 2019.08.18 10:13:42 - Connecting to Tarazed (Netherlands, Alblasserdam)
. 2019.08.18 10:13:42 - 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 10:13:42 - OpenVPN > library versions: OpenSSL 1.1.0h  27 Mar 2018, LZO 2.10
. 2019.08.18 10:13:42 - Connection to OpenVPN Management Interface
. 2019.08.18 10:13:42 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2019.08.18 10:13:42 - OpenVPN > Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
. 2019.08.18 10:13:42 - OpenVPN > Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
. 2019.08.18 10:13:42 - OpenVPN > Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
. 2019.08.18 10:13:42 - OpenVPN > Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
. 2019.08.18 10:13:42 - OpenVPN > TCP/UDP: Preserving recently used remote address: [AF_INET]213.152.161.135:443
. 2019.08.18 10:13:42 - OpenVPN > Socket Buffers: R=[786896->262144] S=[9216->262144]
. 2019.08.18 10:13:42 - OpenVPN > UDP link local: (not bound)
. 2019.08.18 10:13:42 - OpenVPN > UDP link remote: [AF_INET]213.152.161.135:443
. 2019.08.18 10:13:42 - OpenVPN > TLS: Initial packet from [AF_INET]213.152.161.135:443, sid=54826a68 7c286295
. 2019.08.18 10:13:42 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100
. 2019.08.18 10:13:42 - 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 10:13:42 - OpenVPN > VERIFY KU OK
. 2019.08.18 10:13:42 - OpenVPN > Validating certificate extended key usage
. 2019.08.18 10:13:42 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2019.08.18 10:13:42 - OpenVPN > VERIFY EKU OK
. 2019.08.18 10:13:42 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Tarazed, emailAddress=info@airvpn.org
. 2019.08.18 10:13:42 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
. 2019.08.18 10:13:42 - OpenVPN > [Tarazed] Peer Connection Initiated with [AF_INET]213.152.161.135:443
. 2019.08.18 10:13:43 - OpenVPN > SENT CONTROL [Tarazed]: 'PUSH_REQUEST' (status=1)
. 2019.08.18 10:13:43 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.31.46.1,dhcp-option DNS6 fde6:7a:7d20:1b2e::1,tun-ipv6,route-gateway 10.31.46.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:1b2e::1025/64 fde6:7a:7d20:1b2e::1,ifconfig 10.31.46.39 255.255.255.0,peer-id 0,cipher AES-256-GCM'
. 2019.08.18 10:13:43 - OpenVPN > Pushed option removed by filter: 'redirect-gateway ipv6 def1 bypass-dhcp'
. 2019.08.18 10:13:43 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2019.08.18 10:13:43 - OpenVPN > OPTIONS IMPORT: compression parms modified
. 2019.08.18 10:13:43 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified
. 2019.08.18 10:13:43 - OpenVPN > OPTIONS IMPORT: route-related options modified
. 2019.08.18 10:13:43 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
. 2019.08.18 10:13:43 - OpenVPN > OPTIONS IMPORT: peer-id set
. 2019.08.18 10:13:43 - OpenVPN > OPTIONS IMPORT: adjusting link_mtu to 1625
. 2019.08.18 10:13:43 - OpenVPN > OPTIONS IMPORT: data channel crypto options modified
. 2019.08.18 10:13:43 - OpenVPN > Data Channel: using negotiated cipher 'AES-256-GCM'
. 2019.08.18 10:13:43 - OpenVPN > Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
. 2019.08.18 10:13:43 - OpenVPN > Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
. 2019.08.18 10:13:43 - OpenVPN > ROUTE_GATEWAY 192.168.0.1/255.255.255.0 IFACE=en0 HWADDR=4c:32:75:98:64:17
. 2019.08.18 10:13:43 - OpenVPN > GDG6: remote_host_ipv6=n/a
. 2019.08.18 10:13:43 - OpenVPN > GDG6: problem writing to routing socket
. 2019.08.18 10:13:43 - OpenVPN > ROUTE6: default_gateway=UNDEF
. 2019.08.18 10:13:43 - OpenVPN > Opening utun (connect(AF_SYS_CONTROL)): Resource busy (errno=16)
. 2019.08.18 10:13:43 - OpenVPN > Opened utun device utun1
. 2019.08.18 10:13:43 - OpenVPN > do_ifconfig, tt->did_ifconfig_ipv6_setup=1
. 2019.08.18 10:13:43 - OpenVPN > /sbin/ifconfig utun1 delete
. 2019.08.18 10:13:43 - OpenVPN > ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address
. 2019.08.18 10:13:43 - OpenVPN > NOTE: Tried to delete pre-existing tun/tap instance -- No Problem if failure
. 2019.08.18 10:13:43 - OpenVPN > /sbin/ifconfig utun1 10.31.46.39 10.31.46.39 netmask 255.255.255.0 mtu 1500 up
. 2019.08.18 10:13:43 - OpenVPN > /sbin/route add -net 10.31.46.0 10.31.46.39 255.255.255.0
. 2019.08.18 10:13:43 - OpenVPN > add net 10.31.46.0: gateway 10.31.46.39
. 2019.08.18 10:13:43 - OpenVPN > /sbin/ifconfig utun1 inet6 fde6:7a:7d20:1b2e::1025/64
. 2019.08.18 10:13:43 - OpenVPN > add_route_ipv6(fde6:7a:7d20:1b2e::/64 -> fde6:7a:7d20:1b2e::1025 metric 0) dev utun1
. 2019.08.18 10:13:43 - OpenVPN > /sbin/route add -inet6 fde6:7a:7d20:1b2e:: -prefixlen 64 -iface utun1
. 2019.08.18 10:13:43 - OpenVPN > route: writing to routing socket: File exists
. 2019.08.18 10:13:43 - OpenVPN > add net fde6:7a:7d20:1b2e::: gateway utun1: File exists
. 2019.08.18 10:13:43 - OpenVPN > /sbin/route add -net 213.152.161.135 192.168.0.1 255.255.255.255
. 2019.08.18 10:13:43 - OpenVPN > add net 213.152.161.135: gateway 192.168.0.1
. 2019.08.18 10:13:43 - OpenVPN > /sbin/route add -net 0.0.0.0 10.31.46.1 128.0.0.0
. 2019.08.18 10:13:43 - OpenVPN > add net 0.0.0.0: gateway 10.31.46.1
. 2019.08.18 10:13:43 - OpenVPN > /sbin/route add -net 128.0.0.0 10.31.46.1 128.0.0.0
. 2019.08.18 10:13:43 - OpenVPN > add net 128.0.0.0: gateway 10.31.46.1
. 2019.08.18 10:13:43 - OpenVPN > add_route_ipv6(::/3 -> fde6:7a:7d20:1b2e::1 metric -1) dev utun1
. 2019.08.18 10:13:43 - OpenVPN > /sbin/route add -inet6 :: -prefixlen 3 -iface utun1
. 2019.08.18 10:13:43 - OpenVPN > add net ::: gateway utun1
. 2019.08.18 10:13:43 - OpenVPN > add_route_ipv6(2000::/4 -> fde6:7a:7d20:1b2e::1 metric -1) dev utun1
. 2019.08.18 10:13:43 - OpenVPN > /sbin/route add -inet6 2000:: -prefixlen 4 -iface utun1
. 2019.08.18 10:13:43 - OpenVPN > add net 2000::: gateway utun1
. 2019.08.18 10:13:43 - OpenVPN > add_route_ipv6(3000::/4 -> fde6:7a:7d20:1b2e::1 metric -1) dev utun1
. 2019.08.18 10:13:43 - OpenVPN > /sbin/route add -inet6 3000:: -prefixlen 4 -iface utun1
. 2019.08.18 10:13:43 - OpenVPN > add net 3000::: gateway utun1
. 2019.08.18 10:13:43 - OpenVPN > add_route_ipv6(fc00::/7 -> fde6:7a:7d20:1b2e::1 metric -1) dev utun1
. 2019.08.18 10:13:43 - OpenVPN > /sbin/route add -inet6 fc00:: -prefixlen 7 -iface utun1
. 2019.08.18 10:13:43 - OpenVPN > add net fc00::: gateway utun1
. 2019.08.18 10:13:44 - DNS of a network adapter forced (ThinkPad USB 3.0 Pro Dock, from Automatic to 10.31.46.1, fde6:7a:7d20:1b2e::1)
. 2019.08.18 10:13:44 - DNS of a network adapter forced (iPad USB, from Automatic to 10.31.46.1, fde6:7a:7d20:1b2e::1)
. 2019.08.18 10:13:44 - DNS of a network adapter forced (Wi-Fi, from Automatic to 10.31.46.1, fde6:7a:7d20:1b2e::1)
. 2019.08.18 10:13:44 - DNS of a network adapter forced (iPhone USB, from Automatic to 10.31.46.1, fde6:7a:7d20:1b2e::1)
. 2019.08.18 10:13:44 - DNS of a network adapter forced (Bluetooth PAN, from Automatic to 10.31.46.1, fde6:7a:7d20:1b2e::1)
. 2019.08.18 10:13:44 - DNS of a network adapter forced (Thunderbolt Bridge, from Automatic to 10.31.46.1, fde6:7a:7d20:1b2e::1)
. 2019.08.18 10:13:44 - Routes, added a new route, 213.152.161.133 for gateway 10.31.46.1
. 2019.08.18 10:13:44 - Routes, added a new route, 2a00:1678:2470:4:6cea:a07e:e6f3:db56 for gateway fde6:7a:7d20:1b2e::1
. 2019.08.18 10:13:44 - Flushing DNS
I 2019.08.18 10:13:45 - Checking route IPv4
. 2019.08.18 10:13:45 - curl: (60) SSL certificate problem: certificate has expired
. 2019.08.18 10:13:45 -     More details here: https://curl.haxx.se/docs/sslcerts.html
. 2019.08.18 10:13:45 -     curl performs SSL certificate verification by default, using a "bundle"
. 2019.08.18 10:13:45 -     of Certificate Authority (CA) public keys (CA certs). If the default
. 2019.08.18 10:13:45 -     bundle file isn't adequate, you can specify an alternate file
. 2019.08.18 10:13:45 -     using the --cacert option.
. 2019.08.18 10:13:45 -     If this HTTPS server uses a certificate signed by a CA represented in
. 2019.08.18 10:13:45 -     the bundle, the certificate verification probably failed due to a
. 2019.08.18 10:13:45 -     problem with the certificate (it might be expired, or the name might
. 2019.08.18 10:13:45 -     not match the domain name in the URL).
. 2019.08.18 10:13:45 -     If you'd like to turn off curl's verification of the certificate, use
. 2019.08.18 10:13:45 -     the -k (or --insecure) option.
. 2019.08.18 10:13:45 -     HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure.
. 2019.08.18 10:13:45 - Checking route (2° try)
. 2019.08.18 10:13:46 - curl: (60) SSL certificate problem: certificate has expired
. 2019.08.18 10:13:46 -     More details here: https://curl.haxx.se/docs/sslcerts.html
. 2019.08.18 10:13:46 -     curl performs SSL certificate verification by default, using a "bundle"
. 2019.08.18 10:13:46 -     of Certificate Authority (CA) public keys (CA certs). If the default
. 2019.08.18 10:13:46 -     bundle file isn't adequate, you can specify an alternate file
. 2019.08.18 10:13:46 -     using the --cacert option.
. 2019.08.18 10:13:46 -     If this HTTPS server uses a certificate signed by a CA represented in
. 2019.08.18 10:13:46 -     the bundle, the certificate verification probably failed due to a
. 2019.08.18 10:13:46 -     problem with the certificate (it might be expired, or the name might
. 2019.08.18 10:13:46 -     not match the domain name in the URL).
. 2019.08.18 10:13:46 -     If you'd like to turn off curl's verification of the certificate, use
. 2019.08.18 10:13:46 -     the -k (or --insecure) option.
. 2019.08.18 10:13:46 -     HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure.
. 2019.08.18 10:13:46 - Checking route (3° try)
. 2019.08.18 10:13:48 - curl: (60) SSL certificate problem: certificate has expired
. 2019.08.18 10:13:48 -     More details here: https://curl.haxx.se/docs/sslcerts.html
. 2019.08.18 10:13:48 -     curl performs SSL certificate verification by default, using a "bundle"
. 2019.08.18 10:13:48 -     of Certificate Authority (CA) public keys (CA certs). If the default
. 2019.08.18 10:13:48 -     bundle file isn't adequate, you can specify an alternate file
. 2019.08.18 10:13:48 -     using the --cacert option.
. 2019.08.18 10:13:48 -     If this HTTPS server uses a certificate signed by a CA represented in
. 2019.08.18 10:13:48 -     the bundle, the certificate verification probably failed due to a
. 2019.08.18 10:13:48 -     problem with the certificate (it might be expired, or the name might
. 2019.08.18 10:13:48 -     not match the domain name in the URL).
. 2019.08.18 10:13:48 -     If you'd like to turn off curl's verification of the certificate, use
. 2019.08.18 10:13:48 -     the -k (or --insecure) option.
. 2019.08.18 10:13:48 -     HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure.
E 2019.08.18 10:13:48 - Checking route IPv4 failed.
. 2019.08.18 10:13:48 - OpenVPN > Initialization Sequence Completed
! 2019.08.18 10:13:48 - Disconnecting
. 2019.08.18 10:13:48 - Routes, removed a route previously added, 213.152.161.133 for gateway 10.31.46.1
. 2019.08.18 10:13:48 - Routes, removed a route previously added, 2a00:1678:2470:4:6cea:a07e:e6f3:db56 for gateway fde6:7a:7d20:1b2e::1
. 2019.08.18 10:13:48 - Sending management termination signal
. 2019.08.18 10:13:48 - Management - Send 'signal SIGTERM'
. 2019.08.18 10:13:48 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM'
. 2019.08.18 10:13:48 - OpenVPN > SIGTERM received, sending exit notification to peer
. 2019.08.18 10:13:54 - OpenVPN > /sbin/route delete -net 213.152.161.135 192.168.0.1 255.255.255.255
. 2019.08.18 10:13:54 - OpenVPN > delete net 213.152.161.135: gateway 192.168.0.1
. 2019.08.18 10:13:54 - OpenVPN > /sbin/route delete -net 0.0.0.0 10.31.46.1 128.0.0.0
. 2019.08.18 10:13:54 - OpenVPN > delete net 0.0.0.0: gateway 10.31.46.1
. 2019.08.18 10:13:54 - OpenVPN > /sbin/route delete -net 128.0.0.0 10.31.46.1 128.0.0.0
. 2019.08.18 10:13:54 - OpenVPN > delete net 128.0.0.0: gateway 10.31.46.1
. 2019.08.18 10:13:54 - OpenVPN > delete_route_ipv6(::/3)
. 2019.08.18 10:13:54 - OpenVPN > /sbin/route delete -inet6 :: -prefixlen 3 -iface utun1
. 2019.08.18 10:13:54 - OpenVPN > delete net ::: gateway utun1
. 2019.08.18 10:13:54 - OpenVPN > delete_route_ipv6(2000::/4)
. 2019.08.18 10:13:54 - OpenVPN > /sbin/route delete -inet6 2000:: -prefixlen 4 -iface utun1
. 2019.08.18 10:13:54 - OpenVPN > delete net 2000::: gateway utun1
. 2019.08.18 10:13:54 - OpenVPN > delete_route_ipv6(3000::/4)
. 2019.08.18 10:13:54 - OpenVPN > /sbin/route delete -inet6 3000:: -prefixlen 4 -iface utun1
. 2019.08.18 10:13:54 - OpenVPN > delete net 3000::: gateway utun1
. 2019.08.18 10:13:54 - OpenVPN > delete_route_ipv6(fc00::/7)
. 2019.08.18 10:13:54 - OpenVPN > /sbin/route delete -inet6 fc00:: -prefixlen 7 -iface utun1
. 2019.08.18 10:13:54 - OpenVPN > delete net fc00::: gateway utun1
. 2019.08.18 10:13:54 - OpenVPN > Closing TUN/TAP interface
. 2019.08.18 10:13:54 - OpenVPN > /sbin/route delete -inet6 fde6:7a:7d20:1b2e::1025
. 2019.08.18 10:13:54 - OpenVPN > delete host fde6:7a:7d20:1b2e::1025
. 2019.08.18 10:13:54 - OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting
. 2019.08.18 10:13:54 - Connection terminated.
. 2019.08.18 10:13:54 - DNS of a network adapter restored to original settings (ThinkPad USB 3.0 Pro Dock, to Automatic)
. 2019.08.18 10:13:54 - DNS of a network adapter restored to original settings (iPad USB, to Automatic)
. 2019.08.18 10:13:54 - DNS of a network adapter restored to original settings (Wi-Fi, to Automatic)
. 2019.08.18 10:13:54 - DNS of a network adapter restored to original settings (iPhone USB, to Automatic)
. 2019.08.18 10:13:54 - DNS of a network adapter restored to original settings (Bluetooth PAN, to Automatic)
. 2019.08.18 10:13:54 - DNS of a network adapter restored to original settings (Thunderbolt Bridge, to Automatic)
I 2019.08.18 10:13:56 - Cancel requested.
! 2019.08.18 10:13:56 - Session terminated.

I started looking through the suggested link regarding the expired certificates (https://curl.haxx.se/docs/sslcerts.html) but I am not sure that's the right path to fix the issue. 

Any ideas? 

Edited ... by giganerd
Apply LOG formatting to logs

[giovannatutty 0]

multiple servers are going down, what's going on?

[nestegg101 3]

Here are 2 temporary solutions which work for me:

1. Set your system clock back. The cert expired less than 24 hours ago, so set it back at least a couple of days before that (hopefully Support can get this fixed in the meantime).

2. Generate a config file for Curl.exe and use the --insecure option to bypass the SSL warning. If you are running Windows, the Curl config file is named _curlrc and it is placed in your HOME directory or your <USER PROFILE>\Application Data directory. You can also put it in the same location with Curl.exe. This will be your Eddie program directory. Admin rights will be needed. I did this.

Use your text editor to save a text file with "insecure" (without the "") on the first line and save it with the name _curlrc and put it in any one of the above mentioned locations.

That's all it takes. YMMV.

Update: It's been reported that unchecking "Check if the tunnel works" under Eddie Preferences > Advanced does the trick as well.



 

[ShadeVPN 0]

6 hours ago, TItQCNGib0f said:

So the issue is with Eddie.

Install OpenVPN:
https://openvpn.net/community-downloads/

Use the AirVPN config generator to create config files and save those under program files/OpenVPN/config.  

After launching OpenVPN you will be able to right click and connect to the server of your choice.  

I tried it. It connects with config file, but internet doesnt work. Ping and tracert - yes, but not browsers.

[cambell 17]

thanks, putting the clock back is working.

[MarcoH 0]

Same problem here: "flushing DNS", "Connecting to Server", and "Disconnecting".
We have 2 PC's with Windows 10 and both have the same problem.
One PC has been updated yesterday, the other not.

We can connect again....., on both PC's 👍

[ghostp 5]

Hello everyone,
since years the only way for me to use air properly is connecting norway servers via SSL/443/2, because of ISP traffic shaping.
Today I can't connect to any servers with the settings above at all because of some SSL certificate problems:

"I 2019.08.18 10:52:00 - Checking route IPv4
. 2019.08.18 10:52:00 - curl: (60) SSL certificate problem: certificate has expired
. 2019.08.18 10:52:00 -     More details here: https://curl.haxx.se/docs/sslcerts.html
. 2019.08.18 10:52:00 -     curl performs SSL certificate verification by default, using a "bundle"
. 2019.08.18 10:52:00 -     of Certificate Authority (CA) public keys (CA certs). If the default
. 2019.08.18 10:52:00 -     bundle file isn't adequate, you can specify an alternate file
. 2019.08.18 10:52:00 -     using the --cacert option.
. 2019.08.18 10:52:00 -     If this HTTPS server uses a certificate signed by a CA represented in
. 2019.08.18 10:52:00 -     the bundle, the certificate verification probably failed due to a
. 2019.08.18 10:52:00 -     problem with the certificate (it might be expired, or the name might
. 2019.08.18 10:52:00 -     not match the domain name in the URL).
. 2019.08.18 10:52:00 -     If you'd like to turn off curl's verification of the certificate, use
. 2019.08.18 10:52:00 -     the -k (or --insecure) option.
. 2019.08.18 10:52:00 -     HTTPS-proxy has similar options --proxy-cacert and --proxy-insecure."

How can I solve this issue?
Thank you in advance!

[PWolverine 8]

2 hours ago, Anonymousvpnuser1 said:

Wouldn't that mean that our local DNS would be open to be seen? I am not all that educated on this subject.

I'm not really enjoying the setting the clock back fix either. Some things are not working with my clock set back. Tradingview isnt working, google isnt working etc.

I don't believe so, but i'm by no means an expert there.  

I do know that if you go to https://ipleak.net it verifies you coming out of AirVPN's server and your IP isn't local anymore.

[deltaman8 3]

Had the same issue here.
5 min ago I was able to log in successfully again..

Air seems to have fixed it! That was quick 🙂
THANK YOU VERY MUCH!

[Staff 9973]

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
AirVPN Staff