Plugin: Web User Interface for SageTV 2.2-6.6 (V2.25 18 Sep 2009)

[bsung]

This is probably a dumb question and I'm not sure if this is the right thread to post, but I'm a bit confused about neilm's web server plugin. Until very recently, I used to be able to log into my web server directly by using the port I had assigned (from v6 I think) and username/password. I used to be able to get in through the Jetty server application as well. But, I recently had some problems with my plugins so I needed to unintall and reinstall them again. Now, I can't seem to log in directly but instead have to go through Jetty. Does that make sense?

I think there used to be a line in sage.properties where you set the properties of neilm's web server but can't even find where I set the specific port for neilm's web server. Not completely sure my explanation is clear, but any help would be appreciated.

[jreichen]

If you installed nielm's web interface from the SageTV v7 plugin manager then yes, it is now running in Jetty. The port number and other web server properties are configured in the Jetty plugin's configuration options page.

Support for the web ui and Jetty plugins under Sage v7 are provided in the new SageTV v7 Customizations forum.

[bsung]

Originally Posted by jreichen

If you installed nielm's web interface from the SageTV v7 plugin manager then yes, it is now running in Jetty. The port number and other web server properties are configured in the Jetty plugin's configuration options page.

Support for the web ui and Jetty plugins under Sage v7 are provided in the new SageTV v7 Customizations forum.

Ok, thanks

[ericscottf]

When a show reaches the end, or is stopped instead of paused (all on a hd200), the web interface shows it as still playing (not stopped or paused)

Also, it typically takes two clicks of "stop playing" before it is correct in the web interface.

any plans for a fix, or am i doing something wrong?

[jreichen]

Originally Posted by ericscottf

any plans for a fix

Probably not Unless I'm in the code sometime and find out it's an easy fix.

Originally Posted by ericscottf

am i doing something wrong?

I doubt it. There's probably a bug but I'm pretty busy working on something else right now and it's not a critical problem so it will probably remain for now.

[ToonGal]

Originally Posted by jreichen

Support for the web ui and Jetty plugins under Sage v7 are provided in the new SageTV v7 Customizations forum.

It's been very hard to find the current release (if any), because the forums never split v5 and v6, and legacy items are hard to 'search' for, given the lack of v5 user base. Has there been any web development since v2.26R50?

EDIT: As I read this, I know it is obvious there has been development. To phrase the question precisely: "Has there been any development that I can use, given I still use SageTV v5?"

Thanks for the help!

[gplasky]

I would venture to guess that any development has gone into v7. And I don't think the developers are wanting to support the older versions so most of the v7 plugins are not packaged in a v5 or v6 friendly way to even install.

Might be time to bite the bullet and upgrade.

Gerry

[jreichen]

I see you upgraded from Sage 2.2

Gerry's right. 2.27 and later only work on Sage v7. For the most part the changes have been to support new features in Sage v7.

It's extra work to support old releases and with the new plugin system in v7 that seemed like a good time to drop support for older releases (you can still download and run 2.26 on older releases).

[jbuszkie]

Is there a way to seek using the streaming functions?

[s.bachman]

I installed SageTV Web Interface via the plugins manager in SageTV7 and the jetty server works but when I attempt to access the Web Page I get this error

HTTP ERROR 404

Problem accessing /sage/Home/. Reason:

NOT_FOUND

Powered by Jetty://

[ericscottf]

I'm getting the same error, but only after i attempted to switch to SSL.
Everything was working fine before the attempted switch.

HTTP ERROR: 404 %2Fsage%2FHome+Not+Found

RequestURI=/sage/Home

Powered by Jetty://

from my sage.properties:

nielm/webserver/port=8443
nielm/webserver/realms_file=realms.properties
nielm/webserver/root=webserver
nielm/webserver/sage_recordings_includes_archived_files=true
nielm/webserver/servlets_file=servlets.properties
nielm/webserver/session_timeout=
nielm/webserver/ssl_args=-keystoreFile (default %HOME%/.keystore) -keystorePass (default 123456)

-keystoreType (default JKS) -algorithm (default SunX509) -clientAuth (default false) -protocol (default

TLS) -backlog (default 1000) -ifaddress (default none)
nielm/webserver/throttles_file=throttles.properties
nielm/webserver/use_ssl=true

Got my instructions from here:
http://tools.assembla.com/sageplugins/wiki/WebserverSsl

Also, if i ever get this working, i'd like it to be on a different port#. Is that as easy as changing all instances of 8443 to whatever?

any ideas?
thanks

[jreichen]

Originally Posted by jbuszkie

Is there a way to seek using the streaming functions?

No, unfortunately not.

[jreichen]

Originally Posted by s.bachman

I installed SageTV Web Interface via the plugins manager in SageTV7 and the jetty server works but when I attempt to access the Web Page I get this error

HTTP ERROR 404

Problem accessing /sage/Home/. Reason:

NOT_FOUND

Powered by Jetty://

Are you running the SageTV service and client on your server?

Can you shut down all your Sage processes then print non-recursive directory listings of the JARs and jetty/webapps directories?

There's a new thread where there's been a discussion and bug submitted about plugin installation and I'm wondering if this is the same issue.

[jreichen]

Originally Posted by ericscottf

I'm getting the same error, but only after i attempted to switch to SSL...

You're following the instructions for when nielm's web interface is running on its own web server (Tiny Java Web Server). Follow the instructions here for when you're running it on Jetty. There's a link on that page for SSL setup. The process of creating the keys is the same, but the configuration is different.

In case you didn't know, TJWS could only run nielm's web interface. It couldn't run any other web apps. Jetty can run nielm's as well as the mobile web interface, BMT (Batch Metadata Tools), SRE (Sage Recording extender), etc. Jetty is the web server that will be supported from now on.

Hope that helps.

[ericscottf]

Okay, thanks.
Followed those instructions.
Tried it with hashed and plaintext passwords, same problem:
When i go to my https://localhost:sslport/sage/home
i get this in the status bar
"connecting to localhost..."
"Connected"
loop that a few times, then a failure (connection reset generic firefox error)
This is the same error one gets if they attempt to go to any non existent https: site, so i'm guessing that i missed some bit of setup and nobody's listening on my ssl port.

following the instructions for sage 6:
Shut down sage service
(i generated a key with the user that sage runs under (is an admin)
i edited JettyStarter.properties and modified the lines as instructed.
Made sure the firewall on this pc lets that port thru (can't even access the ssl site from this pc)
Regular access works as it always has.

Any ideas? Any way to debug?
thanks

[trallyus]

Originally Posted by ericscottf

Okay, thanks.
Followed those instructions.
Tried it with hashed and plaintext passwords, same problem:
When i go to my https://localhost:sslport/sage/home
i get this in the status bar
"connecting to localhost..."
"Connected"
loop that a few times, then a failure (connection reset generic firefox error)
This is the same error one gets if they attempt to go to any non existent https: site, so i'm guessing that i missed some bit of setup and nobody's listening on my ssl port.

following the instructions for sage 6:
Shut down sage service
(i generated a key with the user that sage runs under (is an admin)
i edited JettyStarter.properties and modified the lines as instructed.
Made sure the firewall on this pc lets that port thru (can't even access the ssl site from this pc)
Regular access works as it always has.

Any ideas? Any way to debug?
thanks

Try capitalizing Home as when I don't capitalize home it says HTTP ERROR 404

Problem accessing /sage/home. Reason:

NOT_FOUND

Powered by Jetty://

Hopefully that is the problem and not something else.
Trallyus

[ericscottf]

Yeah, that's not it -- if that was the error, then the server would at least be responding on the ssl port, which it is not.

The server's not listening on that port or not running. It works fine on the non ssl, however.

anyone have a suggestion?
thanks

[trallyus]

Not sure if this helps , but my only other suggestion is to go to setup/sagetv plugins/installed plugins/jetty webserver and click it to configure plugin and see if enable ssl is set to true.

Then if your running sagetvservicecontrol, choose disable and stop on it it then reenable it and that should restart jetty with the new settings.

I had trouble with jetty restarting the server to accept the new settings and turning sage all the way off and restarting it usally fixed it and had forgotten to turn off sagetvservicecontrol.exe

Trallyus

[jreichen]

Originally Posted by trallyus

Not sure if this helps , but my only other suggestion is to go to setup/sagetv plugins/installed plugins/jetty webserver and click it to configure plugin and see if enable ssl is set to true.

This is what I was going to suggest. Have you tried it?

I thought users would usually go to the plugin manager to install Jetty so that's the starting point. There's a setting there to enable SSL (it sets up Jetty's properties to start up an SSL HTTP connection) as well as a URL in the property's description for the wiki that has the instructions for creating the SSL certificate.

[CptKirk]

Working to import my BTV recordings into SageTV.

Following the how-to guide by Geek Tonic.

http://www.geektonic.com/2008/01/how...hows-into.html

Used "BTV Negociator" by Fonceur to get the meta data.

Used "Translate BTV XML" by Nielm to change it to SageTV format.

Everything looks good in the XML file to be used.

Opened the SageTV Web Interface and clicked the import xml link.

Checked only the Import TV files link.

For 'Upload any Sage XML files here:' I browsed to the ExtractedInfo_sage.xml file.

For 'Directory Path To Import All XML (EX: D:\PVR_DATA):' I'm not sure.

If I leave it blank and try to do the query it says: is not a valid directory on the server

If I enter the path to where I save recordings to, D:\TV2, and try to do the query it says: Processing List of 0 Files:

There are over 300 files to import. So something not working correctly.

Has anyone done this recently and have it work?