1. Caddy version (caddy version
):
Caddy 0.11.2 (+f249158) (unofficial)
2. How I run Caddy:
Docker Compose
image: jessestuart/caddy:latest
a. System environment:
b. Command:
n/a
c. Service/unit/compose file:
caddy:
container_name: caddy
image: jessestuart/caddy:latest
restart: always
environment:
- ACME_AGREE=true
- CLOUDFLARE_EMAIL=<removed>
- CLOUDFLARE_API_KEY=<removed>
networks:
- caddy-proxy
ports:
- 443:443
- 80:80
- 8480:8480
- 8443:8443
secrets:
- cloudflare_api
- cloudflare_email
dns:
- 192.168.10.1
#- 8.8.8.8
volumes:
- ./caddy/certs:/root/.caddy
- ./caddy/srv:/srv
- ./caddy/Caddyfile:/etc/Caddyfile
d. My complete Caddyfile or JSON config:
(tls) {
tls letsencrypt@domain.com {
dns cloudflare
wildcard
}
}
https://sabnzbd.internal.domain.com {
import tls
log / stdout "Sabnzbd : {common}"
proxy / http://drogo.local:8086/ {
transparent
#websocket
insecure_skip_verify
}
}
DO NOT REDACT anything except credentials
3. The problem I’m having:
Sabnzbd has been workign fine, and is fine to access via the url https://sabznbd.internal.domain.com for my internal network (this is not exposed).
But with the update to sabnzbd linuxserio docker image) and v3.0.1 most of the site navigation is fine, until you go to the rss feed and hit the read feed button.
This is supposed to trigger a read of the rss feed and navigate to it, But wiht the update in version it does nothing anymore, and looking at the sab log it doesn’t trigger an action.
If I ignore the reverse proxy and go to the http://drogo.local:8086 directly, all works as it should.
4. Error messages and/or full log output:
No error, but the caddy log has the following when you hit that rss feed button:
Sabnzbd : 192.168.10.141 - - [29/Aug/2020:03:10:47 +0000] "POST /config/rss/test_rss_feed HTTP/2.0" 303 120