Skip to main content

Aluvia Gateway Nodes

You connect to Aluiva through an Aluiva Gateway Node. Gateway nodes handle authentication, load balancing, and route your connection to an upstream mobile IP address on a US carrier entwork. All gateway nodes are located in the United States. You will automatically be connected to the optimal node.

Use the information below to connect to a gateway node.

Hostname​

gateway.aluvia.io

Ports and Supported Protocols​

  • Port 8080 for HTTP
  • Port 8443 for HTTPS
  • SOCKS support coming soon

Username and Password​

Your Aluiva Gateway Node credentials (username and password) are required to authenticate into the gateway node.

You can find your credentials on the "Credentials" page in Aluvia dashboard.

Keep Your Credentials Safe Store credentials securely and never commit them to version control or share them publicly.

Using Your Credentials​

Authentication Format​

Credentials must be provided with every request to the Aluvia gateway node. The exact method depends on your programming language, integration method, or client software.

  • Basic methods are outlined below
  • Take a look at our helpful code examples
  • Review our integration sections for integrating with automation tools, AI tools, or other 3rd party software.

Basic Authentication Header:

Authorization: Basic base64(username:password)

Proxy Authentication:

Proxy-Authorization: Basic base64(username:password)

URL Format:

http://username:password@gateway.aluvia.io:8080

Client Configuration: Most HTTP clients accept username and password as separate parameters during proxy configuration. Please refer to your client software documentation.

Security Recommendations​

  • Use Environment Variables: Store credentials in environment variables rather than hardcoding them
  • Never Commit Credentials: Add credential files to .gitignore to prevent accidental commits
  • Use Secret Management: For production environments, use secret management tools like AWS Secrets Manager, HashiCorp Vault, or similar services
  • Limit Exposure: Only share credentials with team members who need access