Jump to content

fix: lookup not working


tomassasovsky
Go to solution Solved by Luke,

Recommended Posts

tomassasovsky

Lookup works inconsistently. My setup is:

- Emby Server running on TrueNas Scale.
- Emby Theater is connected to the server, running on Windows 11.

Lookup also doesn't work consistently if I pause the video. It's really buggy.

Edited by tomassasovsky
Link to comment
Share on other sites

tomassasovsky

Any updates on this?

It's pretty worrying that, as a paying customer, I can't even rely on the most basic funtionality that is resuming playback on a video or moving to another point in the video's timeline.

Link to comment
Share on other sites

tomassasovsky

Another thing to note is, I was not able to reproduce this with Emby for Android. It does happen on both the web app and Emby Theater (Windows 11)

@Luke

Edited by tomassasovsky
Link to comment
Share on other sites

tomassasovsky

I've identified the issue:
This error occurs if I connect through my domain where I host my Emby server. However, I don't encounter this issue if I connect directly to the local IP address on my network where the server is. I think it may have something to do with the networking configuration. Here's my current config on the Network section in the Emby server:

I also have a Raspberry Pi running Nginx as a reversed proxy. Its config is pretty simple:
 

server {
  server_name mydomain.com;

  location / {
    proxy_pass http://192.168.50.55:10079/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
  }

    listen [::]:443 ssl; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/mydomain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/mydomain.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

} server {
    if ($host = mydomain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot

    server_name mydomain.com;

    listen 80;
    listen [::]:80;
    return 404; # managed by Certbot
}

 

network_1.jpg

network_2.jpg

network_3.jpg

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...