hopefully a fix for image loading

Overlord-Server/src/main-server.ts

@@ -128,6 +128,13 @@ const TLS_KEY_PATH = config.tls.keyPath;
 const TLS_CA_PATH = config.tls.caPath; 
 const TLS_CERTBOT = config.tls.certbot;
 
+function envFlagEnabled(name: string): boolean {
+  const value = String(process.env[name] || "").trim().toLowerCase();
+  return value === "1" || value === "true" || value === "yes" || value === "on";
+}
+
+const TLS_OFFLOAD = envFlagEnabled("OVERLORD_TLS_OFFLOAD");
+
 const pluginLoadedByClient = new Map<string, Set<string>>();
 const pendingPluginEvents = new Map<string, Array<{ event: string; payload: any }>>();
 const pluginLoadingByClient = new Map<string, Set<string>>();
@@ -221,12 +228,27 @@ const pendingScripts = new Map<string, PendingScript>();
 
 async function startServer() {
   await loadPluginState();
-  const tls = await prepareTlsOptions({
+  let tls:
+    | {
+        tlsOptions: { cert?: string; key?: string; ca?: string };
+        certPathUsed: string;
+        source: "certbot" | "configured" | "self-signed";
+      }
+    | null = null;
+
+  if (TLS_OFFLOAD) {
+    logger.warn(
+      "[TLS] OVERLORD_TLS_OFFLOAD=true: TLS is expected to terminate at an external proxy/load balancer.",
+    );
+    logger.warn("[TLS] Running internal HTTP listener only. Do not expose the container port directly to the internet.");
+  } else {
+    tls = await prepareTlsOptions({
       certPath: TLS_CERT_PATH,
       keyPath: TLS_KEY_PATH,
       caPath: TLS_CA_PATH,
       certbot: TLS_CERTBOT,
     });
+  }
 
   const routeDeps = {
     notificationsConfig: {
@@ -349,7 +371,7 @@ async function startServer() {
   const server = Bun.serve<SocketData>({
     port: PORT,
     hostname: HOST,
-    tls: tls.tlsOptions,
+    ...(tls ? { tls: tls.tlsOptions } : {}),
     idleTimeout: 255,
     fetch: createHttpFetchHandler({
       metrics,
@@ -397,7 +419,21 @@ async function startServer() {
     disconnectTimeoutMs: DISCONNECT_TIMEOUT_MS,
   });
 
+  if (tls) {
     logServerStartup(server, tls.certPathUsed, tls.source);
+  } else {
+    const hostname = server.hostname || "0.0.0.0";
+    const port = server.port ?? 0;
+    logger.info("========================================");
+    logger.info("Overlord Server - PROXY TLS OFFLOAD MODE");
+    logger.info("========================================");
+    logger.info(`HTTP (internal): http://${hostname}:${port}`);
+    logger.info(`WS   (internal): ws://${hostname}:${port}/api/clients/{id}/stream/ws`);
+    logger.info("");
+    logger.info("External access should be HTTPS/WSS via your reverse proxy platform.");
+    logger.info("Set this mode only when TLS is terminated by the platform (for example Render). ");
+    logger.info("========================================");
+  }
 }
 
 startServer();

README.md

@@ -70,6 +70,23 @@ These can be changed with:
 
 It's literally just docker any question chatgpt can answer so don't worry.
 
+## Reverse proxy TLS offload (Render, etc.)
+
+Some platforms (such as Render Web Services) terminate TLS at the edge and expect your container to serve plain HTTP on the internal port.
+
+For those platforms, set:
+
+- `OVERLORD_TLS_OFFLOAD=true`
+
+Defaults are unchanged. If `OVERLORD_TLS_OFFLOAD` is not set (or false), Overlord keeps its current behavior and serves HTTPS/WSS directly with configured/self-signed/certbot certificates.
+
+When offload mode is enabled:
+
+- Container listener is `http://0.0.0.0:$PORT` (internal only)
+- External URL should still be `https://...` via your platform proxy
+- Health checks should target `http://localhost:$PORT/health` inside the container
+- Do not expose the internal container port directly to the public internet
+
 ## Using-Production-packages-(Windows)
 
 Build a production-ready package where the server can still build client binaries at runtime:

docker-compose.quickstart.yml

@@ -18,6 +18,9 @@ services:
       - OVERLORD_TLS_CERT=/app/certs/server.crt
       - OVERLORD_TLS_KEY=/app/certs/server.key
       - OVERLORD_TLS_CA=
+      # Set true only behind a trusted reverse proxy that terminates TLS (for example Render).
+      # Default false keeps current behavior: Overlord terminates TLS in-process.
+      - OVERLORD_TLS_OFFLOAD=false
       # Optional certbot integration (used only when NODE_ENV=production)
       - OVERLORD_TLS_CERTBOT_ENABLED=false
       - OVERLORD_TLS_CERTBOT_LIVE_PATH=/etc/letsencrypt/live

docker-compose.yml

@@ -18,6 +18,9 @@ services:
       OVERLORD_TLS_CERT: ${OVERLORD_TLS_CERT:-/app/certs/server.crt}
       OVERLORD_TLS_KEY: ${OVERLORD_TLS_KEY:-/app/certs/server.key}
       OVERLORD_TLS_CA: ${OVERLORD_TLS_CA:-}
+      # Set true only behind a trusted reverse proxy that terminates TLS (for example Render).
+      # Default false keeps current behavior: Overlord terminates TLS in-process.
+      OVERLORD_TLS_OFFLOAD: ${OVERLORD_TLS_OFFLOAD:-false}
       # Optional certbot integration (used only when NODE_ENV=production)
       OVERLORD_TLS_CERTBOT_ENABLED: ${OVERLORD_TLS_CERTBOT_ENABLED:-false}
       OVERLORD_TLS_CERTBOT_LIVE_PATH: ${OVERLORD_TLS_CERTBOT_LIVE_PATH:-/etc/letsencrypt/live}