Open Aiki033 opened 5 days ago
The problem is with the reverse proxy, not this container. The reverse proxy is terminating the connection.
You can try adjusting the timeouts, by adding the following settings to the advanced section of your host in NPM:
proxy_read_timeout 3600;
proxy_send_timeout 3600;
Hi,
sadly, it did not work but thank you for pointing in the right direction. I will update if I can find a solution.
thank you.
Current Behavior
The Web UI keeps disconnecting after a few minutes of not interacting. Whenever I return to the Jdownloader TAB it is already disconnected. I noticed this happens when accessing through my domain (NPM) https://mydomain.org but not when accessing through IP address https://192.x.x.x:5800. Already tried enabling, disabling the following on NPM - websocket support, block common exploit, cache assets.
Expected Behavior
keep the Web UI connected during idle or no interaction.
Steps To Reproduce
No response
Environment
Container creation
volumes: appdata_jdownloader-2: driver: local
services: jdownloader-2: container_name: jdownloader-2 ports:
networks: default: external: true name: nixel-bridge
Container log
Container inspect
Anything else?
No response