Utility: Vista Sidebar Gadget

[KarylFStein]

I think by default Jetty has a listener on 8080. I added an SSL port to it as well, but kept the 8080 one open. So, the gadget on my home desktop uses 8080 (that port is not available outside the LAN). Outside the LAN, the web server is only accessible over the HTTPS port. The gadget won't work over the Internet, but like cnbc said, you wouldn't want to do that anyway since your password is unencrypted...

[mkanet]

I just installed the latest version just now. I actually have jetty with http as well, except it listens on port 8380. 8080 is already used for another network service on this machine. I have at least 9 network services running on this machine... (ssh2,sftp, vnc, II7 with asp.net apps/ssh, etc) so, common ports are very scarce.

Ive tried every single combination I could think of... (with jetty authentication enabled):

Stuff I've tried:

Server: localhost, localhost/sage, localhost/sage/home, http://localhost:8380/sage/Home, https://localhost:8090/sage/Home, localhost:8090/sage/Home (I've even tried all that replacing localhost with other valid resolvable/pingable DNS names).Port: 8380
Port: 8090

Oddly, the ONLY thing that worked this time thanks to your advice (it didnt work for me using the previous version of this gadget from yesterday) was when using my cloaked url: sagetv.myurl.com Port:80 ....Keeping in mind that is really pointing to https://myurl.com:8090/Sage/home.

I finally connect, and ------ for each tuner... However, they are all blank when my tuners are active and recording. Record schedule is blank too. So, its still not getting the data.

I doubt I've missed any other configuration to trick it to work using the latest version.

I dont know.. maybe its just better to leave this alone... This gadget is probably better suited for a more typical sageTV setup. Or, maybe I'm just too dumb to figure it out. However, CNCB, if you do have the motivation to help me get this working, I would be very grateful. It is a very cool app regardless if I can't use it. I just dont know what else to try,

PS: This is a relatively minor issue, but the gadget maxes out at only 10 tuners. I have 12 active tuners.

Thanks so much for all your help!
-Michael

Originally Posted by KarylFStein

I think by default Jetty has a listener on 8080. I added an SSL port to it as well, but kept the 8080 one open. So, the gadget on my home desktop uses 8080 (that port is not available outside the LAN). Outside the LAN, the web server is only accessible over the HTTPS port. The gadget won't work over the Internet, but like cnbc said, you wouldn't want to do that anyway since your password is unencrypted...

[cncb]

Originally Posted by mkanet

I just installed the latest version just now. I actually have jetty with http as well, except it listens on port 8380. 8080 is already used for another network service on this machine. I have at least 9 network services running on this machine... (ssh2,sftp, vnc, II7 with asp.net apps/ssh, etc) so, common ports are very scarce.

Can you access the webserver through a browser with a standard http address? That is, without the cloaked URL and SSL: e.g. "http://localhost:8380/sage/Home". It sounds like that is what KarylFStein is doing with 2 different ports. The same address and port should then work in the gadget. By the way, only the address part of the URL should go in the "Server" field for the gadget, not http or port number, /sage, etc.

I'm not sure if Jetty authentication is having any affect so you might want to try turning that off. You could also try "127.0.0.1" or the specific IP address of the local server instead of "localhost".

[mkanet]

Yes, of course, "http://localhost:8380/sage/Home" works fine for both ssl and non secure ports same for BMT. I've already tried 127.0.0.1 as well. The only thing I didnt try is disabling authentication.

I am also trying with two different ports... one SSL and one not. Plus, a third way for me using a cloaked URL which the gadget seemed to like best; which didnt really work.

Yeah, my understand of how to configure it was exactly how you mentioned below; but all those weird configurations I tried were just out of desperation

Originally Posted by cncb

Can you access the webserver through a browser with a standard http address? That is, without the cloaked URL and SSL: e.g. "http://localhost:8380/sage/Home". It sounds like that is what KarylFStein is doing with 2 different ports. The same address and port should then work in the gadget. By the way, only the address part of the URL should go in the "Server" field for the gadget, not http or port number, /sage, etc.

I'm not sure if Jetty authentication is having any affect so you might want to try turning that off. You could also try "127.0.0.1" or the specific IP address of the local server instead of "localhost".

[KarylFStein]

Hmm, now I'm having problems. I reinstalled SageTV a few days ago and installed the Jetty and webserver stuff like I had before EXCEPT I used version 2.26 of the webserver instead of 2.25.

My gadget (1.2b) now keeps saying "NA" for everything including the flyout.

I used my browser to hit the same URL the gadget should be using, (http://192.168.0.101:8080/sage/Home?xml=currrecording), and it gave me the following:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<!DOCTYPE sageShowInfo (View Source for full doctype...)>
- <sageShowInfo version="1.3">
- <systemInfo>
<alertLevel description="Status" level="0" />
</systemInfo>
<channelList />
<favoriteList />
<showList />
<systemMessageList />
</sageShowInfo>

I looked at my Jetty logs and noticed that a "no recordings going on" reply in the old setup was 244 bytes while now it's 294. So, not sure if something changed in the message going to 2.26. (That means I *do* see the gadget making a successful request and getting a reply in the Jetty logs. It just doesn't seem to know what to do with the reply...)

[jreichen]

Originally Posted by KarylFStein

Hmm, now I'm having problems. I reinstalled SageTV a few days ago and installed the Jetty and webserver stuff like I had before EXCEPT I used version 2.26 of the webserver instead of 2.25.

My gadget (1.2b) now keeps saying "NA" for everything including the flyout.

I used my browser to hit the same URL the gadget should be using, (http://192.168.0.101:8080/sage/Home?xml=currrecording), and it gave me the following:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<!DOCTYPE sageShowInfo (View Source for full doctype...)>
- <sageShowInfo version="1.3">
- <systemInfo>
<alertLevel description="Status" level="0" />
</systemInfo>
<channelList />
<favoriteList />
<showList />
<systemMessageList />
</sageShowInfo>

I looked at my Jetty logs and noticed that a "no recordings going on" reply in the old setup was 244 bytes while now it's 294. So, not sure if something changed in the message going to 2.26. (That means I *do* see the gadget making a successful request and getting a reply in the Jetty logs. It just doesn't seem to know what to do with the reply...)

I added the alert level and system messages to the xml so that would explain the size difference.

[cncb]

It sounds like the gadget is not handling changes to the XML appropriately. I will take a look.

[cncb]

Originally Posted by jreichen

I added the alert level and system messages to the xml so that would explain the size difference.

I installed the new 2.26 version of the web server and it seems that the problem is that the gadget is now getting an empty reply/document for the current recordings XML. Any idea what might have changed to cause this?

[jreichen]

Originally Posted by cncb

I installed the new 2.26 version of the web server and it seems that the problem is that the gadget is now getting an empty reply/document for the current recordings XML. Any idea what might have changed to cause this?

At this url? http://192.168.xx.xx:8080/sage/Recordings?xml=yes

Mine is working fine. The Jetty build has a copy of nielm_sagexmlinfo.jar in the war file so it doesn't need it in the JARs folder. Do you have an older version in the JARs folder?

Is there anything in the sage log?

[cncb]

Sorry, never mind. It turns out that it was failing to load the XML because it was (unexpectedly) validating the XML against the old schema. I will post a fix to the gadget for testing shortly.

[cncb]

Ok, can you guys try the update posted below to make sure it works with your SSL setups before I submit it?

[KarylFStein]

That one works for me now, thanks!

[cncb]

Originally Posted by KarylFStein

That one works for me now, thanks!

Thanks. I posted the update.

[shill]

I've just moved from the TJWS version of nielm's webserver (which is working fine) to the Jetty version (2.26) and added the gadget to my Windows 7 desktop. Unfortunately, I'm getting the same "NA" error message complaining about network connections, server, and settings issues. The XML pages all appear to work fine, and my login info works as well.

Interestingly, the jetty log file shows no request activity UNLESS I intentionally flub the password, in which case it shows the 401 response.

I'm really looking forward to this gadget - thanks for providing it!


Never mind - it randomly started working

[sbeaulieu]

Greate gadget! I got it working without issue.

One thing I noticed is how infrequent something is actually recording midday. Because of this it would be very cool to be able to see a few lines of the recording schedule in the Now Recording window so I can see what is coming up tonight without the having to click to get the full list from the fly out.

[cncb]

Originally Posted by sbeaulieu

One thing I noticed is how infrequent something is actually recording midday. Because of this it would be very cool to be able to see a few lines of the recording schedule in the Now Recording window so I can see what is coming up tonight without the having to click to get the full list from the fly out.

I agree - that's a good idea. Perhaps for each "slot" in the gadget that doesn't have a current recording I could instead show the next upcoming recording? I will definitely consider this for a future update.

[carlgar]

You should also consider a couple of minor issues with the Include padding in start and end times option. I am currently seeing a favorite program listed in the gadget showing the requested 2 minute end padding. However, Sage does not show the 2 minute end padding, I suspect because of a back to back shows. If not an easy fix I would prefer the current logic to show the longest length. The issue that bothers me the most is with a manual recording. When I manually add end padding to a manual recording, the gadget does not see that padding, Sage does. It is fairly common for me to make a recording manual just so I can add the end padding. I consider this to be an oversight in the logic.

[cncb]

Originally Posted by carlgar

The issue that bothers me the most is with a manual recording. When I manually add end padding to a manual recording, the gadget does not see that padding, Sage does. It is fairly common for me to make a recording manual just so I can add the end padding. I consider this to be an oversight in the logic.

There really is no "logic" involved. I just use the padding supplied by the web server (XML) for the recordings and the padding is not available for manual recordings.

[carlgar]

Originally Posted by cncb

There really is no "logic" involved. I just use the padding supplied by the web server (XML) for the recordings and the padding is not available for manual recordings.

Interesting, I never even considered what was available to an external program. I had only been thinking that it was studio code.

[cncb]

I just submitted v1.4 that also shows upcoming recordings in the gadget.