...
| Panel |
|---|
| panelIconId | atlassian-light_bulb_on |
|---|
| panelIcon | :light_bulb_on: |
|---|
| panelIconText | :light_bulb_on: |
|---|
| bgColor | #FFFAE6 |
|---|
|
TIP: You might need to change the hostname my.patientsknowbest.com depending on what API you are trying to reach. For exact To get the relevant hostname consult our PKB API Network Connectivity page. |
...
| Tip |
|---|
Presence of Connected to my.patientsknowbest.com. indicate success. |
Expected failure output
| Code Block |
|---|
Trying 35.246.122.93... |
| Warning |
|---|
Absence of Connected to my.patientsknowbest.com. indicates failure. |
Trouble shooting
There might be multiple reasons why above check failed.
On the host that runs your service run the next command:
| Code Block |
|---|
|
timeout 3 nmap my.patientsknowbest.com -p 443 |
Expected success output
| Code Block |
|---|
Starting Nmap 7.95 ( https://nmap.org ) at 2024-11-14 15:30 CET
Nmap scan report for my.patientsknowbest.com (35.246.122.93)
Host is up (0.018s latency).
rDNS record for 35.246.122.93: 93.122.246.35.bc.googleusercontent.com
PORT STATE SERVICE
443/tcp open https
Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds |
| Tip |
|---|
443/tcp open https indicates that packets can reach our servers.
|
Expected failure outputs
Network error
| Code Block |
|---|
Starting Nmap 7.95 ( https://nmap.org ) at 2024-11-26 11:44 CET |
| Warning |
|---|
Absence of Nmap scan report for my.patientsknowbest.com (35.246.122.93and more output lines indicate that your client cannot establish a network connection to our server. This is most likely caused by firewall rules of your organizations not allowing egress towards us. |
| Panel |
|---|
| panelIconId | 1f3c1 |
|---|
| panelIcon | :checkered_flag: |
|---|
| panelIconText | 🏁 |
|---|
| bgColor | #DEEBFF |
|---|
|
NEXT: Try to resolve the issue within your organization. |
We reject your traffic
| Panel |
|---|
| panelIconId | atlassian-light_bulb_on |
|---|
| panelIcon | :light_bulb_on: |
|---|
| panelIconText | :light_bulb_on: |
|---|
| bgColor | #FFFAE6 |
|---|
|
TIP: This failure should only happen for APIs where we implemented IP allow listing, such as HL7. |
...
| Code Block |
|---|
Starting Nmap 7.95 ( https://nmap.org ) at 2024-11-14 15:30 CET
Nmap scan report for my.patientsknowbest.com (35.246.122.93)
Host is up (0.018s latency).
rDNS record for 35.246.122.93: 93.122.246.35.bc.googleusercontent.com
PORT STATE SERVICE
443/tcp filtered https
Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds |
| Panel |
|---|
| panelIconId | 1f3c1 |
|---|
| panelIcon | :checkered_flag: |
|---|
| panelIconText | 🏁 |
|---|
| bgColor | #DEEBFF |
|---|
|
NEXT: Make sure your send traffic from an IP address that you previously whitelisted with us. |
Server is down
| Code Block |
|---|
Starting Nmap 7.95 ( https://nmap.org ) at 2024-11-15 10:03 CET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.02 seconds |
| Warning |
|---|
Note: Host seems down. indicates some network error or the host is really down.
|
| Panel |
|---|
| panelIconId | 1f3c1 |
|---|
| panelIcon | :checkered_flag: |
|---|
| panelIconText | 🏁 |
|---|
| bgColor | #DEEBFF |
|---|
|
NEXT: Visit https://www.pkbstatus.com/ and look out comms from us. |
