Hi
Hamclock Version 26.5.0
Server:
Raspberry Pi 4
Debian 1:6.12.75-1+rpt1
Debian GNU/Linux 13 (trixie) (13.5)
Connecting to the server via Chrome running on Windows 11 across the LAN but using the public FQDN.
I use a connection to my own DX Cluster via telnet. Since the latest upgrade the login has reverted to just callsign with no addition. As my own callsign requires a password this prevents the server from connecting. The following settings are set in .env but are not being read at the browser.
SETTINGS_SYNC=true
DX_CLUSTER_SOURCE=dxspider
DX_CLUSTER_HOST=dxc.m0mhx.uk
DX_CLUSTER_PORT=7300
DX_CLUSTER_CALLSIGN=M0MHX-56
Console errors from Chrome below:
(index):1 The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/#potentially-trustworthy-origin and https://html.spec.whatwg.org/#the-cross-origin-opener-policy-header.
(index):1 The page requested an origin-keyed agent cluster using the Origin-Agent-Cluster header, but could not be origin-keyed since the origin 'http://hamclock.m0mhx.uk:3001' had previously been placed in a site-keyed agent cluster. Update your headers to uniformly request origin-keying for all pages on the origin.
index-BJo93mdE.js:9 🌐 i18next is maintained with support from locize.com — consider powering your project with managed localization (AI, CDN, integrations): https://locize.com 💙
vendor-MEG3rvtw.js:29 [Deprecation] The keyword 'slider-vertical' specified to an 'appearance' property is not standardized. It will be removed in the future. Use instead.
Di @ vendor-MEG3rvtw.js:29
:3001/api/presence:1 Failed to load resource: the server responded with a status of 429 (Too Many Requests)
index-BJo93mdE.js:1277 [usePropagation] WASM engine unavailable, falling back to REST/EST. Self-hosters: run "node scripts/fetch-wasm.js && npm run build" to install the WASM bundle. (Cannot read properties of undefined (reading 'digest'))
Lots more items relating to digest deleted but can send if required.
73
Nick, M0MHX
Hi
Hamclock Version 26.5.0
Server:
Raspberry Pi 4
Debian 1:6.12.75-1+rpt1
Debian GNU/Linux 13 (trixie) (13.5)
Connecting to the server via Chrome running on Windows 11 across the LAN but using the public FQDN.
I use a connection to my own DX Cluster via telnet. Since the latest upgrade the login has reverted to just callsign with no addition. As my own callsign requires a password this prevents the server from connecting. The following settings are set in .env but are not being read at the browser.
SETTINGS_SYNC=true
DX_CLUSTER_SOURCE=dxspider
DX_CLUSTER_HOST=dxc.m0mhx.uk
DX_CLUSTER_PORT=7300
DX_CLUSTER_CALLSIGN=M0MHX-56
Console errors from Chrome below:
(index):1 The Cross-Origin-Opener-Policy header has been ignored, because the URL's origin was untrustworthy. It was defined either in the final response or a redirect. Please deliver the response using the HTTPS protocol. You can also use the 'localhost' origin instead. See https://www.w3.org/TR/powerful-features/#potentially-trustworthy-origin and https://html.spec.whatwg.org/#the-cross-origin-opener-policy-header.
(index):1 The page requested an origin-keyed agent cluster using the Origin-Agent-Cluster header, but could not be origin-keyed since the origin 'http://hamclock.m0mhx.uk:3001' had previously been placed in a site-keyed agent cluster. Update your headers to uniformly request origin-keying for all pages on the origin.
index-BJo93mdE.js:9 🌐 i18next is maintained with support from locize.com — consider powering your project with managed localization (AI, CDN, integrations): https://locize.com 💙
vendor-MEG3rvtw.js:29 [Deprecation] The keyword 'slider-vertical' specified to an 'appearance' property is not standardized. It will be removed in the future. Use instead.
Di @ vendor-MEG3rvtw.js:29
:3001/api/presence:1 Failed to load resource: the server responded with a status of 429 (Too Many Requests)
index-BJo93mdE.js:1277 [usePropagation] WASM engine unavailable, falling back to REST/EST. Self-hosters: run "node scripts/fetch-wasm.js && npm run build" to install the WASM bundle. (Cannot read properties of undefined (reading 'digest'))
Lots more items relating to digest deleted but can send if required.
73
Nick, M0MHX