rodainas 188 Posted July 10, 2021 Share Posted July 10, 2021 (edited) Then make it simpler again no nginx, now no cloudfare, no domain name Just you, your router, and emby server So publicip:publicembyport Edited July 10, 2021 by rodainas 1 Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 10, 2021 Share Posted July 10, 2021 Just now, rodainas said: Then make it simpler again no nginx, now no cloudfare, no domain name Just you, your router, and emby server Yes, Step by step is always a good idea. When one configuration works, then we test the next. 1 Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 10, 2021 Author Share Posted July 10, 2021 1 minute ago, rodainas said: Then make it simpler again no nginx, now no cloudfare, no domain name Just you, your router, and emby server So publicip:publicembyport Still no dice. Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 10, 2021 Author Share Posted July 10, 2021 Well the Emby ports aren't forwarded anymore, because I changed the port forwarding settings in the router to forward 80 to 80 and 443 to 443, because that's what was in the NGINX config. So it not working is correct, if you think about it that way. Link to comment Share on other sites More sharing options...
rodainas 188 Posted July 10, 2021 Share Posted July 10, 2021 You need to forward your public emby ports to the local machine running emby 1 Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 10, 2021 Share Posted July 10, 2021 (edited) 7241 to 8096 And test: http://yourip:7241 - should work http;//yourip:8096 - should not work Edited July 10, 2021 by vdatanet 1 Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 10, 2021 Author Share Posted July 10, 2021 28 minutes ago, vdatanet said: 7241 to 8096 And test: http://yourip:7241 - should work http;//yourip:8096 - should not work Both work. On 7241 I get the Guest account, and options to manually log in or reset my password. On 8096 it takes me directly to the manual login screen. Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 10, 2021 Author Share Posted July 10, 2021 The serverId string is different on each port, for the record. This is the result of entering RemoteIp:port in the address bar, nothing else. The Guest account has all the "hide this user" options disabled. So the 7241 result is what should happen, I have no idea why 8096 is enforcing manual login. Also no idea why the server IDs are different. Link to comment Share on other sites More sharing options...
rodainas 188 Posted July 10, 2021 Share Posted July 10, 2021 4 minutes ago, crusher11 said: Both work. On 7241 I get the Guest account, and options to manually log in or reset my password. On 8096 it takes me directly to the manual login screen. The difference on screens should be cookies. Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 10, 2021 Share Posted July 10, 2021 Next step is block port 8096 on router's firewall. I don't know why because port is not forwarded. Here is the manual: https://fccid.io/TE7C7/User-Manual/TempConfidential-User-Man-TE7C7-rev-3-2015834 Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 10, 2021 Share Posted July 10, 2021 My question is: If port 8096 is not forwaded in router why does it work? 1 Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 10, 2021 Author Share Posted July 10, 2021 9 minutes ago, rodainas said: The difference on screens should be cookies. In an incognito window? Link to comment Share on other sites More sharing options...
rodainas 188 Posted July 10, 2021 Share Posted July 10, 2021 (edited) 22 minutes ago, vdatanet said: My question is: If port 8096 is not forwaded in router why does it work? The same happened with my vps, I just blocket it. But the difference is with the vps there is no router just the machine with the public ip address, so no router to map or forward anything. Comes to my mind, any possibility the emby server is on DMZ? Edited July 10, 2021 by rodainas Link to comment Share on other sites More sharing options...
GrimReaper 3322 Posted July 10, 2021 Share Posted July 10, 2021 (edited) 51 minutes ago, crusher11 said: Also no idea why the server IDs are different. Do you have a rogue server instance running somewhere? What does device.txt from the Emby-Server/programdata/data folder show you? What is the string inside (that would be your serverId)? And did you try to actually login to that 8096 one? Edit: To clarify, that seem suspicious like another instance with default settings and UPnP enabled; since it is on another port, it will happily co-exist with your main server. Edited July 10, 2021 by GrimReaper76 Append 1 Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 11, 2021 Share Posted July 11, 2021 Disable automatic port forwarding in Emby, even better, turn it off on your router Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 11, 2021 Author Share Posted July 11, 2021 Ooh. I set up a test instance on my Shield. Couldn't ever find the app in my apps list so I couldn't uninstall it. Wonder if that's it. Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 11, 2021 Author Share Posted July 11, 2021 Yep. Uninstalled the Shield server and 8096 now fails. Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 11, 2021 Share Posted July 11, 2021 (edited) In my opinion, the next step is to set up cloudflare (first without nginx) In your router, set: emby's public port to emby's private (non ssl and ssl) Setup your cloudflare domain Edited July 11, 2021 by vdatanet Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 11, 2021 Author Share Posted July 11, 2021 How do I find Emby's private ports? Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 11, 2021 Share Posted July 11, 2021 1 minute ago, crusher11 said: How do I find Emby's private ports? Sorry, local. Default are 8096 and 8920. So you need 7241 to 8096 and 4343 to 8920 Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 11, 2021 Author Share Posted July 11, 2021 1 minute ago, vdatanet said: Sorry, local. Default are 8096 and 8920. So you need 7241 to 8096 and 4343 to 8920 The domain still redirects to port 5000. Link to comment Share on other sites More sharing options...
rodainas 188 Posted July 11, 2021 Share Posted July 11, 2021 1 minute ago, crusher11 said: The domain still redirects to port 5000. 7241 and 4343 You are using non standard ports Try http://domainname.com:7241 or https://domainname.com:4343 1 Link to comment Share on other sites More sharing options...
vdatanet 1549 Posted July 11, 2021 Share Posted July 11, 2021 1 minute ago, crusher11 said: The domain still redirects to port 5000. Test this: Set Emby's public ports to 80 and 443 Set router forwading 80 to 8096 and 443 to 8920 1 Link to comment Share on other sites More sharing options...
crusher11 856 Posted July 11, 2021 Author Share Posted July 11, 2021 2 minutes ago, rodainas said: 7241 and 4343 You are using non standard ports Try http://domainname.com:7241 or https://domainname.com:4343 7241 works, 4343 doesn't. Link to comment Share on other sites More sharing options...
rodainas 188 Posted July 11, 2021 Share Posted July 11, 2021 1 minute ago, crusher11 said: 7241 works, 4343 doesn't. Whats the error for 4343? 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