Configuration

Learn about all configuration options for InTunnel clients.

CLI Configuration

The CLI can be configured via:

1. Command-line flags
2. Environment variables
3. Configuration file

Command-Line Flags

intunnel -token YOUR_TOKEN -port 3000 -subdomain myapp -domain intunnel.cloud

Flag	Description	Default
-token	Authentication token	(required)
-port	Local port to expose	3000
-subdomain	Subdomain to use	(from token)
-domain	Domain to use	intunnel.cloud

Environment Variables

export INTUNNEL_TOKEN="your-token"
export INTUNNEL_PORT="8080"
export INTUNNEL_SUBDOMAIN="myapp"
export INTUNNEL_DOMAIN="intunnel.cloud"

intunnel

Configuration File

Create ~/.intunnel/config.yaml:

token: "your-token-here"
port: 3000
subdomain: "myapp"
domain: "intunnel.cloud"

Full configuration file reference →

GUI Configuration

The GUI stores settings automatically:

Setting	Location
Windows	%APPDATA%\InTunnel\settings.json
macOS	~/Library/Application Support/InTunnel/settings.json
Linux	~/.config/intunnel/settings.json

INFO

Tokens are not saved automatically for security. You need to enter your token each time.

Local Service Configuration

Common Frameworks

Configure your local framework to accept connections:

React (Create React App)

# Already works on port 3000 by default
npm start

Next.js

# Uses port 3000 by default
npm run dev

Vue.js

# Uses port 8080 by default
npm run serve

Express.js

const PORT = process.env.PORT || 3000;
app.listen(PORT, () => {
  console.log(`Server running on port ${PORT}`);
});

Django

python manage.py runserver 0.0.0.0:8000

Flask

flask run --host=0.0.0.0 --port=5000

Rails

rails server -b 0.0.0.0 -p 3000

Binding Address

Some frameworks bind to 127.0.0.1 by default. InTunnel can still access these, but for full compatibility, bind to 0.0.0.0:

# Node.js example
node server.js --host 0.0.0.0

Port Selection

Common Ports

Port	Common Use
3000	React, Next.js, Express
5000	Flask, Python
8000	Django
8080	Vue.js, general dev
4200	Angular
5173	Vite

Finding Your Port

macOS/Linux:

lsof -i -P | grep LISTEN

Windows (PowerShell):

netstat -an | findstr LISTEN

Connection Settings

Auto-Reconnect

Both CLI and GUI automatically reconnect on connection loss:

• Initial retry: 1 second
• Max backoff: 30 seconds
• Unlimited retry attempts

Timeout Settings

Setting	Value
Connection timeout	30 seconds
Idle timeout	None (persistent)
Request timeout	60 seconds

Network Configuration

Firewall Rules

InTunnel needs outbound access to:

• *.intunnel.cloud port 7000 (tunnel connection)
• *.intunnel.online port 7000
• *.intunnel.tech port 7000

Proxy Support

If behind a corporate proxy, you may need to configure it:

export HTTP_PROXY=http://proxy.company.com:8080
export HTTPS_PROXY=http://proxy.company.com:8080
intunnel -token YOUR_TOKEN

WARNING

Some proxies may block WebSocket connections required for tunneling.

Next Steps

• Security Configuration - Security best practices
• CLI Commands - Full CLI reference
• Troubleshooting - Common issues