Troubleshooting HellaNZB Remote: Common Issues and Fixes

HellaNZB Remote: Complete Setup Guide for Remote NZB Management

This guide walks you through installing, configuring, and securely using HellaNZB Remote to manage NZB downloads from anywhere. Assumptions: you have a working NZB downloader (e.g., NZBGet, Sabnzbd) running on a home server or NAS, and basic router/access knowledge. If not, the steps still apply—reasonable defaults are included.

1. What HellaNZB Remote does

• Remote control: Send NZBs, start/stop downloads, monitor queue and history.
• Integration: Works with popular NZB clients via APIs (NZBGet, Sabnzbd).
• Mobile/remote use: Access from phone or remote web client.

2. Prerequisites

• A running NZB client (NZBGet or Sabnzbd) on a device with a stable LAN IP (default examples: 192.168.1.50).
• Router with ability to forward a port (if you need access outside your LAN).
• Optional: dynamic DNS (DDNS) if your home IP changes, and an SSL certificate or reverse proxy for secure access.
• HellaNZB Remote app or web UI installed on the device you’ll use to control it.

3. Install and enable API access on your NZB client

1. NZBGet

   • Open NZBGet web UI (usually http://:6789).
   • Go to Settings → Security.
   • Set an Username and Password and ensure API is enabled.
   • Note the Control IP settings and port (default 6789).

2. Sabnzbd

   • Open Sabnzbd web UI (usually http://:8080).
   • Go to Config → General / API.
   • Copy the API Key and set a username/password if desired.
   • Note the port (default 8080).

4. Install HellaNZB Remote and connect to your client

• Install the HellaNZB Remote app or open its web UI.
• In Remote settings:
  • Host: enter your NZB client’s LAN IP (e.g., 192.168.1.50).
  • Port: enter the client port (6789 for NZBGet, 8080 for Sabnzbd).
  • Username/Password or API Key: paste the credentials from step 3.
  • Test connection and save.

5. Configure secure remote access (recommended)

Option A — Reverse proxy with SSL (recommended for security)

• Run a reverse proxy (Caddy, Nginx, Traefik) on a machine that’s reachable from the Internet or bind your router to forward to it.
• Configure the proxy to forward a subdomain (e.g., nzb.example.com) to your NZB client’s local IP:port.
• Use Let’s Encrypt (Caddy or Traefik can automate) to enable HTTPS.
• Limit access with basic auth or IP allowlists if desired.

Option B — VPN

• Install a VPN server (WireGuard, OpenVPN) on your home network.
• Connect your phone/remote device to the VPN to access the NZB client securely without opening ports.

Option C — Port forwarding (less secure)

• Forward the NZB client port from your router to your server.
• Use a strong password and, if supported, enable HTTPS in the NZB client.
• Add rate limits or IP restrictions on your router if possible.

6. Optional: Use Dynamic DNS

• Sign up for a DDNS provider (DuckDNS, No-IP).
• Configure your router or a local client to update the DDNS hostname.
• Use the hostname in HellaNZB Remote connection settings for stable remote access.

7. Common settings and tips

• Connection timeout: increase if you see intermittent failures on slow connections.
• Auto-reconnect: enable if supported to recover after temporary network loss.
• Queue rules: set max concurrent downloads and queue priorities in your NZB client for better bandwidth control.
• Notifications: enable push notifications in HellaNZB Remote (if available) for completed or failed downloads.
• Test locally first: confirm control works on LAN before configuring remote access.

8. Troubleshooting

• Cannot connect: verify NZB client is running, IP/port correct, and API credentials match.
• Authentication failed: re-enter username/password or API key; check for trailing spaces.
• DNS/hostname not resolving: use your public IP to test, then fix DDNS settings.
• SSL errors: ensure certificate matches the domain and include the correct port in the reverse proxy.

9. Example quick-check checklist

1. NZB client running and reachable on LAN.
2. API credentials copied.
3. HellaNZB Remote connected and tested locally.
4. Remote access method selected and configured (VPN or reverse proxy with TLS).
5. Notifications and auto-reconnect enabled.

10. Security best practices

• Use HTTPS for remote access.
• Prefer VPN access over raw port forwarding.
• Use strong, unique passwords or API keys.
• Keep NZB client and HellaNZB Remote updated.
• Limit exposed services and use firewall rules.

If you want, I can generate specific reverse proxy configs (Caddy, Nginx, Traefik) or a WireGuard setup file for your router and NZB client—tell me which server OS and NZB client you use.