Allow HTTP connections to TrueNAS servers #3

Closed
opened 2026-11-16 02:36:07 +00:00 by aaron · 0 comments
Owner

Problem

tntop currently requires HTTPS. Users cannot connect to a TrueNAS server that only serves HTTP.

Change

Allow users to add and connect to servers with an http:// URL. Use an unencrypted WebSocket connection for HTTP servers and keep the existing TLS behavior for HTTPS servers.

Done when

  • Users can add, save and connect to an HTTP server.
  • HTTP connections use ws://; HTTPS connections continue to use wss://.
  • HTTP connections do not attempt certificate checks or certificate trust prompts.
  • HTTPS validation and certificate handling still work.
  • Connection docs explain that HTTP sends API keys and server data without encryption.
  • Tests cover HTTP URL validation and connection setup alongside existing HTTPS behavior.
## Problem tntop currently requires HTTPS. Users cannot connect to a TrueNAS server that only serves HTTP. ## Change Allow users to add and connect to servers with an `http://` URL. Use an unencrypted WebSocket connection for HTTP servers and keep the existing TLS behavior for HTTPS servers. ## Done when - Users can add, save and connect to an HTTP server. - HTTP connections use `ws://`; HTTPS connections continue to use `wss://`. - HTTP connections do not attempt certificate checks or certificate trust prompts. - HTTPS validation and certificate handling still work. - Connection docs explain that HTTP sends API keys and server data without encryption. - Tests cover HTTP URL validation and connection setup alongside existing HTTPS behavior.
aaron added this to the v0.2.0 milestone 2026-11-16 14:41:41 +00:00
aaron closed this issue 2026-11-16 17:21:14 +00:00
Sign in to join this conversation.
No description provided.