Errror SSL 5

Solved
Albert_mol
Comes here often

Errror SSL 5

Hello today all my osx recibe error SSL =5 from 11:00 GMT+1

 

Yesterday all working correctly, all have last version 1.0.98

 

Is a server error?, i test with other conectivty , and show same error

 

2019-01-18 17:25:24.883480 [0x70000a9ab000]: TunClient::connect_to_proxy() [pcc199.meraki.com:993], r < 0, ERR_get_error = 0
2019-01-18 17:25:24.883629 [0x70000a9ab000]: TunClient::connect_to_proxy() [pcc199.meraki.com:993], r < 0, errno = 32
2019-01-18 17:25:24.883684 [0x70000a9ab000]: TunClient::connect_to_proxy() [pcc199.meraki.com:993], unexpected SSL error 5 after SSL_connect() returned -1
sigpipe_handle
2019-01-18 17:26:06.532810 [0x70000a9ab000]: TunClient::connect_to_proxy() [pcc199.meraki.com:993], r < 0, ERR_get_error = 0
2019-01-18 17:26:06.532973 [0x70000a9ab000]: TunClient::connect_to_proxy() [pcc199.meraki.com:993], r < 0, errno = 32
2019-01-18 17:26:06.533021 [0x70000a9ab000]: TunClient::connect_to_proxy() [pcc199.meraki.com:993], unexpected SSL error 5 after SSL_connect() returned -1
2019-01-18 17:27:03.405934 [0x10b13c5c0]: ClientManager::check_client_pulse(): client pcc199.meraki.com:993 timed out; restarting

 

 

1 Accepted Solution
PhilipDAth
Kind of a big deal
Kind of a big deal

You need to open a ticket with support.

 

When I nmap scan node pcc198.meraki.com port 993 is open.  So I think something is wrong with node pc199.

View solution in original post

3 Replies 3
PhilipDAth
Kind of a big deal
Kind of a big deal

Is the date/time on your machines roughly correct?

Albert_mol
Comes here often

Hello

 

yes, all machines have time server.

 

And now I'm into one machine with same error into m_log, and the date and time correct.

 

2019-01-19 11:33:49.345887 [0x700005f4e000]: TunClient::main() [pcc199.meraki.com:993], starting up...

2019-01-19 11:35:10.31497 [0x700005f4e000]: TunClient::connect_to_proxy() [pcc199.meraki.com:993], r < 0, ERR_get_error = 0

sigpipe_handle

2019-01-19 11:35:10.32648 [0x700005f4e000]: TunClient::connect_to_proxy() [pcc199.meraki.com:993], r < 0, errno = 32

2019-01-19 11:35:10.32729 [0x700005f4e000]: TunClient::connect_to_proxy() [pcc199.meraki.com:993], unexpected SSL error 5 after SSL_connect() returned -1

2019-01-19 11:35:56.807704 [0x118cd25c0]: ClientManager::check_client_pulse(): client pcc199.meraki.com:993 timed out; restarting

sigusr1_handle

2019-01-19 11:35:57.910750 [0x700005f4e000]: TunClient::main() [pcc199.meraki.com:993], starting up...

 

I test NMAP and not show port 993 open

 

MBP-WS-AA03231:~ albert$ nmap pcc199.meraki.com

Starting Nmap 7.70 ( https://nmap.org ) at 2019-01-19 11:36 CET

Nmap scan report for pcc199.meraki.com (209.206.58.14)

Host is up (0.031s latency).

rDNS record for 209.206.58.14: fra167.meraki.com

Not shown: 996 filtered ports

PORT      STATE  SERVICE

80/tcp    open   http

443/tcp   open   https

60020/tcp closed unknown

60443/tcp closed unknown

PhilipDAth
Kind of a big deal
Kind of a big deal

You need to open a ticket with support.

 

When I nmap scan node pcc198.meraki.com port 993 is open.  So I think something is wrong with node pc199.

Get notified when there are additional replies to this discussion.