NZBGet Port Settings and Access Guide

NZBGet provides a web-based interface that allows you to manage Usenet automation easily from any browser. By default, the interface is accessible through a specific port, but depending on your setup, you may need to change or troubleshoot it.

This guide explains how the NZBGet port works, how to modify it, and how to avoid common access issues.

Default NZBGet Port

NZBGet uses the following port for its Web interface:

• Username: 6789
• Access URL: http://<device-ip>:6789

This port is used across most installations, including:

• Native desktop installations (Windows, Linux, macOS)
• Docker containers (e.g., LinuxServer.io image)
• NAS systems like Synology and QNAP
• Media automation platforms like Unraid or DietPi

How to Change the NZBGet Port

There are two common ways to change the port:

Option 1: Change via Web Interface (If Accessible)

1. Go to http://localhost:6789 and log in.
2. Click on Settings.
3. Go to Security → ControlPort.
4. Change the value from 6789 to your desired port.
5. Save all changes.
6. Restart NZBGet.

⚠️ After restarting, you’ll need to use the new port in your browser: http://localhost:<new-port>

Option 2: Change via Configuration File

If the Web interface isn’t accessible:

1. Open the nzbget.conf configuration file.
   • Common paths:
     • /etc/nzbget.conf (Linux)
     • /config/nzbget.conf (Docker)
2. Look for this line: ControlPort=6789
3. Replace 6789 with your desired port (e.g., 8080).
4. Save and restart NZBGet.

Port Already in Use?

If another application is using port 6789, you might see errors or be unable to access NZBGet.

How to Check:

On Linux/macOS: sudo lsof -i :6789

On Windows (Command Prompt): netstat -aon | findstr :6789

If another process is using the port, change NZBGet to a different one (e.g., 6790) using the steps above.

Using NZBGet Behind a Reverse Proxy

If you’re running NZBGet alongside a Web server (like Nginx or Apache), it’s common to reverse proxy access instead of exposing the port directly.

Basic Nginx Proxy Example:

location /nzbget/ {
    proxy_pass http://localhost:6789/;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
}

This allows access at http://yourdomain.com/nzbget/ while keeping NZBGet on its default port.

Firewall and Router Considerations

If you can’t reach NZBGet from another device on your network:

• Check firewall settings to make sure port 6789 (or your custom port) is allowed.
• On routers, avoid port forwarding unless NZBGet access is restricted to LAN.
• For Docker users, confirm the port is published correctly with -p 6789:6789.

NZBGet Port Overview

Troubleshooting Port Access

Issue: Can’t access http://localhost:6789
Fix:

• Confirm NZBGet is running
• Verify the port hasn’t been changed
• Check firewall/antivirus blocking
• Use docker ps to check port mapping if in a container

Issue: Port conflict
Fix: Change NZBGet’s port or shut down the other service

Issue: Secure remote access
Fix: Run behind a reverse proxy and use HTTPS