---
title: "Check Access To PKB Servers"
canonical: "https://wiki.patientsknowbest.com/space/api/4494131216/Check%20Access%20To%20PKB%20Servers"
format: markdown
---
> Macro (toc)

# Instructions

> 📝 Following instruction on this page you can test if your network traffic can flow both ways between your host and our servers.

On the host that runs your service run the next command:

```shell
echo quit | timeout 3 telnet my.patientsknowbest.com 443
```

Above command will try for three seconds to connect to one of our servers (`my.patientsknowbest.com`).

> ℹ️ **TIP**: You might need to change the hostname `my.patientsknowbest.com` depending on what API you are trying to reach. To get the relevant hostname consult our [https://wiki.hub.patientsknowbest.com/wiki/pages/createpage.action?spaceKey=api&title=PKB%20API%20Network%20Connectivity%20-%20new&linkCreation=true&fromPageId=4494131216](https://wiki.hub.patientsknowbest.com/wiki/pages/createpage.action?spaceKey=api&title=PKB%20API%20Network%20Connectivity%20-%20new&linkCreation=true&fromPageId=4494131216) page.

# Expected Success Output

```
Trying 35.246.122.93...
Connected to my.patientsknowbest.com.
Escape character is '^]'.
Connection closed by foreign host.
```

> ✅ Presence of `Connected to my.patientsknowbest.com.` indicate success.

## Expected Failure Output

```
Trying 35.246.122.93...
```

> ❌ 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:

```shell
timeout 3 nmap my.patientsknowbest.com -p 443
```

#### Expected success output

```
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
```

> ✅ `443/tcp open  https` indicates that packets can reach our servers.

#### Expected failure outputs

##### Network error

```
Starting Nmap 7.95 ( https://nmap.org ) at 2024-11-26 11:44 CET
```

> ❌ Absence of `Nmap scan report for my.patientsknowbest.com (35.246.122.93`and 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.

> ℹ️ **NEXT**: Try to resolve the issue within your organization.

##### We reject your traffic

> ℹ️ **TIP**: This failure should only happen for APIs where we implemented IP allow listing, such as HL7.

```
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
```

> ❌ `443/tcp filtered  https` indicates that traffic reaces our servers, but we drop them, cause given IP is not in our allow list.

> ℹ️ **NEXT**: Make sure your send traffic from an IP address that you previously whitelisted with us.

> ℹ️ **TIP**: To request an IP address to be allowed through our firewalls, please contact [integrations@patientsknowbest.com](mailto:integrations@patientsknowbest.com).
> ℹ️ 
> ℹ️ The IP address to be whitelisted will be the IP address as presented to PKB once outside of your internal network. This is often the IP address once NAT’d. Please consider any failover IPs that you may need to whitelist also. Your network team will be able to help you determine the correct IP address.

##### Server is down

```
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
```

> ❌ `Note: Host seems down.` indicates some network error or the host is really down.

> ℹ️ **NEXT**: Visit [https://www.pkbstatus.com/](https://www.pkbstatus.com/)  and look out comms from us.