Replies: 1 comment
-
Double check that the Synology reverse proxy has the appropriate settings to permit websocket connections. Also, if Synology is an ARM/ARM64 device the 0.20.0 build is broken as per #826 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First Check
Homebox Version
0.20
What is the issue you are experiencing?
after updating to version 0.20, docker logs produce a lot of errors when requesting the site
ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header"
How can the maintainer reproduce the issue?
- protocol https
- hostname homebox.xxx.xxx
- port 443
- protocol http
- hostname localhost
- port 7745
Deployment
Docker (Synology)
OS Architechture
x86_64 (AMD, Intel)
Deployment Details
DSM 7.2.2-72806 Update 3
container manager(docker) 24.0.2
synology reverse proxy
`version: "3.9"
services:
homebox:
image: ghcr.io/sysadminsmedia/homebox:latest
container_name: homebox
restart: unless-stopped
environment:
- HBOX_LOG_LEVEL=info
- HBOX_LOG_FORMAT=text
- HBOX_WEB_MAX_FILE_UPLOAD=100
- HBOX_OPTIONS_ALLOW_ANALYTICS=false
- HBOX_SWAGGER_SCHEMA=https
- HBOX_DATABASE_DRIVER=sqlite3
- HBOX_LABEL_MAKER_WIDTH=576
- HBOX_LABEL_MAKER_HEIGHT=354
- HBOX_WEB_LISTEN=0.0.0.0:7745
volumes:
- /volume1/docker/homebox/data:/data/
ports:
- "127.0.0.1:7745:7745"
networks:
- default
`
Beta Was this translation helpful? Give feedback.
All reactions