shackbill 21 Posted May 2 Share Posted May 2 I just built a backup server in a cloud account i have. I have no problem connecting and managing it from inside my LAN from my desktop computer but if i try to connect using an app on my iPhone or Samsung TV i get a CANT REACH SERVER error. Ive also tried to turn off the wifi on my iPhOne and connect thru cellular and i get the same error. I turned on debug on the logs to see if it was attempting a connect but i dont see anything. Any ideas on what else i should check this seems like a very basic issue but i cant think of what im doing wrong. embyserver.txt Link to comment Share on other sites More sharing options...
Luke 37233 Posted May 2 Share Posted May 2 Hi, have you setup https for your emby server? if yes, then the Samsung TV could be rejecting your certificate. It is very picky about what certificates it will accept. Link to comment Share on other sites More sharing options...
shackbill 21 Posted May 2 Author Share Posted May 2 (edited) yea and i didnt really have a choice as the 'APPBOX' preconfigured everything. but it is a LETSENCRYPT cert and looks good. see attach. Also as i mentioned earlier the same problem exists if i try to connect using my iPhone app. Edited May 2 by shackbill Link to comment Share on other sites More sharing options...
Luke 37233 Posted May 2 Share Posted May 2 It could be the same reason for both. I'm surprised to hear that about the iPhone, but i can tell you that Samsung TV's will definitely not accept LetsEncrypt. In fact your choices are pretty limited. Some users have reported success with ZeroSSL and others with Digicert. This is of course, assuming you entered the correct address and port into the apps, so I would double check that as well. Link to comment Share on other sites More sharing options...
Lessaj 81 Posted May 2 Share Posted May 2 (edited) How exactly are you connecting to the server using your phone or TV? EDIT: +1 for ZeroSSL I switched to it from LetsEncrypt when I was having issues on my LG TV, if I recall it had something to do with the root CA being cross signed. It's been a while. Though I suspect that you don't have much choice in the matter because this is being handled by a reverse proxy and is a wild card certificate, so probably your server provider is using this. Edited May 2 by Lessaj Link to comment Share on other sites More sharing options...
shackbill 21 Posted May 2 Author Share Posted May 2 (edited) i use a LETSENCRYPT on my home server and my sammies accept it just fine. this error doesnt really appear to be something that a cert would give. see screenshot Edited May 2 by shackbill Link to comment Share on other sites More sharing options...
Solution Lessaj 81 Posted May 2 Solution Share Posted May 2 You need to use port 443. 1 Link to comment Share on other sites More sharing options...
Luke 37233 Posted May 2 Share Posted May 2 Quote i use a LETSENCRYPT on my home server and my sammies accept it just fine. I'm glad to hear that. Just be aware that historically it hasn't worked so you can't assume it will for all Samsung's. Link to comment Share on other sites More sharing options...
shackbill 21 Posted May 2 Author Share Posted May 2 (edited) DOH! i just now saw that issue.. i was looking HERE: (see attch) and not paying attention to thenetwork condig, Edited May 2 by shackbill Link to comment Share on other sites More sharing options...
shackbill 21 Posted May 2 Author Share Posted May 2 (edited) im getting same error. smh. NVM fat fingered. working now. thanks. Edited May 2 by shackbill 1 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