Repository navigation
Settings Connection
The Connection tab controls how Nebulae listens for peers, the proxy server used for outgoing connections, and the IP filter that blocks unwanted hosts.
| Setting | Description |
|---|---|
| Listening port | The TCP/UDP port the torrent engine opens for incoming peer connections. Default: 51413. |
| Use UPnP / NAT-PMP port forwarding from router | Asks your router to forward the listening port automatically so remote peers can reach you without manual port forwarding. |
| Use different port on each startup | Randomizes the listening port each time the application starts (overrides the port field above). |
Tip
If your router supports UPnP, enabling it is the easiest way to achieve connectable status and higher peer counts.
| Setting | Description |
|---|---|
| Global maximum number of connections | Hard cap on the total number of peer connections across all torrents. Default: 500. |
| Maximum number of connections per torrent | Per-torrent cap on simultaneous peer connections. Default: 100. |
| Global maximum number of upload slots | Maximum concurrent upload slots across all torrents. Default: 8. |
| Maximum number of upload slots per torrent | Maximum concurrent upload slots for a single torrent. Default: 14 (tuned for Racing Mode compatibility). |
Note
When Racing Mode is enabled (BitTorrent tab), the engine overrides the per-torrent and global connection limits to 150 and 1 000 respectively, and sets 14 unchoke slots — regardless of what is entered here. These fields resume control when Racing Mode is off.
Configure an outbound proxy for peer or tracker traffic. Nebulae supports HTTP, SOCKS4, and SOCKS5.
| Setting | Description |
|---|---|
| Type | Proxy protocol: None (disabled), HTTP, SOCKS4, SOCKS5. |
| Host | Proxy server IP address or hostname (e.g., 127.0.0.1). |
| Port | Proxy server port number. |
| Use proxy for peer connections | Routes peer-to-peer traffic through the proxy. |
| Disable connections not supported by proxies | Disables connection types that cannot route through a proxy (e.g., UDP tracker announces with SOCKS4). |
| Proxy requires authentication | Reveals Username and Password fields when checked. |
| Username / Password | Credentials for authenticated proxies. Visible only when Proxy requires authentication is enabled. |
| Use proxy for torrent connections | Routes all torrent traffic (not only peer connections) through the proxy. |
| Use proxy for RSS feeds | Routes RSS feed fetches through the proxy. |
Important
When Nebulae is configured for private-network routing through Tailscale (see Tailnet Status), the SOCKS5 proxy at 127.0.0.1:1055 is used automatically. Setting a conflicting proxy here can break private-path routing.
| Setting | Description |
|---|---|
| Enable IP filter | Activates blocklist-based IP filtering. |
| Filter file path | Absolute path to an IP filter file in .dat (eMule/PeerGuardian) or .p2p format. |
| Apply filter to trackers too | Also blocks tracker announces to filtered IP ranges (not just peer connections). |
Note
The filter file is read from disk on startup and whenever you save settings. Large blocklists (hundreds of MB) may slow startup momentarily.
Next: Settings — Speed · Previous: Settings — Downloads