The Remote Proxy Access Service allows you to securely access your application container interfaces—such as ChirpStack or File Browser—through a web browser from anywhere in the world. This access is enabled through a unique, authenticated URL linked to your VeeaHub.

Requirements

• Veea Platform version 2.29.0 or later
• Installed SO2 component
• An application that supports remote proxy access (e.g., LoRaWAN)

Remote Access in the LoRaWAN Application

The LoRaWAN application package, version 2.1.4 or later, supports remote access via the proxy service. Remote access can be enabled during subscription.

When subscribing, users can also:

• Enable remote access with a checkbox
• Set a custom login and password for ChirpStack and File Browser

How the Remote Proxy URL Works

Once enabled, the LoRaWAN application sets up a proxy service in the Veea Cloud, creating a unique URL that links directly to the ChirpStack UI and Configuration File Editor.

The URL is constructed from the following four components:

1. Application container name – e.g., vh-chirpstack-core
2. Serial number of the VeeaHub gateway running the app – findable in:
   • The label on the physical VeeaHub
   • Control Center: Navigate to VeeaHubs > Serial Number
3. Cloud domain name – always services.veea.io
4. Port number – typically 443 for HTTPS (optional in the URL)

Example URL format:

https://vh-chirpstack-core.<serial-number>.services.veea.io

With the correct URL and credentials, you’ll have remote access to ChirpStack’s dashboard or the File Browser interface securely and without needing a local connection.