Zabbix 3.0 Manualcomponents are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). 451 • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error0 码力 | 1074 页 | 12.04 MB | 1 年前3- Zabbix 3.2 Manualcomponents are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error0 码力 | 1012 页 | 12.11 MB | 1 年前3
- Zabbix 3.4 Manualcomponents are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error0 码力 | 1136 页 | 15.03 MB | 1 年前3
- Zabbix 4.0 Manualcomponents are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error0 码力 | 1365 页 | 16.69 MB | 1 年前3
- Zabbix 4.2 Manualcomponents are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error0 码力 | 1270 页 | 15.64 MB | 1 年前3
- Zabbix 4.4 Manualcomponents are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: 672 failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned0 码力 | 1393 页 | 16.55 MB | 1 年前3
- Zabbix 4.4 中文手册components are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error0 码力 | 1850 页 | 13.52 MB | 1 年前3
- Zabbix 5.2 Manualcomponents are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error0 码力 | 1725 页 | 11.53 MB | 1 年前3
- Zabbix 4.2 中文手册components are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error0 码力 | 1869 页 | 13.68 MB | 1 年前3
- Zabbix 5.4 中文手册components are compiled with (it may or may not work, Zabbix may refuse to accept such certificates from peers). • Extended Key Usage extension. If used then generally both clientAuth (TLS WWW client authentication) its CRL is not included in TLSCRLFile In TLS server log in case of mbed TLS (PolarSSL) and OpenSSL peers: failed to accept an incoming connection: from 127.0.0.1: TLS handshake with 127.0.0.1 returned error0 码力 | 2339 页 | 19.57 MB | 1 年前3
共 18 条
- 1
- 2