Jump to content
Not connected, Your IP: 3.137.170.14
Sign in to follow this  
ozon3xp

DD-WRT Open VPN error

Recommended Posts

19700101 13:48:48 Socket Buffers: R=[180224->131072] S=[180224->131072] 

19700101 13:48:48 I UDPv4 link local: [undef] 

19700101 13:48:48 I UDPv4 link remote: [AF_INET]199.241.146.178:443 

19700101 13:48:48 TLS: Initial packet from [AF_INET]199.241.146.178:443 sid=25283ed9 500a87bc 

19700101 13:48:48 N VERIFY ERROR: depth=1 error=certificate is not yet valid: C=IT ST=IT L=Perugia O=airvpn.org CN=airvpn.org CA emailAddress=info@airvpn.org 

19700101 13:48:48 N TLS_ERROR: BIO read tls_read_plaintext error: error:14090086:lib(20):func(144):reason(134) 

19700101 13:48:48 N TLS Error: TLS object -> incoming plaintext read error 

19700101 13:48:48 NOTE: --mute triggered... 

19700101 13:48:48 1 variation(s) on previous 3 message(s) suppressed by --mute 

19700101 13:48:48 I SIGUSR1[soft tls-error] received process restarting 

19700101 13:48:48 Restart pause 2 second(s) 

 

I'm getting this error as of today.

 

Thanks

Share this post


Link to post

 

19700101 13:48:48 N VERIFY ERROR: depth=1 error=certificate is not yet valid: C=IT ST=IT L=Perugia O=airvpn.org CN=airvpn.org CA emailAddress=info@airvpn.org

19700101 13:48:48 N TLS_ERROR: BIO read tls_read_plaintext error: error:14090086:lib(20):func(144):reason(134) 

I'm getting this error as of today.
 
Thanks

 

 

Hello!

 

As you can see in the log entry, you have an error caused by reason 134, preceded by an "not yet valid" which is only apparently enigmatic. This implies that your timeline is not matching with our timeline, even though the Attractor Field could be the same.

 

In our timeline, the technology you are using is not available in 1970. Our certificates began to be issued after 2010 and our whole infrastructure was born only in 2010. It is unclear how, in spite of the divergence, communications are flowing between you and us. We strongly recommend that you try to fix the divergence with the help of an NTP server for your router, before any potential paradox can cause extensive damage either in your or our observable time line, or even fall in the scope of a different Attractor Field.

 

In any case, please proceed quickly but with extreme caution.

 

Kind regards

John

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Security Check
    Play CAPTCHA Audio
    Refresh Image
Sign in to follow this  

×
×
  • Create New...