Skip to main content

Configure NNTP Servers

Configure NNTP (Usenet) servers for streaming content directly from Usenet without downloading the entire NZB first.

Overview​

NNTP servers enable Cinephage to:

  • Stream from Usenet — Stream NZB content without full download
  • Check article availability — Verify NZB articles exist before downloading
  • Multi-server failover — Use multiple providers for redundancy

Adding an NNTP Server​

Navigate to Settings > Integrations > NNTP Servers.

Step 1: Click Add Server​

Step 2: Configure Server Settings​

FieldDescriptionExample
NameDisplay name for this serverEweka Primary
HostNNTP server hostnamenews.eweka.nl
PortServer port563 (SSL) or 119
SSLEnable SSL/TLS encryptionRecommended
UsernameYour Usenet provider usernameFrom provider
PasswordYour Usenet provider passwordFrom provider
ConnectionsMaximum concurrent connections8 (check provider limit)
PriorityServer priority (lower = higher priority)1

Step 3: Test Connection​

  1. Click Test to verify credentials
  2. Check connection speed and authentication
  3. Review any error messages

Step 4: Save​

Click Save to add the server.

Server Priority​

When multiple servers are configured:

  1. Priority 1 servers used first
  2. Fallback to lower priority if primary fails
  3. Article completion checked across all servers

Priority Strategy​

PriorityUse Case
1Primary (fastest) provider
2-5Backup providers
6-10Block fill servers

Connection Limits​

Check your Usenet provider's connection limits:

ProviderTypical Connections
Eweka50
Newshosting60
UsenetExpress50
Blocknews30
Don't Exceed Limits

Setting connections higher than your provider allows may result in:

  • Connection refused errors
  • Temporary IP blocks
  • Degraded performance

SSL/TLS Configuration​

PortSSLUse Case
563YesRecommended (SSL)
119NoUnencrypted
80NoAlternative clear
443YesAlternative SSL

Always enable SSL when available for:

  • Privacy protection
  • ISP throttling avoidance
  • Security

Bulk Actions​

Select multiple servers to:

  • Enable/Disable — Toggle servers on/off
  • Test — Verify all connections at once
  • Delete — Remove servers

Status Indicators​

StatusMeaning
HealthyConnection test successful
UnhealthyConnection test failed
DisabledServer disabled, not used

Troubleshooting​

Connection Refused​

  1. Check host and port — Verify correct server address
  2. Verify SSL setting — SSL port requires SSL enabled
  3. Check firewall — Ensure port is not blocked
  4. Provider status — Check if provider is having issues

Authentication Failed​

  1. Verify credentials — Check username/password
  2. Account status — Ensure subscription is active
  3. Connection limits — May be exceeded on provider side
  4. Case sensitivity — Some providers are case-sensitive

Slow Performance​

  1. Reduce connections — Too many can cause throttling
  2. Check priority — Ensure fastest server is priority 1
  3. SSL overhead — Try non-SSL if speed is critical
  4. Provider issues — Check provider status page

SSL Certificate Errors​

  1. Update certificates — System CA bundle may be outdated
  2. Verify hostname — Must match certificate exactly
  3. Try alternative port — 443 instead of 563

Best Practices​

Multiple Providers​

Configure at least 2 servers:

  • Primary — Fast, unlimited provider
  • Backup — Block account for missing articles

Connection Tuning​

System TypeConnections
Low-power4-8
Standard8-16
High-performance20-30

Security​

  • Always use SSL when available
  • Don't share credentials between users
  • Use strong passwords for Usenet accounts
  • Monitor usage for unexpected activity

API Endpoints​

MethodEndpointDescription
GET/api/usenet/serversList servers
POST/api/usenet/serversCreate server
PUT/api/usenet/servers/[id]Update server
DELETE/api/usenet/servers/[id]Delete server
POST/api/usenet/servers/[id]/testTest connection
POST/api/usenet/servers/syncSync connections

See Also​