Following instruction on this page you can test if your network traffic can flow both ways between your host and client has support for one of the SSL/TLS versions required by our servers.
On the host that runs your service run the next command:
| Code Block |
|---|
curl -o /dev/null -s -vvv https://my.patientsknowbest.com |
Expected success output
| Code Block |
|---|
* Trying 35.246.122.93:443...
...
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
...
* Connection #0 to host my.patientsknowbest.com left intact |
...
| Panel |
|---|
| panelIconId | 1f3c1 |
|---|
| panelIcon | :checkered_flag: |
|---|
| panelIconText | 🏁 |
|---|
| bgColor | #DEEBFF |
|---|
|
NEXT: Consult documentation of your integration enginge for to see what SSL/TLS versions it supports. |
Expected failure output
| Code Block |
|---|
* Trying 35.246.122.93:443...
* Connected to my.patientsknowbest.com (35.246.122.93) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Unknown (21):
} [5 bytes data]
* TLSv1.3 (OUT), TLS alert, protocol version (582):
} [2 bytes data]
* error:0A0000BF:SSL routines::no protocols available
* Closing connection 0 |
...
| Panel |
|---|
| panelIconId | 1f3c1 |
|---|
| panelIcon | :checkered_flag: |
|---|
| panelIconText | 🏁 |
|---|
| bgColor | #DEEBFF |
|---|
|
NEXT: Consult documentation of your integration enginge for to see what SSL/TLS versions it supports. |
| Panel |
|---|
| panelIconId | atlassian-light_bulb_on |
|---|
| panelIcon | :light_bulb_on: |
|---|
| panelIconText | :light_bulb_on: |
|---|
| bgColor | #FFFAE6 |
|---|
|
TIP: This ususally indicates that client software is outdated might be outdated or missing security updates (can be OS and/or integration engine version). |
| Panel |
|---|
| panelIconId | 1f3c1 |
|---|
| panelIcon | :checkered_flag: |
|---|
| panelIconText | 🏁 |
|---|
| bgColor | #DEEBFF |
|---|
|
NEXT: See way how you can Explore ways to update your client software. |
