Is there an existing issue for this?
Current Behavior
When trying to access Calibre using Synology's Quick Connect (using my own domain), I would get an error:
KasmVNC encountered an error: TypeError: undefined is not an object (evaluating 'UI.rfb.lastActiveAt')
However, when I try accessing Calibre using my local IP, it opens just fine.
This only just recently started happening. I didn't have an issue a couple weeks ago.
I should mention that Calibre Web is still working fine.
Expected Behavior
Calibre should open without error regardless of whether I use my registered domain or local IP address.
Steps To Reproduce
I enter the URL to the docker container.
Environment
- OS: Synology DSM
- How docker service was installed: I used Container Manager
CPU architecture
x86-64
Docker creation
Container logs
date stream content
2025/02/27 16:15:29 stdout 2025-02-27 16:15:29,899 [PRIO] Connections: accepted: @172.17.0.1_1740633329.880952::websocket
2025/02/27 16:15:29 stdout 2025-02-27 16:15:29,880 [INFO] websocket 0: got client connection from 127.0.0.1
2025/02/27 16:15:27 stdout qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
2025/02/27 16:15:22 stdout Obt-Message: Xinerama extension is not present on the server
2025/02/27 16:15:22 stdout [mi] mieq: warning: overriding existing handler (nil) with 0x557d2c55e930 for event 3
2025/02/27 16:15:22 stdout [mi] mieq: warning: overriding existing handler (nil) with 0x557d2c55e930 for event 2
2025/02/27 16:15:22 stdout [ls.io-init] done.
2025/02/27 16:15:22 stdout Errors from xkbcomp are not fatal to the X server
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86NavInfo
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86SidevuSonar
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86ClearvuSonar
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86TraditionalSonar
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86RadarOverlay
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86DualRangeRadar
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86SingleRangeRadar
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86FishingChart
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86NavChart
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86Sos
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86MarkWaypoint
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86AutopilotEngageToggle
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86PreviousElement
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86NextElement
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86CameraAccessToggle
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86CameraAccessDisable
2025/02/27 16:15:22 stdout > Warning: Could not resolve keysym XF86CameraAccessEnable
2025/02/27 16:15:22 stdout The XKEYBOARD keymap compiler (xkbcomp) reports:
2025/02/27 16:15:22 stdout 19
2025/02/27 16:15:22 stdout
2025/02/27 16:15:22 stdout Underlying X server release 12101012
2025/02/27 16:15:22 stdout See http://kasmweb.com for information on KasmVNC.
2025/02/27 16:15:22 stdout Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
2025/02/27 16:15:22 stdout Xvnc KasmVNC 1.3.3 - built Feb 22 2025 19:05:16
2025/02/27 16:15:22 stdout
2025/02/27 16:15:22 stdout _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
2025/02/27 16:15:22 stdout [custom-init] No custom files found, skipping...
2025/02/27 16:15:21 stdout
2025/02/27 16:15:21 stdout ───────────────────────────────────────
2025/02/27 16:15:21 stdout Build-date: 2025-02-26T06:41:34+00:00
2025/02/27 16:15:21 stdout Linuxserver.io version: v7.26.0-ls324
2025/02/27 16:15:21 stdout ───────────────────────────────────────
2025/02/27 16:15:21 stdout User GID: 100
2025/02/27 16:15:21 stdout User UID: 1027
2025/02/27 16:15:21 stdout
2025/02/27 16:15:21 stdout ───────────────────────────────────────
2025/02/27 16:15:21 stdout GID/UID
2025/02/27 16:15:21 stdout ───────────────────────────────────────
2025/02/27 16:15:21 stdout
2025/02/27 16:15:21 stdout https://www.linuxserver.io/donate/
2025/02/27 16:15:21 stdout To support LSIO projects visit:
2025/02/27 16:15:21 stdout
2025/02/27 16:15:21 stdout ───────────────────────────────────────
2025/02/27 16:15:21 stdout Brought to you by linuxserver.io
2025/02/27 16:15:21 stdout
2025/02/27 16:15:21 stdout ╚══════╝╚══════╝╚═╝ ╚═════╝
2025/02/27 16:15:21 stdout ███████╗███████║██║╚██████╔╝
2025/02/27 16:15:21 stdout ██║ ╚════██║██║██║ ██║
2025/02/27 16:15:21 stdout ██║ ███████╗██║██║ ██║
2025/02/27 16:15:21 stdout ██║ ██╔════╝██║██╔═══██╗
2025/02/27 16:15:21 stdout ██╗ ███████╗██╗ ██████╗
2025/02/27 16:15:21 stdout
2025/02/27 16:15:21 stdout ───────────────────────────────────────
2025/02/27 16:15:21 stdout usermod: no changes
2025/02/27 16:15:21 stdout [migrations] no migrations found
2025/02/27 16:15:21 stdout [migrations] started
2025/02/27 16:06:33 stdout The X11 connection broke (error 1). Did the X11 server die?
2025/02/27 16:06:33 stdout X connection to :1 broken (explicit kill or server shutdown).
2025/02/27 16:06:33 stdout 2025-02-27 16:06:33,194 [PRIO] Connections: closed: @172.17.0.1_1740632368.750008::websocket (Clean disconnection)
2025/02/27 15:59:28 stdout 2025-02-27 15:59:28,767 [PRIO] Connections: accepted: @172.17.0.1_1740632368.750008::websocket
2025/02/27 15:59:28 stdout 2025-02-27 15:59:28,749 [INFO] websocket 1: got client connection from 127.0.0.1
2025/02/27 15:59:27 stdout 2025-02-27 15:59:27,968 [PRIO] Connections: closed: @172.17.0.1_1740631517.183735::websocket (Clean disconnection)
2025/02/27 15:45:17 stdout 2025-02-27 15:45:17,202 [PRIO] Connections: accepted: @172.17.0.1_1740631517.183735::websocket
2025/02/27 15:45:17 stdout 2025-02-27 15:45:17,182 [INFO] websocket 0: got client connection from 127.0.0.1
2025/02/27 15:45:11 stdout qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
2025/02/27 15:45:04 stdout Obt-Message: Xinerama extension is not present on the server
2025/02/27 15:45:04 stdout [mi] mieq: warning: overriding existing handler (nil) with 0x564658c4c930 for event 3
2025/02/27 15:45:04 stdout [mi] mieq: warning: overriding existing handler (nil) with 0x564658c4c930 for event 2
2025/02/27 15:45:04 stdout Errors from xkbcomp are not fatal to the X server
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86NavInfo
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86SidevuSonar
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86ClearvuSonar
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86TraditionalSonar
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86RadarOverlay
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86DualRangeRadar
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86SingleRangeRadar
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86FishingChart
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86NavChart
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86Sos
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86MarkWaypoint
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86AutopilotEngageToggle
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86PreviousElement
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86NextElement
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86CameraAccessToggle
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86CameraAccessDisable
2025/02/27 15:45:04 stdout > Warning: Could not resolve keysym XF86CameraAccessEnable
2025/02/27 15:45:04 stdout The XKEYBOARD keymap compiler (xkbcomp) reports:
2025/02/27 15:45:04 stdout
2025/02/27 15:45:04 stdout Underlying X server release 12101012
2025/02/27 15:45:04 stdout See http://kasmweb.com for information on KasmVNC.
2025/02/27 15:45:04 stdout Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
2025/02/27 15:45:04 stdout Xvnc KasmVNC 1.3.3 - built Feb 22 2025 19:05:16
2025/02/27 15:45:04 stdout
2025/02/27 15:45:04 stdout _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
2025/02/27 15:45:03 stdout pa_context_connect() failed: Connection refused
2025/02/27 15:45:03 stdout Connection failure: Connection refused
2025/02/27 15:45:03 stdout pa_context_connect() failed: Connection refused
2025/02/27 15:45:03 stdout Connection failure: Connection refused
2025/02/27 15:45:03 stdout [ls.io-init] done.
2025/02/27 15:45:03 stdout [custom-init] No custom files found, skipping...
2025/02/27 15:45:02 stdout
2025/02/27 15:45:02 stdout ───────────────────────────────────────
2025/02/27 15:45:02 stdout Build-date: 2025-02-26T06:41:34+00:00
2025/02/27 15:45:02 stdout Linuxserver.io version: v7.26.0-ls324
2025/02/27 15:45:02 stdout ───────────────────────────────────────
2025/02/27 15:45:02 stdout User GID: 100
2025/02/27 15:45:02 stdout User UID: 1027
2025/02/27 15:45:02 stdout
2025/02/27 15:45:02 stdout ───────────────────────────────────────
2025/02/27 15:45:02 stdout GID/UID
2025/02/27 15:45:02 stdout ───────────────────────────────────────
2025/02/27 15:45:02 stdout
2025/02/27 15:45:02 stdout https://www.linuxserver.io/donate/
2025/02/27 15:45:02 stdout To support LSIO projects visit:
2025/02/27 15:45:02 stdout
2025/02/27 15:45:02 stdout ───────────────────────────────────────
2025/02/27 15:45:02 stdout Brought to you by linuxserver.io
2025/02/27 15:45:02 stdout
2025/02/27 15:45:02 stdout ╚══════╝╚══════╝╚═╝ ╚═════╝
2025/02/27 15:45:02 stdout ███████╗███████║██║╚██████╔╝
2025/02/27 15:45:02 stdout ██║ ╚════██║██║██║ ██║
2025/02/27 15:45:02 stdout ██║ ███████╗██║██║ ██║
2025/02/27 15:45:02 stdout ██║ ██╔════╝██║██╔═══██╗
2025/02/27 15:45:02 stdout ██╗ ███████╗██╗ ██████╗
2025/02/27 15:45:02 stdout
2025/02/27 15:45:02 stdout ───────────────────────────────────────
2025/02/27 15:45:00 stdout [migrations] no migrations found
2025/02/27 15:45:00 stdout [migrations] started
Is there an existing issue for this?
Current Behavior
When trying to access Calibre using Synology's Quick Connect (using my own domain), I would get an error:
However, when I try accessing Calibre using my local IP, it opens just fine.
This only just recently started happening. I didn't have an issue a couple weeks ago.
I should mention that Calibre Web is still working fine.
Expected Behavior
Calibre should open without error regardless of whether I use my registered domain or local IP address.
Steps To Reproduce
I enter the URL to the docker container.
Environment
CPU architecture
x86-64
Docker creation
Container logs