[Bug] mkvtoolnix browser UI failure about docker-mkvtoolnix HOT 7 CLOSED

Could you share a screenshot of what the browser is displaying ?

Do you have the same behaviour in a private/incognito window ?

from docker-mkvtoolnix.

Yeah, behaviour is the same, not depends on browser or regular/private mode

Screen here: first it's just grey screen, then appears label "failed to connect" (after ~1 minute)

Inspect code shows the same html as if I call this page via curl from ubuntu terminal

from docker-mkvtoolnix.

Are you accessing the container directly via the IP of the device running the container (not through a reverse proxy)?

from docker-mkvtoolnix.

Using browser yes, I'm hosting behind nginx. But if I call localhost:5800 via curl - I got same html. Or it's correct behaviour for such call and nginx can be a problem here?

My nginx flow: VPS with domain and certificate from certbot -> call to my NAS via ip:port (NAS have no domain, so I use self-signed certificate). Another services like standalone gitlab, grafana and so on are working correctly, maybe I need to set up correctly my location to toolnix container?

nginx config on NAS is here:

map $http_upgrade $connection_upgrade {
        default upgrade;
        ''      close;
}

upstream docker-mkvtoolnix {
        server 127.0.0.1:5800;
}

server {
        listen 443 ssl;
        listen [::]:443 ssl;

        ssl_certificate /etc/nginx/nginx-selfsigned.crt;
        ssl_certificate_key /etc/nginx/nginx-selfsigned.key;

        server_name _;

        proxy_set_header Host $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;

        location /toolnix/ {
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $connection_upgrade;
                proxy_read_timeout 86400;
                rewrite ^/toolnix/(.*)$ /$1 break;
                proxy_pass http://docker-mkvtoolnix;
        }
}

from docker-mkvtoolnix.

The HTML might be the same, but Javascript will do dynamic stuff. I suspect that the websocket connection it tries to establish doesn't work.

You can look at https://github.com/jlesage/docker-mkvtoolnix#reverse-proxy for example configuration. I think you don't have the websocket support.

from docker-mkvtoolnix.

well, the problem was in second nginx behind first nginx (in flow I described above), I added websocket settings on NAS, but forgot to do the same on proxy. thank you for help!

from docker-mkvtoolnix.

Great, happy to see that you found the issue!

from docker-mkvtoolnix.