Plugin: SageTV Web Interface V2 for Jetty

[Islander]

Ok that explains that, yes sorry I am running both, by switching I mean switching from one tab of my web browser to the other, but I understand now why the webserver does not have that info.

[Hunter69]

I had the webserver plugin installed running on the tiny java web server. I followed the instructions to migrate to jetty v2. I maintained the 8080 port. I goto to my sage server

http:\\sageserver:8080\sage\home

the server responds by asking a user name and password. I understand the default user name=user, the default password=frey.

This is where I am stuck. It will not accept the username and password. I greatly appreciate your help in this matter.

Bill

[GKusnick]

Originally Posted by Hunter69

the server responds by asking a user name and password. I understand the default user name=user, the default password=frey.

Look in your realm.properties file (in SageTV/SageTV/jetty/etc) to find out the correct username and password.

[Hunter69]

The realm.properties states user frey.

[KarylFStein]

The default login is user=sage, password=frey. But you should change that .

[Hunter69]

Well after some digging, I found the server was still using the tiny java web server. So performed the steps again as descibed to migrate from tjws. Now I cannot connect at all. What kind of information could I provide that would allow someone to assist me in getting this working?

[jreichen]

These items would be helpful:

1. What is the value for the load_at_startup_runnable_classes line in Sage.properties?
2. Run it with SageTV's debug logging turned on and post the log here
3. Print a directory listing of the JARs and jetty folders

[Hunter69]

Ok I checked the sage.properties, it was missing the sagex from the startup line. This got jetty running. Now it wants to allow me to connect at

http://sageserver:8080

it does not like

http://sageserver:8080/sage

but if I put in

http://sageserver:8080/sagem


This is the one part of the instructions that I did not perform
it gets me to a directory page.

Iam researching how to do the debugging mode etc.

I read through this section in the instructions and felt that I would not be required to perform this step
Restore settings ¶

Skip this section if you are not migrating from TJWS to Jetty.

* webserver/realms.properties - the file no longer exists in this location. For Jetty, it's located in the jetty/etc folder. The 'user' role is the only supported role. Granting access to different URLs based on role is not currently supported.
* webserver/transcode.properties - replace or merge this file with the one installed when the zip file was extracted
* webserver/extenders.properties - replace or merge this file with the one installed when the zip file was extracted
* webserver/paths.properties - replace or merge this file with the one installed when the zip file was extracted
* Sage.properties, specifically these settings
o ssl keystore location (nielm/webserver/ssl_args) - set the keystore location in the JettyStarter.properties. See the Jetty SSL wiki page for instructions.
o http(s) port (nielm/webserver/port) - set the http and https ports in JettyStarter.properties. The corresponding properties in that file are jetty.port and jetty.ssl.port. Remove the '#' at the beginning of the line to uncomment them.

I manually adjusted the jettystarter.properties to listen on 8080. I did not have ssl enabled yet. Did I miss something that was critical?



I had not enabled SSL. So was thinking that this part was unnecessary. I adjusted the jettystarted.properties to listen on 8080 for now at least

[Hunter69]

Here is the error I get

HTTP ERROR: 404

Problem accessing /sage/home. Reason:

NOT_FOUND

Powered by Jetty://

[jreichen]

Originally Posted by Hunter69

Here is the error I get

HTTP ERROR: 404

Problem accessing /sage/home. Reason:

NOT_FOUND

Powered by Jetty://

Try Home with a capital "H"

[Hunter69]

Here is the debugging log

[Hunter69]

How do I do this

Print a directory listing of the JARs and jetty folders

[Hunter69]

Will this do

By the way I tried your suggestion with no different results.

Thanks again for all you help

[jreichen]

Jetty is set up and running just fine but you still have the files for the TJWS version of nielm's webserver installed. The set of files that are extracted are quite different for the TJWS version vs the Jetty version.

Go through the steps on the wiki again to clean up the TJWS version (especially cleaning up the JARs folder), and make sure you download the appropriate build - it's the 3rd download on the 1st post of this thread. Then do the installation of the Jetty version again.

[Hunter69]

Ok I am going through it again. I am clicking on the 3rd link down. It leads me to webserver_2_26_build49

Is that the correct file?

[jreichen]

No, the name should be something like nielm_websrv_jetty_2_x.zip.

[jreichen]

The links had a misspelling and were invalid so they were taking you to the downloads page with the list of all downloads rather than a specific file. Try them again.

[Hunter69]

Ok I think it is running off of Jetty. I can connect to it. How do I confirm it is using Jetty.

Thanks
Bill

[jreichen]

If your URL has the same port as JettyStarter.properties then it's running on Jetty.

[Hunter69]

I confirmed that Jetty is being used. Thank you very very much for your help and patience!

Bill