# Region Selection

SocketXP Cloud Gateway is hosted in the following regions:

  • us-central (Iowa, U.S.) Default Region
  • eu (Frankfurt, Germany)
  • au (Sydney, Australia [coming soon...])

By default, SocketXP agent connects to the SocketXP Cloud Gateway located in the us-central region.


The country, state or province where the SocketXP Cloud Gateway is hosted in a region may change without notice based on the cloud resource availability in that region.


We respect your privacy and confidentiality. To know more about our GDPR policy visit: https://www.socketxp.com/gdpr (opens new window)

# Authentication Token

Sign up in the region specific SocketXP Portal page to get a region specific authentication token to login/connect your devices with the SocketXP Cloud Gateway in that region.

# US-Central (Default Region)

Sign up at https://portal.socketxp.com (opens new window).

# Europe Region

Sign up at https://portal.eu.socketxp.com (opens new window).

# Australia Region (coming soon...)

Sign up at https://portal.au.socketxp.com (opens new window).

Region Specific Auth-Token

You cannot use the authentication token provided by a SocketXP IoT Cloud Gateway in one region (say, for eg: us-central) to login or connect a device to a SocketXP IoT Cloud Gateway in another region (say, eu). You need to sign-up in the region specific portal page to get a region specific authtoken. Use the region specific authtoken to login/connect a device to the gateway in that region.

# Command Examples:

To select a specific region, use the "--region" option as shown below:

# Login

$ socketxp login [authtoken] --region "eu"

# Connect

SSH Service:

$ socketxp connect tcp:// --region "eu"

Connected to SocketXP Cloud Gateway.
Access the TCP service securely using the SocketXP agent in IoT Slave Mode.

HTTP Service:

$ socketxp connect --region "eu"

Connected to SocketXP Cloud Gateway.
Public URL -> https://abc123.eu.socketxp.com

# Sample Config.json file:

$ cat /etc/socketxp/config.json

"region" : "eu",
"tunnels" : [
      "destination": "tcp://"
      "destination": "",
      "subdomain": "techron-abc123456789",
      "custom_domain": "dev.example.com"