mattykellyuk 18 Posted September 3, 2021 Posted September 3, 2021 (edited) Hi, I'm sorry I'm sure there are plenty of similar threads but my problem seem quite weird. So I have SSL connection setup using my domain and cloudfare. Yesterday one of my users couldn't use emby (others are fine) and while investigating I found some weird results. So when going to my domain Chrome on windows is saying its not secure and the site can't be reached but the android app works when not connected to my home wifi. Also chrome on my android phone is fine going to my domain. So I went to check and have confirmed the following: The HTTPS port for external streaming is 443. This is open Secure connect mode is 'required..' Nameservers on domain and cloudfare match IP address of DNS in cloudfare is correct I'm lost so any suggestions would be great. Just so weird that its stopped worker. I haven't changed anything. fyi my domain is https://emby.xxx Thanks Edited November 17, 2021 by mattykellyuk
rbjtech 5284 Posted September 3, 2021 Posted September 3, 2021 (edited) Cert is valid and access look fine to me using Chrome... Maybe clear all the cache on the browser and dns cache may help ? Edited September 3, 2021 by rbjtech
mattykellyuk 18 Posted September 3, 2021 Author Posted September 3, 2021 6 minutes ago, rbjtech said: Cert is valid and access look fine to me using Chrome... Maybe clear all the cache on the browser and dns cache may help ? Thanks for trying. Yeah tried that and did a restart and still no luck. Chrome gives the option for a 'Connectivity diagnostics' which passes everything apart from 'Gateway' which says this 'Failed to ping the default network gateway'
rbjtech 5284 Posted September 3, 2021 Posted September 3, 2021 (edited) Ensure your Chrome has the 'Baltimore CyberTrust Root' cert - as this is what your cloudflare cert is ultimately trusted by. If you have this, then there is no reason a trust cannot be established .. very odd. Edited September 3, 2021 by rbjtech
mattykellyuk 18 Posted September 3, 2021 Author Posted September 3, 2021 1 hour ago, rbjtech said: Ensure your Chrome has the 'Baltimore CyberTrust Root' cert - as this is what your cloudflare cert is ultimately trusted by. If you have this, then there is no reason a trust cannot be established .. very odd. Yeah it displays as in your screenshot. 1
rbjtech 5284 Posted September 3, 2021 Posted September 3, 2021 Have you tried an alternative browser such as Edge or Firefox ?
mattykellyuk 18 Posted September 3, 2021 Author Posted September 3, 2021 7 minutes ago, rbjtech said: Have you tried an alternative browser such as Edge or Firefox ? yeah tried Edge but had the same problem so didn't try firefox.
mattykellyuk 18 Posted September 3, 2021 Author Posted September 3, 2021 Should also say I have had users with problems using android tv app and LG webos app but others that are fine so could be people who aren't very confident with IT
Carlo 4561 Posted September 3, 2021 Posted September 3, 2021 Hi, Your site loads up fine for me as well just like what @rbjtech said.
mattykellyuk 18 Posted September 6, 2021 Author Posted September 6, 2021 19 hours ago, Luke said: @mattykellyuk has this helped? Well its reassured me that it should be OK but I'm still seeing the same problem. On my Windows 10 PC and chromebook the link in the first post to my domain doesn't work. On my android phone and work Windows 10 laptop they do.
rodainas 191 Posted September 6, 2021 Posted September 6, 2021 12 minutes ago, mattykellyuk said: Well its reassured me that it should be OK but I'm still seeing the same problem. On my Windows 10 PC and chromebook the link in the first post to my domain doesn't work. On my android phone and work Windows 10 laptop they do. Maybe different dns servers on those devices groups?
Carlo 4561 Posted September 6, 2021 Posted September 6, 2021 Open a command prompt on both your Windows PC and your laptop. Next try the following: ping emby.redtruckracing.tk That should come back with an IP address. Are the IPs shown on both computers the same?
mattykellyuk 18 Posted September 6, 2021 Author Posted September 6, 2021 3 hours ago, cayars said: Open a command prompt on both your Windows PC and your laptop. Next try the following: ping emby.redtruckracing.tk That should come back with an IP address. Are the IPs shown on both computers the same? Thanks. Computer with the problem says 'ping request could not find host emby.redtruckracing.tk...' Laptop that works find an IP address, but not the same IP as the server.
Carlo 4561 Posted September 6, 2021 Posted September 6, 2021 This sounds like you have a basic networking setup issue. I'd start by looking to see what DNS servers are being used for the working clients and which are being used on the clients not working and switch them out of the non working clients.
mattykellyuk 18 Posted September 6, 2021 Author Posted September 6, 2021 3 minutes ago, cayars said: This sounds like you have a basic networking setup issue. I'd start by looking to see what DNS servers are being used for the working clients and which are being used on the clients not working and switch them out of the non working clients. Sorry bit of a noob with DNS. Any guidance would be great. Cloudfare has a section on DNS which I just update the IP address of the server when it changes and as nameservers which which the ones of my domain.
Carlo 4561 Posted September 6, 2021 Posted September 6, 2021 This isn't a Cloudflare issue but the networking setup on your local network. Your devices are using different DNS servers. Do you have multiple routers? If so these are probably giving your devices/computers different settings.
mattykellyuk 18 Posted September 6, 2021 Author Posted September 6, 2021 21 minutes ago, cayars said: This isn't a Cloudflare issue but the networking setup on your local network. Your devices are using different DNS servers. Do you have multiple routers? If so these are probably giving your devices/computers different settings. Yeah that makes sense thanks. I recently added a booster router which I don't think I didn't correctly. So I turned it off and unplugged from the router, restarted the router and emby and it doesn't seem to have helped. The router is set to keep the server on a given IP address.
Carlo 4561 Posted September 6, 2021 Posted September 6, 2021 That's good because you don't want the server changing. The problem isn't the server but the clients who can't ping the server.
rbjtech 5284 Posted September 7, 2021 Posted September 7, 2021 on each client in a command prompt - type ipconfig /all look for the line that says 'DNS servers' - unless you have changed it, it's usually the same as the Default Gateway IP and DNS is usually provided by your ISP (by forwarding in the router) Compare the working and non-working addresses to a) ensure they are on the same LAN (ie 192.168.1.x) and b) have the same DNS/GW settings. There is nothing sensitive about local IP's, so if you want to post them here we can advise further.
mattykellyuk 18 Posted September 7, 2021 Author Posted September 7, 2021 4 hours ago, rbjtech said: on each client in a command prompt - type ipconfig /all look for the line that says 'DNS servers' - unless you have changed it, it's usually the same as the Default Gateway IP and DNS is usually provided by your ISP (by forwarding in the router) Compare the working and non-working addresses to a) ensure they are on the same LAN (ie 192.168.1.x) and b) have the same DNS/GW settings. There is nothing sensitive about local IP's, so if you want to post them here we can advise further. thanks. Below is what I get when I do that on the server. I have the server set to 192.168.0.2 on the router. When cayars says clients do you mean fire sticks, tvs and everything or can this be fixed 'centrally'? Thanks appreciate your help. I'm assuming this is why some of my users can't use emby at the moment. Windows IP Configuration Host Name . . . . . . . . . . . . : SERVER Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : Home Ethernet adapter Ethernet 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-V Physical Address. . . . . . . . . : 70-85-C2-5D-6D-81 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Ethernet: Connection-specific DNS Suffix . : Home Description . . . . . . . . . . . : Intel(R) I211 Gigabit Network Connection Physical Address. . . . . . . . . : 70-85-C2-5D-6D-7F DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2a02:c7f:5086:2500:c93a:f828:46a1:f4a5(Preferred) IPv6 Address. . . . . . . . . . . : fdb4:388e:fee3:0:c93a:f828:46a1:f4a5(Preferred) Temporary IPv6 Address. . . . . . : 2a02:c7f:5086:2500:51e9:a73c:6619:809b(Preferred) Temporary IPv6 Address. . . . . . : fdb4:388e:fee3:0:51e9:a73c:6619:809b(Preferred) Link-local IPv6 Address . . . . . : fe80::c93a:f828:46a1:f4a5%8(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : 06 September 2021 20:55:57 Lease Expires . . . . . . . . . . : 07 September 2021 20:55:56 Default Gateway . . . . . . . . . : fe80::c2a3:6eff:fe29:ba41%8 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 57705922 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-85-A2-F8-70-85-C2-5D-6D-81 DNS Servers . . . . . . . . . . . : fdb4:388e:fee3:0:c2a3:6eff:fe29:ba40 192.168.0.1 fdb4:388e:fee3:0:c2a3:6eff:fe29:ba40 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Ethernet 3: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : TAP-NordVPN Windows Adapter V9 Physical Address. . . . . . . . . : 00-FF-E4-7E-12-CA DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Wi-Fi: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 3168 Physical Address. . . . . . . . . : F8-94-C2-BC-7C-0D DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Local Area Connection* 3: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter Physical Address. . . . . . . . . : F8-94-C2-BC-7C-0E DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Local Area Connection* 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2 Physical Address. . . . . . . . . : FA-94-C2-BC-7C-0D DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes
rbjtech 5284 Posted September 7, 2021 Posted September 7, 2021 (edited) ok - so your server is using :- IP - 192.168.0.2 G/W - 192.168.0.1 DNS - 192.168.0.1 This is all pretty standard and correct. Did you reserve this IP in DHCP, or was this the IP it got by itself ? The important part is to make sure the emby Clients are all using the same settings but with a different IP address - they SHOULD be if they use DHCP (Auto Config)- ie IP - 192.168.0.x (anything from 3 to 255) G/W - 192.168.0.1 DNS - 192.168.0.1 As long as these settings are correct, then DNS on any client should work the same. Yes by client we mean anything that is not the emby server - firetv sticks, web clients etc Edited September 7, 2021 by rbjtech
rbjtech 5284 Posted September 7, 2021 Posted September 7, 2021 (edited) Ah - hold on - are you trying to get to your own server internally using the external address ? If yes, then on the clients that are working - are they NOT using wifi/LAN ? You cannot access the external address on a LAN unless you have a setup called 'loopback' or 'hairpin' on the router which re-routes the external traffic back to your LAN. If you need to access the server internally (on your own lan), then just use the local IP and unsecure port. ie http:\\192.168.0.2:8096 Edited September 7, 2021 by rbjtech
mattykellyuk 18 Posted September 7, 2021 Author Posted September 7, 2021 Under my router settings 'LAN TCP/IP Setup' I have the server 'Address Reservation' for 192.168.0.2 and 'Use Router as DHCP Server' ticked with the addresses 192.168.0.2 to 192.168.0.254. Should I change that last setting to 192.168.0.2 to 192.168.0.2? When you say 'IP - 192.168.0.x (anything from 3 to 255)' is the above a problem or I thought this was correct as I did the command prompt on the machine that runs emby? I am trying to access externally on a number of devices some internal and some external. Some work some don't
mattykellyuk 18 Posted September 7, 2021 Author Posted September 7, 2021 4 minutes ago, rbjtech said: Ah - hold on - are you trying to get to your own server internally using the external address ? If yes, then on the clients that are working - are they NOT using wifi/LAN ? You cannot access the external address on a LAN unless you have a setup called 'loopback' or 'hairpin' on the router which re-routes the external traffic back to your LAN. If you need to access the server internally (on your own lan), then just use the local IP and unsecure port. ie http:\\192.168.0.2:8096 To summarise I had users say they couldn't access from outside my network. I normally test this by going to my domain and found it worked on some devices and not others.
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