warpgate tls issue while running in ecs container with loadbalancer

[ankeshgpt153]

While running Warpgate in AWS ECS container, getting an issue related to TLS

March 25, 2026, 10:18	25.03.2026 04:48:25 ERROR warpgate::commands::run: Server error error=protocol server: HTTP	warpgate
March 25, 2026, 10:18	Caused by:	warpgate
March 25, 2026, 10:18	0: rustls setup	warpgate
March 25, 2026, 10:18	1: loading TLS certificate and key:	warpgate
March 25, 2026, 10:18	2: I/O: Is a directory (os error 21)	warpgate
March 25, 2026, 10:18	3: Is a directory (os error 21)	warpgate
March 25, 2026, 10:18	25.03.2026 04:48:25 INFO warpgate_protocol_http: Cookie domain configured: .warpgate.xxx.xxx.io (base host: warpgate.dev-ssh.cnhi.io) - cookies will work for warpgate.xxx.xxx.io and all its subdomains	warpgate
March 25, 2026, 10:18	25.03.2026 04:48:25 INFO warpgate::commands::run: Accepting HTTP connections on 0.0.0.0:8888	warpgate

warpgate.yaml

sso_providers: []
recordings:
enable: true
path: /data/recordings
external_host: null
database_url: postgres://xxx:xxx@xxx:5432/warpgate
ssh:
enable: true
listen: '0.0.0.0:2222'
keys: /data/ssh-keys
host_key_verification: auto-accept
inactivity_timeout: 24h
keepalive_interval:
secs: 60
nanos: 0
http:
enable: true
listen: '0.0.0.0:8888'
trust_x_forwarded_headers: true
session_max_age: 24h
cookie_max_age: 1day
mysql:
enable: true
listen: '0.0.0.0:33306'
postgres:
enable: true
listen: '0.0.0.0:55432'
log:
retention: 7days
send_to: null
format: text

[Eugeny]

Looks like you've mounted a non-existing host path in place of the certificate files, which results in the container runtime creating an empty directory in its place

[ankeshgpt153]

Providing tls key and cert is mandatory i bind http behind loadbalancer with aws cert ?

[Eugeny]

Yes, Warpgate doesn't support running without TLS, even if you already have a TLS reverse proxy in front of it