DrCornelius 1 Posted April 3, 2019 Share Posted April 3, 2019 (edited) I'm having problems with Emby connect, I have a pfSense server that has let's encrypt on it and I'm using it as a reverse proxy, before 4.x I didn't have any problems and now I can only connect directly using my DDNS. GET https://connect.emby.media/service/servers?userId=--SECRET-- HTTP/1.1 Host: connect.emby.media Connection: keep-alive X-Application: Emby Mobile/4.1.0.18 accept: application/json Origin: https://app.emby.media X-Connect-UserToken: --SECRET-- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 DNT: 1 Referer: https://app.emby.media/ Accept-Encoding: gzip, deflate, br HTTP/1.1 200 OK Server: nginx Date: Wed, 03 Apr 2019 13:01:51 GMT Content-Type: text/html Content-Length: 285 Connection: keep-alive Keep-Alive: timeout=60 X-Powered-By: PHP/5.5.9-1ubuntu4.22 Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Content-Type, Range, X-Connect-Token, X-Connect-UserToken, X-Application Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS Vary: Accept-Encoding [{"Id":"--SECRET--","Url":"https:\/\/--DDNS--:--EXT-PORT--","Name":"Media server","SystemId":"--SECRET--","AccessKey":"--SECRET--","LocalAddress":"http:\/\/--LOCAL-IP--:8096","UserType":"Linked","SupporterKey":""}] 2019-04-03 15:01:52.013 Info HttpServer: HTTP GET http://--DDNS--:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 2019-04-03 15:01:52.051 Info HttpServer: HTTP Response 200 to --SECRET--. Time: 38ms. http://--DDNS--:8096/emby/system/info/public 2019-04-03 15:01:59.770 Info HttpServer: HTTP GET http://--DDNS--:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 2019-04-03 15:01:59.772 Info HttpServer: HTTP Response 200 to --SECRET--. Time: 2ms. http://--DDNS--:8096/emby/system/info/public Edited April 4, 2019 by DrCornelius 1 Link to comment Share on other sites More sharing options...
Luke 37317 Posted April 3, 2019 Share Posted April 3, 2019 Can you please describe the problem that you're having? Link to comment Share on other sites More sharing options...
DrCornelius 1 Posted April 3, 2019 Author Share Posted April 3, 2019 I can't connect anymore after the update from 3.x to 4.x, when I try to connect using Emby connect I get the error: "We're unable to connect to the selected server right now. Please ensure it is running and try again.". Link to comment Share on other sites More sharing options...
Luke 37317 Posted April 3, 2019 Share Posted April 3, 2019 Does your server dashboard display the correct local and remote address? Link to comment Share on other sites More sharing options...
DrCornelius 1 Posted April 3, 2019 Author Share Posted April 3, 2019 (edited) Yes, and I can connect directly! I have another Emby on the same server, same proxy config and it works, the updated one doesn't. I'm having problems with Emby connect, I have a pfSense server that has let's encrypt on it and I'm using it as a reverse proxy, before 4.x I didn't have any problems and now I can only connect directly using my DDNS. GET https://connect.emby.media/service/servers?userId=--SECRET-- HTTP/1.1 Host: connect.emby.media Connection: keep-alive X-Application: Emby Mobile/4.1.0.18 accept: application/json Origin: https://app.emby.media X-Connect-UserToken: --SECRET-- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 DNT: 1 Referer: https://app.emby.media/ Accept-Encoding: gzip, deflate, br HTTP/1.1 200 OK Server: nginx Date: Wed, 03 Apr 2019 13:01:51 GMT Content-Type: text/html Content-Length: 285 Connection: keep-alive Keep-Alive: timeout=60 X-Powered-By: PHP/5.5.9-1ubuntu4.22 Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Content-Type, Range, X-Connect-Token, X-Connect-UserToken, X-Application Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS Vary: Accept-Encoding [{"Id":"--SECRET--","Url":"https:\/\/--DDNS--:--EXT-PORT--","Name":"Media server","SystemId":"--SECRET--","AccessKey":"--SECRET--","LocalAddress":"http:\/\/--LOCAL-IP--:8096","UserType":"Linked","SupporterKey":""}] 2019-04-03 15:01:52.013 Info HttpServer: HTTP GET http://--DDNS--:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 2019-04-03 15:01:52.051 Info HttpServer: HTTP Response 200 to --SECRET--. Time: 38ms. http://--DDNS--:8096/emby/system/info/public 2019-04-03 15:01:59.770 Info HttpServer: HTTP GET http://--DDNS--:8096/emby/system/info/public. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 2019-04-03 15:01:59.772 Info HttpServer: HTTP Response 200 to --SECRET--. Time: 2ms. http://--DDNS--:8096/emby/system/info/public Edited April 4, 2019 by DrCornelius Link to comment Share on other sites More sharing options...
Luke 37317 Posted April 4, 2019 Share Posted April 4, 2019 Is this still happening? Link to comment Share on other sites More sharing options...
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