Skip to content

A self-hosted media server and file management system

fix: caddy does not handle ws correctly in docker

aminnausinee13779b57d4
diff --git a/docker/etc/caddy/Caddyfile b/docker/etc/caddy/Caddyfile
index 03177611..60f7beb6 100644
--- a/docker/etc/caddy/Caddyfile
+++ b/docker/etc/caddy/Caddyfile
@@ -1,26 +1,32 @@
app.test {
+
log {
+ format console
+ level INFO
output file /var/log/caddy/caddy-access.log
}
- log {
- output file /var/log/caddy/caddy-error.log
- level ERROR
+ @reverb_ws {
+ path_regexp ^/(app|apps)/.*
+ header Connection *Upgrade*
+ header Upgrade websocket
}
@reverb_ws path_regexp ^/(app|apps)/.*
- reverse_proxy @reverb_ws ws:6001 {
- header_up Host {host}
- header_up X-Forwarded-For {remote}
- header_up X-Forwarded-Proto {scheme}
- }
+ reverse_proxy @reverb_ws ws:6001
- reverse_proxy app:8080 {
- header_up X-Forwarded-For {remote}, 127.0.0.1
- header_up X-Real-IP {remote}
- header_up X-Forwarded-Proto {scheme}
- header_up Host {host}
- }
+ # reverse_proxy @reverb_ws ws:6001 {
+ # header_up X-Forwarded-For {remote}
+ # header_up X-Forwarded-Proto {scheme}
+ # }
+
+ reverse_proxy app:8080
+
+ # reverse_proxy app:8080 {
+ # header_up X-Forwarded-For {remote}, 127.0.0.1
+ # header_up X-Real-IP {remote}
+ # header_up X-Forwarded-Proto {scheme}
+ # }
encode gzip