Justus 8 Posted February 18, 2021 Posted February 18, 2021 (edited) Hey, i have an issue that it isnt possible to connect external, to my server. I have not changed anything and before it worked all fine. Im running it on my Windows PC attached are the logs. Ive checked if my ports are open, and the 8096 is open, but 8920 is closed on https://portchecker.co/ even though its open in my router settings and firewall? Could it be that why i cant connect externally via browser or app? Edited February 22, 2021 by Justus
Justus 8 Posted February 18, 2021 Author Posted February 18, 2021 Tried restarting the server, the PC, the router, set up the ports again in the router settings. Why is this not working? It worked like yesterday perfectly fine, and i didnt changed anything? Ther arent new updates of the server or plugins so what is wrong?
rbjtech 5284 Posted February 18, 2021 Posted February 18, 2021 According to the log, your server is only listening on http port 8096. Have you setup a proper SSL certificate for emby ? What does the dashboard show for 'Remote (WAN) Access' - is it a https:\\a.b.c.d (or domain name) :8920 ? If you haven't setup SSL then you will only have access via http on port 8096.
Justus 8 Posted February 19, 2021 Author Posted February 19, 2021 (edited) Yea i only used http 8096 since. I havent set up a SSL certificate yet, since i dont know how yet. My WAN Acces is http a.b.c.d:8096 Edited February 19, 2021 by Justus
Happy2Play 9783 Posted February 19, 2021 Posted February 19, 2021 Does the dashboard show the same WAN address as Port Checker - Check Open Ports Online?
rbjtech 5284 Posted February 19, 2021 Posted February 19, 2021 (edited) ok - so if port 8096 is open (portchecker has confirmed it is - which means your router is forwarding correctly and any firewalls are passing port 8096 fine) - then simply connect using http:\\a.b.c.d:8096 on the device and it should work. Note this is http - not https. Note 2 - Your ISP may dynamically change your WAN address - so be wary of this. There are ways around this using a service called DDNS - but if you plan on setting up SSL, then this can all be incorporated in that. Edited February 19, 2021 by rbjtech
Happy2Play 9783 Posted February 19, 2021 Posted February 19, 2021 It started working, so am guessing a ip change and took awhile for Connect to update to allow the client to connect. 1 1
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