-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Getting constant MKVToolNix - Disconnected in google chrome #73
Comments
Do you have the same issue in an incognito window ? With another browser ? |
Is 192.168.13.5 the IP of the machine running the container ? Are you accessing the interface via a reverse proxy or something like that ? How much time do you have to wait for the problem to appear ? |
You are correct, 192.168.13.5 is the ip of the host machine. I did that to limit the access to only that ip. I am not using any reverse proxy or anything. The time is different, sometimes is almost instant, some other times it takes a bit. The multiplexing is never interrupted though, every time I refresh, everything continues as if nothing ever happened. I think it has something to do with the VNC maybe? Because the processes continue without any issues. Do you think it may have something to do with the static ip? |
@jlesage I just tried to run this without the static ip and I am still seeing the error |
This is the exact error that happens when the app crashes:
|
Hey, sorry to bother you, but are there any updates with this issue @jlesage ?Thanks! |
You can try to activate debug logging by using the URL http://192.168.13.5:5800/?logging=debug |
Also, do you have the same behaviour accessing the container from different machines ? |
This is what I gathered from the console: I will try accessing from another machine and I will come back @jlesage |
Do you have any firewall installed ? Looks like something is closing the connection. |
Not that I am aware of. And if I have it, shouldn't it affect the other computer's behavior? Because I haven't notice that same points |
You mean that you don't see the problem when accessing the container from another computer ? |
Exactly |
Hey! Do you need anything else from my side @jlesage ? |
Sorry, since the problem seems to be one of your machine accessing the container (and not the container itself), I'm not sure what else I can do... |
Maybe the logs I sent were useful to debug the problem? |
Unfortunately, no. They show that the connection is terminated... but how and by who, I don't know. |
What OS this client machine is running ? |
The latest macos version! |
I also use MacOS without issue. Is the firewall (under Setting->Network) turned on ? |
Yes it is! |
Can you try to turn it off to see if problem persists? |
This did not make a difference |
Incoming connections are not needed for the browser, so I don't expect any impact related to this. Still, it could be other functionalities of the firewall that could impact, or another (security related?) software installed on your machine. |
Okay, I will try using another macos machine |
Just wanted to say that I tried this again on another mac computer I have (which has the firewall off) and I encountered the same problem. This might me useful @jlesage:
|
Hey @jlesage , were my logs helpful? Thanks! |
No, same thing as before: they just show that a disconnection happened. |
I am seeing similar issue from Chrome on Windows 11 and a Chromebook. Container is deployed in Synology using DSM 7 container manager. mkvtoolnix:
image: jlesage/mkvtoolnix
ports:
- "5800:5800"
volumes:
- "/volume1/docker/mkvtoolnix:/config:rw"
- "/volume1/torrents/conversions/output:/output:rw"
- "/volume1/torrents/completed:/storage:ro"
- "/volume1/EmbyMedia:/emby_media:ro"
- "/volume1/PlexMedia:/plex_media:ro"
environment:
- USER_ID=1034
- GROUP_ID=65538
- DISPLAY_WIDTH=1280
- DISPLAY_HEIGHT=720
- INSTALL_PACKAGES=jq
- SUP_GROUP_IDS=240699
- VNC_PASSWORD=[redact]
restart: unless-stopped I am using a a reverse proxy configuration in the DSM (https is using a valid LetsEncrypt cert setup in DSM Security) |
@jgeorgeson, this is most likely caused by the reverse proxy. Do you have the same problem if you access directly the container, without the reverse proxy? |
Actually I think it was a permissions problem. In adding the plex/emby media folder mounts, I had changed the UID/GID and just noticed this morning that the application was unable to access the /storage and /output mounts. I had reset the UID/GID to what I shared in my config and restarted the container before posting my comment and started working on something else. Going back to that tab now it was still connected where as before it would disconnect in just a couple minutes without interaction. I'll keep watching, and try connecting direct if it comes back. |
Logs:
|
Current Behavior
Basically the title, every now and then I get this disconnected error. I am using google chrome

Expected Behavior
The error should not appear
Steps To Reproduce
I just have to wait and the error appears
Environment
Container creation
I run everything using docker compose
Container log
Container inspect
No response
Anything else?
I used the SECURE_CONNECTION=1 because I was having issues without it at first. Then I used this (I don't know exactly how certificates work) and the error disappeared. However, I am now seeing it again.
The text was updated successfully, but these errors were encountered: