Skip to content
scryer media docs

Reverse Proxy

Reverse Proxy

Section titled “Reverse Proxy”

Weaver can run at a domain root or under a URL subpath. If you use a subpath, configure both Weaver and the proxy with the same base URL.

Docker Subpath Example

Section titled “Docker Subpath Example”

To host Weaver at a subpath like https://example.com/weaver/, add a command override:

services:
  weaver:
    image: ghcr.io/scryer-media/weaver:latest
    command: ["--config", "/config", "serve", "--port", "9090", "--base-url", "/weaver"]
    ports:
      - "9090:9090"
    volumes:
      - weaver-config:/config
      - /path/to/downloads:/downloads

Then configure your reverse proxy to forward /weaver/ to Weaver.

Good Defaults

Section titled “Good Defaults”
  • Preserve the /weaver base path end to end.
  • Terminate TLS at the proxy.
  • Keep WebSocket support enabled if your proxy requires it explicitly.
  • Keep /graphql, /graphql/ws, assets, and app routes under the same base path.
  • Keep /metrics private unless it is intentionally exposed to your monitoring system.

Troubleshooting

Section titled “Troubleshooting”
  • Missing CSS or JavaScript usually means the base URL and proxy path disagree.
  • Broken live updates usually means WebSocket forwarding is missing.
  • Login or API failures can indicate that headers or path rewriting changed the request seen by Weaver.