-
Notifications
You must be signed in to change notification settings - Fork 24
Inbounds Management
Elora VPN edited this page Nov 5, 2024
·
1 revision
- Overview
- Understanding Inbounds
- Configuration Guide
- Technical Details
- Best Practices
- Troubleshooting
An inbound configuration in this panel represents a connection point for VPN services. Each inbound is synchronized with a target host, allowing centralized management of VPN configurations across multiple servers.
- Automatic synchronization with target hosts
- Real-time traffic monitoring
- Centralized account management
- Multiple protocol support
- Advanced security options
Each inbound in the management panel must correspond to an inbound on the target host with a matching key. This relationship ensures:
- Automatic account synchronization
- Traffic monitoring
- Configuration management
- Load balancing capabilities
- VLESS (Default)
- VMess
- Trojan
- Shadowsocks
- TLS (Default)
- Reality
- None (Not recommended for production)
- Click the purple CREATE button
- Fill in required fields:
Field | Description | Example |
---|---|---|
Remark | Identifiable name | Germany-Frankfurt-A |
Key | Unique identifier | 1 |
Port | Connection port | 443 |
Domain | Service domain | de.example.com |
Request Host | Request header host | de.example.com |
SNI | TLS SNI field | de.example.com |
Address | Server address | 162.44.132.10 |
Path | WebSocket path | /ws |
- Configure additional settings:
- Enable: Activate the inbound
- Develop: Enable development mode
- Security: Choose security type
- Flow: Set traffic flow type
- Type: Select protocol type
- Host: Select target host
When an inbound is created:
- System verifies target host availability
- Checks for matching key on target host
- Synchronizes configuration
- Establishes monitoring
Type Options:
- vless (default)
- vmess
- trojan
- shadowsocks
Security Options:
- tls (default)
- reality
- none
Flow Options:
- xtls-rprx-vision
- xtls-rprx-vision-udp443
- Each inbound requires a unique key per host
- Keys link panel inbounds to host inbounds
- Used for synchronization and traffic matching
- Client connects to inbound
- Traffic is recorded on host
- Data syncs to panel
- Statistics update in real-time
- ID: Unique identifier
- Remark: Descriptive name
- Domain: Service domain
- Key: Sync identifier
- Host: Target server
- Type: Protocol type
- Enable: Status
- Develop: Development mode
- Modified: Last update
- Search by remark, domain, or address
- Sort by creation date
- Filter by host
- Filter by status
- 🗑️ Delete: Remove inbound
- ✏️ Edit: Modify settings
When a user purchases a service:
- Account created in panel
- Configuration synced to host
- Access details generated
- Traffic monitoring begins
- Real-time usage tracking
- Bandwidth allocation
- Usage limitations
- Alert systems
- Always use TLS/Reality security
- Regularly rotate ports
- Use strong SNI configurations
- Monitor for unusual traffic
- Balance users across inbounds
- Monitor server load
- Use appropriate protocols
- Configure proper paths
- Regular configuration review
- Traffic pattern analysis
- Security updates
- Performance monitoring
- Backup configurations
Problem: Inbound not syncing
Solutions:
1. Verify host connection
2. Check key matching
3. Confirm port availability
4. Review security settings
Problem: Traffic not updating
Solutions:
1. Check host connectivity
2. Verify inbound status
3. Review logging settings
4. Check database connection
Error | Cause | Solution |
---|---|---|
Key Conflict | Duplicate key on host | Use unique key |
Sync Failed | Host unreachable | Check connection |
Port in Use | Port already allocated | Change port |
- Testing environment
- Separate logging
- Debug options
- No traffic limits
- Traffic shaping
- Rate limiting
- Connection pooling
- Load balancing