Closed joinso closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
looks like whatever reverse proxy you use doesnt properly support websockets. It works fine with ours.
Hi! I solved doing this: In /etc/nginx/sites-enabled I just add this file: digikam.conf: server { listen 443 ssl; listen [::]:443 ssl;
server_name YOUR_DOMAIN;
if ( $host !~ "(^YOUR_DOMAIN$)" ) { return 404; }
include /usr/syno/etc/www/certificate/ReverseProxy_713c2ab0-3816-48b9-b34c-1dca2e567ecc/cert.conf*;
include /usr/syno/etc/security-profile/tls-profile/config/ReverseProxy_713c2ab0-3816-48b9-b34c-1dca2e567ecc.conf*;
add_header Strict-Transport-Security "max-age=15768000; includeSubdomains; preload" always;
proxy_ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
location / {
proxy_connect_timeout 60;
proxy_read_timeout 60;
proxy_send_timeout 60;
proxy_intercept_errors off;
proxy_http_version 1.1;
proxy_set_header Cross-Origin-Embedder-Policy require-corp;
proxy_set_header Cross-Origin-Opener-Policy same-origin;
proxy_set_header Cross-Origin-Resource-Policy same-site;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass https://localhost:3001;
}
location /websockify {
proxy_pass https://localhost:3001;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
location /vnc {
proxy_pass https://localhost:3001;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
error_page 403 404 500 502 503 504 /dsm_error_page;
location /dsm_error_page {
internal;
root /usr/syno/share/nginx;
rewrite (.*) /error.html break;
allow all;
}
} But there is still and issue with "lastActivity": When timeout fires, it show this error:
Uncaught TypeError: Cannot read properties of undefined (reading 'lastActiveAt') in: https://MY_DOMAIN/vnc/dist/main.bundle.js:22919:61
TypeError: Cannot read properties of undefined (reading 'lastActiveAt') at https://MY_DOMAIN/vnc/dist/main.bundle.js:22919:61
Any idea?
Regards, Jordi
Unfortunately, we do not support reverse proxies other than our own. Further, this github issue section is specifically for digikam, not whatever reverse proxy you're using.
Is there an existing issue for this?
Current Behavior
Digikam not showing when using under a reverse proxy domain.
Expected Behavior
Show Digikam using VNC.
Steps To Reproduce
1.- Setup a proxy reverse that points mydomain.tld:443 to localhost:3000 2.- When we visit https://mydomain.tld:443, VNC is loaded but it shows this error:
noVNC encountered an error: TypeError : UI.rfb is undefined.
And in browser console, a lot of connection errors are shown:
Firefox can’t establish a connection to the server at ws://mydomain.tld/audio/socket.io/?EIO=4&transport=websocket&sid=6QcJUJldSGp7dbD1AAAc. websocket.js:44:26 Firefox can’t establish a connection to the server at ws://mydomain.tld/websockify. main.bundle.js:13489:18 WebSocket on-error event main.bundle.js:16523:14 Failed when connecting: Connection closed (code: 1006) main.bundle.js:17981:24 Firefox can’t establish a connection to the server at ws://mydomain.tld/files/socket.io/?EIO=4&transport=websocket&sid=DO_x8LFbgoRLDiy0AAAe. websocket.js:44:26 Uncaught TypeError: UI.rfb is undefined _sessionTimeoutInterval http://mydomain.tld/vnc/dist/main.bundle.js:22629
Environment
CPU architecture
x86-64
Docker creation
Container logs