Angelblue05 4130 Posted August 12, 2015 Share Posted August 12, 2015 We use the server address to connect via http and websocket. I still don't think a hostname works. But please if I'm wrong, correct me . The address is manipulated since we append http/https to it, as well as ws/wss for the websocket connection. Would it be compatible with the hostname in this case? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Logos302 86 Posted August 12, 2015 Share Posted August 12, 2015 This is getting a little bit out of my depth but as I understand how DNS works. The TCP/IP stack would just take your hostname and convert it to ip. So as long as the name you choose is resolvable by the client to your server (Obviously). AS an example you say I want Server-1/lasdjflkajsd and it will take the server-1 and convert it using DNS to it's ip. So I'm not sure how you wouldn't be compatible with hostname to be honest. This is all part of network standards. I'm not at home to look at my set up, but I don't think I gave it a name for my server and if I did I would have given it my hostname. Hostname also allows for changes ie if you get a new router and it uses a different IP range that your old one everything will still work as your new routers dns will have the correct records. In the end you are using the ip address it just easier to read by us mer-humans. Where this can fall apart is if someone is using there ISP DNS or Google's DNS (on there clients, the router is a different story), which do not have your server's record. So it would fail. I much prefer to know that I'm connecting to Server-1 rather then 192.129.1.111. don't you? Link to comment Share on other sites More sharing options...
im85288 1493 Posted August 12, 2015 Share Posted August 12, 2015 I haven't read the entire thread but we aim to follow how it works with other Emby clients. The Emby server stores local and remote server addresses (in what format I'm not sure). Anyway to cut a long story short can you connect remotely with the web client? If so then we should be able to the same with the Kodi addon. If not then you would be better reporting about it in the server section. Link to comment Share on other sites More sharing options...
jani 4 Posted August 13, 2015 Share Posted August 13, 2015 (edited) I haven't read the entire thread but we aim to follow how it works with other Emby clients. The Emby server stores local and remote server addresses (in what format I'm not sure). Anyway to cut a long story short can you connect remotely with the web client? If so then we should be able to the same with the Kodi addon. If not then you would be better reporting about it in the server section. Here's one possible reason, but I haven't verified it: - Emby server only listens for IPv4 address (0.0.0.0) - By default, Emby for Kodi might prefer IPv6. - That's what wget does: jani@raspberry ~ ❯❯❯ wget -T 15 liquorice:8096 --2015-08-13 17:45:00-- http://liquorice:8096/ Resolving liquorice (liquorice)... fd4e:bfce:25c3::403, CENSORED::403, 192.168.1.42 Connecting to liquorice (liquorice)|fd4e:bfce:25c3::403|:8096... failed: Connection timed out. Connecting to liquorice (liquorice)|CENSORED::403|:8096... failed: Connection timed out. Connecting to liquorice (liquorice)|192.168.1.42|:8096... connected. HTTP request sent, awaiting response... 302 Found Location: web/index.html [following] --2015-08-13 17:45:30-- http://liquorice:8096/web/index.html Reusing existing connection to liquorice:8096. HTTP request sent, awaiting response... 200 OK Length: 4514 (4.4K) [text/html] Saving to: ‘index.html’ index.html 100%[================================================================================================>] 4.41K --.-KB/s in 0s 2015-08-13 17:45:31 (52.4 MB/s) - ‘index.html’ saved [4514/4514] But yeah, I got carried away a bit and a new thread would be better. Anyway, the real problem is the broken texture cache on 15.0 and thus I thought this thread might be for broken stuff in 15.0 as it used to work when I was on 14.2. Edited August 13, 2015 by jani Link to comment Share on other sites More sharing options...
Recommended Posts