CBers 7114 Posted January 24, 2018 Posted January 24, 2018 I have seen Emby adding in the local port instead of the external port to requests when requesting a playback item through the web app. So, there is actually no problem here, correct? @@ebr - possibly an Emby error then with the local port being added to calls? Could be erroneous, but worth checking?
Swynol 375 Posted January 24, 2018 Author Posted January 24, 2018 trying to navigate to the address in the logs doesnt work as that port is blocked on my router/firewall. But in the logs it gets a HTTP 200 code and all works. so just a display bug. 1
Luke 40075 Posted January 24, 2018 Posted January 24, 2018 @@ebr - possibly an Emby error then with the local port being added to calls? Could be erroneous, but worth checking? All it's doing is logging the full url that is coming in.
CBers 7114 Posted January 24, 2018 Posted January 24, 2018 All it's doing is logging the full url that is coming in. Then it's wrong. It should be the https port, not the local port. 1
tidusjar 55 Posted January 24, 2018 Posted January 24, 2018 Just to confirm with the port thing. Ombi will connect to emby via the port provided by the user. There is no code that will use 8096 unless provided by the user. The only thing I can think of is that it's possible that nginx is doing something strange and messing with the HttpContext Current URL? (If that's how you are getting the request URL). Or there might be a bug in emby? I do not know where the problem lies. 1
CBers 7114 Posted January 24, 2018 Posted January 24, 2018 Ok So does that mean you're going to fix it, or ignore it?
Luke 40075 Posted January 24, 2018 Posted January 24, 2018 I don't believe there is anything to fix. That's just how emby server is seeing the url.
CBers 7114 Posted January 24, 2018 Posted January 24, 2018 I don't believe there is anything to fix. That's just how emby server is seeing the url. Then it's a bug in Emby, as Tidusjar has stated that Ombi doesn't even know about that port. Something is wrong somewhere.
pir8radio 1305 Posted January 25, 2018 Posted January 25, 2018 Then it's a bug in Emby, as Tidusjar has stated that Ombi doesn't even know about that port. Something is wrong somewhere. its' probably related to nginx. It's not how nginx is doing things... it's just how emby logs the requests.... Emby web server doesn't respect some http headers... Emby is building that GET/POST log entry using some kind of program logic, like (requested_protocol)+(host_header)+(requested_port)+(path) The below path isn't even possible My nginx won't accept http and i have no port 8080 open on my firewall. what the real request looks like is https://guest.mydomain.com/emby 2018-01-23 19:19:21.252 Info HttpServer: HTTP GET http://guest.mydomain.com:8080/emby/ anyway this only affects reverse proxy users, and it's only wrong in the logs... the real GET/POST commands are coming and going with the correct URL. 1
damelloman 0 Posted October 14, 2019 Posted October 14, 2019 I have a reverse proxy (HAproxy) as well and I get similar logs. I have a few plugins installed but pretty must what comes default with Emby. Not really an issue. Rather more of a "What's this?" kinda thing. 2019-10-14 09:21:27.873 Info HttpServer: HTTP Response 200 to GATEWAY. Time: 1ms. http://[::ffff:LocalEmbyServer]:8096/ 2019-10-14 09:21:28.892 Info HttpServer: HTTP OPTIONS http://[::ffff:LocalEmbyServer]:8096/. UserAgent: 2019-10-14 09:21:28.893 Info HttpServer: HTTP Response 200 to GATEWAY. Time: 1ms. http://[::ffff:LocalEmbyServer]:8096/ 2019-10-14 09:21:29.921 Info HttpServer: HTTP OPTIONS http://[::ffff:LocalEmbyServer]:8096/. UserAgent: 2019-10-14 09:21:29.922 Info HttpServer: HTTP Response 200 to GATEWAY. Time: 1ms. http://[::ffff:LocalEmbyServer]:8096/ 2019-10-14 09:21:30.933 Info HttpServer: HTTP OPTIONS http://[::ffff:LocalEmbyServer]:8096/. UserAgent: 2019-10-14 09:21:30.934 Info HttpServer: HTTP Response 200 to GATEWAY. Time: 1ms. http://[::ffff:LocalEmbyServer]:8096/ 2019-10-14 09:21:31.948 Info HttpServer: HTTP OPTIONS http://[::ffff:LocalEmbyServer]:8096/. UserAgent: 2019-10-14 09:21:31.949 Info HttpServer: HTTP Response 200 to GATEWAY. Time: 1ms. http://[::ffff:LocalEmbyServer]:8096/ 2019-10-14 09:21:32.971 Info HttpServer: HTTP OPTIONS http://[::ffff:LocalEmbyServer]:8096/. UserAgent: 2019-10-14 09:21:32.972 Info HttpServer: HTTP Response 200 to GATEWAY. Time: 1ms. http://[::ffff:LocalEmbyServer]:8096/ 2019-10-14 09:21:33.978 Info HttpServer: HTTP OPTIONS http://[::ffff:LocalEmbyServer]:8096/. UserAgent: 2019-10-14 09:21:33.979 Info HttpServer: HTTP Response 200 to GATEWAY. Time: 1ms. http://[::ffff:LocalEmbyServer]:8096/ 2019-10-14 09:21:34.985 Info HttpServer: HTTP OPTIONS http://[::ffff:LocalEmbyServer]:8096/. UserAgent:
Luke 40075 Posted October 14, 2019 Posted October 14, 2019 Those are options requests to get cors information.
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now