Connectivity Check for Public Cloud

Prev Next

This document will address connectivity issues that users face when using pCloudy's public cloud. It also acts as a guideline to new users who will be using the public cloud.

Please ensure that the URLs/IPs mentioned below are allowed on the respective network that you use to connect to the pCloudy platform.

Cloud Farm URLs

  1. URL - https://device.pcloudy.com
    IPs - 221.134.198.226, 221.134.198.227,159.100.192.108, 199.59.227.198, 159.100.198.118, 199.59.230.162, 159.100.195.114, 159.100.196.120, 185.114.77.167, 185.114.78.208

  2. URL - https://us.pcloudy.com
    IPs - 184.105.178.238, 184.105.178.226, 199.59.227.198, 159.100.198.118, 159.100.195.114, 159.100.196.120, 185.114.77.167, 185.114.78.208, 147.75.230.37, 147.75.227.184, 147.75.229.59, 147.75.236.169, 103.29.33.53, 206.201.199.118, 185.114.78.57

  3. URL - https://ind-west.pcloudy.com
    IPs - 147.75.228.103, 103.29.35.84, 103.58.166.16, 103.58.166.14, 185.114.76.176, 199.59.228.117, 185.152.130.77, 206.201.195.224, 159.100.207.171, 147.75.224.39, 147.75.231.125, 147.75.232.185, 167.179.3.94

  4. URL - https://sg.pcloudy.com
    IPs - 202.55.95.245, 202.55.81.214

Wildnet URLs:

  1. https://wildnetserverservices.pcloudy.com
    IP - 65.1.200.201

  2. https://wildnetservices.pcloudy.com
    IP - 3.6.161.28

Also Please ensure that the below mentioned port numbers are enabled to use the wildnet feature on the platform.

80 -- HTTP
443 -- HTTPS

If you get “Device Connectivity Error”, the following WebSocket needs to be enabled.

To connect the device from device.pcloudy.com we use WebSocket communication. Within the firewall allow below URLs from the browser to use WebSockets.

https://device.pcloudy.com
https://us.pcloudy.com
https://ind-west.pcloudy.com
https://sg.pcloudy.com

Curl must be allowed for the URL (device.pcloudy.com) using CLI. This is required for use of pCloudy REST APIs. We have mentioned the steps to allow the curl on your computer system. Please follow steps to allow the curl in your respective computer OS.

Open terminal and enter the command curl https://device.pcloudy.com. Refer to the screenshot below for the expected output.

image.png

Open the terminal and type the command https://device.pcloudy.com. Refer to the screenshot below for the expected output.

image.png

Open the command prompt and type the command curl https://device.pcloudy.com. Refer to the screenshot below for the expected output. Incase you need to install curl in the windows, click here and follow the steps accordingly.

image.png

  • 80 – HTTP
  • 443 – HTTPS

Incase the user faces

To decrease the latency and to make faster performance pCloudy changed the architecture with new streaming protocol i.e webRTC (Google) which gives us ~500 ms latency. Users can see almost real time streaming for any actions performed on the pCloudy devices. to
achieve it below pre-requisite needs to be followed.

  • 49152 - 65535 - TURN -> TCP and UDP
for reference -
  • 3478 and 5349 - STUN -> TCP and UDP
for reference -
  • 32768 to 65535 - TURN relay transport (this includes the above TURN ports as well)
  • 50000-60000 - UDP(WebRTC and RTSP)

Ports:
443 - HTTPS
50000-60000 - UDP(WebRTC and RTSP)

  • https://turn-pcloudy.pcloudy.com(IP: 20.219.199.11)
  • https://turn2.pcloudy.com(IP: 20.219.199.11)
  • https://turn3.pcloudy.com(IP: 20.228.162.136)
  • https://turn4.pcloudy.com(IP: 4.193.123.32)

To connect the device from https://device.pcloudy.com
We use Web Socket communication. Within the firewall allow
the(https://device.pcloudy.com, https://ind-west.pcloudy.com, https://us.pcloudy.com and
https://sg.pcloudy.com) browser to use WebSockets.
Below are the references for turn severs (Need not to whitelist, these are only for references of
Turn Servers)
(https://datatracker.ietf.org/doc/html/rfc8656.html#section-7.2)
(https://datatracker.ietf.org/doc/html/rfc8489#section-18.6)