Connection issues - probably IPv6 related?

Access your ARGUS TV system from your sofa using Kodi or XBMC (http://kodi.tv/)
Post Reply
nslr
Posts: 5
Joined: Mon Aug 13, 2012 6:00 pm

Connection issues - probably IPv6 related?

Post by nslr » Tue Feb 12, 2013 6:45 pm

Hi,

Just this weekend, I updated my HTPC to Windows 8 Pro. I hoped that would be as painless as when I updated my other PC's - but no :(
My HTPC is running several "web-servers" - CouchPotato, Sickbeard, etc.. But it's also running a Node.js-server, which is acting as a proxy to all these other web interfaces - and this proxy is set up for port 80.
Now, when using Windows 8, the system automatically occupies port 80 for something called "http.sys" (See http://www.mikeplate.com/2011/11/06/sto ... n-windows/ for more detail) - this is for .Net-apps (and others) to have a common API for serving up things.
This meant, that I could not use my Node.js-based proxy. But the above link had a solution! Just make http.sys use IPv6, and leave port 80 free on IPv4!
But now XBMC cannot connect to the Argus TV Core anymore! Here's a log of the error:

Code: Select all

17:29:32 T:5180   ERROR: AddOnLog: ARGUS TV client: can not write to http://localhost:49943/ArgusTV/Core/Ping/52
17:29:32 T:5180   ERROR: AddOnLog: ARGUS TV client: Ping failed... No connection to Argus TV.
17:29:33 T:5180   ERROR: ADDON: Dll ARGUS TV client - Client returned bad status (6) from Create and is not usable
17:29:33 T:5180 WARNING: PVR::CPVRClients::UpdateAndInitialiseClients - failed to create add-on ARGUS TV client, status = 6
17:29:33 T:5180 WARNING: PVR::CPVRClients::UpdateAndInitialiseClients - failed to load the dll for add-on ARGUS TV client, disabling it
17:29:33 T:3920  NOTICE: Thread CAddonStatusHandler:pvr.argustv start, auto delete: true
Does this mean anything to anyone?? :) Using both 127.0.0.1 and localhost do not work. I changed it to localhost, because it was mentioned in the article above.

Thanks in advance!

User avatar
dot-i
Site Admin
Posts: 5848
Joined: Mon Oct 01, 2012 3:40 pm

Re: Connection issues - probably IPv6 related?

Post by dot-i » Tue Feb 12, 2013 7:13 pm

Did you try ::1? This is the IPv6 equivalent of localhost...
I have the heart of a child. I keep it in a jar on my shelf. -- Robert Bloch
Image

nslr
Posts: 5
Joined: Mon Aug 13, 2012 6:00 pm

Re: Connection issues - probably IPv6 related?

Post by nslr » Tue Feb 12, 2013 7:35 pm

Nope, I'll give that a try, and let you know :-)

nslr
Posts: 5
Joined: Mon Aug 13, 2012 6:00 pm

Re: Connection issues - probably IPv6 related?

Post by nslr » Tue Feb 12, 2013 9:52 pm

That made no difference :(
Which processes are supposed to be running, for the API to be accessible? I can't access the Web interface for scheduling since I tried solving the http.sys-error by re-installing Argus last night. Can the 2 issues be connected?

When trying to wget the API call, I get this error:

Code: Select all

--2013-02-12 20:47:20--  http://localhost:49943/ArgusTV/Core/Ping/52
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:49943... failed: Connection refused.
A ping of localhost gets me this:

Code: Select all

C:\Users\nslr>ping localhost

Pinging nslr-htpc [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms

Ping statistics for ::1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

User avatar
andrewNZ
Posts: 677
Joined: Thu Nov 26, 2009 2:07 pm
Location: Dunedin, New Zealand

Re: Connection issues - probably IPv6 related?

Post by andrewNZ » Tue Feb 12, 2013 11:10 pm

Not a firewall issue is it?
You can fix it, or you can fix it until it's broken. I usually choose the latter.

Server: WHS 2011. Hauppauge HVR 2200. Avermedia A835. ArgusTV Server. EPG Collector.
Clients: Win7 64bit. MediaPortal. ArgusTV Client. StreamedMP.

nslr
Posts: 5
Joined: Mon Aug 13, 2012 6:00 pm

Re: Connection issues - probably IPv6 related?

Post by nslr » Sat Feb 23, 2013 9:56 pm

Nope, no firewall issues. But I did find a solution. Luckily I didn't get far enough as to implement my reverse-proxy in ASP or some other .Net env - that would have been a huge waste of time :)

If anyone runs into this issue in the future, I found a solution here:
http://superuser.com/questions/510407/w ... ay-port-80

Stop the service "World Wide Web Publishing Service", and set startup to manual.
The thing with diverting the http.sys module to use IPv6 does not work, as some part of the Argus-XBMC plugin apparently needs IPv4

kalo
Posts: 1
Joined: Thu Dec 24, 2015 2:44 pm

Re: Connection issues - probably IPv6 related?

Post by kalo » Thu Dec 24, 2015 2:56 pm

I'm using Nginx as a reverse proxy. All my problems were solved by using UtilDEv Web Server Explorer to modify the website to use a Virtual Directory (Network Addresses tab).
Hope this helps
Kalo

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest