Jetty Web Server v3 released - plus more

[jusjoken]

The update of the Jetty Web Server to support Jetty 9 (old version was Jetty 6) is now completed and released.

IMPORTANT

This is an "All or nothing update"...most old apps will not work with Jetty 9 and the updated apps will not work with jetty 6. Please take the time to update Jetty and then each web app you use.


Install/Update process

• Install or update Jetty Web Server first, restart (if prompted), then install or update all web apps.
• goto http://yourIP:yourPort/apps (ie: http://localhost:8080/apps)

Troubleshooting

• Clear cache in web browser before running any of the updated web apps.
• Upload logs from - logs/jettystarter.log
• With SageTV stopped - clean out any FOLDERS from the jetty/webapps folder other than "apidocs" folder if that exists. Do NOT delete any of the .war FILES. Restart SageTV

Features/Changes

• Jetty 9...supports Java 8+
• new feature to set default app in plugin configuration
• new feature to disable login security in plugin confguration
• update to the /apps webapp
• enables future web app development

Recommended Java version = 8 or 11 (will not work with Java 7)
Note: Due to lack of direct support of Javascript in Java 16+, some web apps may not fully function...may review in future. Java 8 and 11 seem fine

Updates

• Jetty Starter - updated to Jetty 9.4.44
• SageTV Web Applications - lists and links to all web apps running on SageTV Jetty 9 server
• SageTV Web Interface - SkiingWiz has completed the update
• SageTV Mobile Web Interface - updated to support Jetty9
• Media Streaming Services - used by Mobile Web Interface
• SageTV Sagex API Extensions (sagex-api) - updated to Jetty9
• SageTV Sagex Remote API Services (sagex-services) - updated to Jetty9
• SageTV Swagger interface for Sagex remote api testing - updated to Jetty9 and newer swagger ui
• Batch Metadata Tools - Web Interface - updated to Jetty9
• SageAlerts - updated to work with Jetty9 (only works on Java 8)
• SJQ - tested and works with Jetty9
• SJQ Web UI - minor changes to allow to install with SageTV 9
• SRE - SkiingWiz updated to work with Jetty9

[jusjoken]

[hvymetal]

Nice Job...Thanks for your development

[MattHelm]

Thanks a bunch. I'm proud to be a member of your Patreon page!

[egeller]

So what do I change to remove the password requirement?

It used to be in the XML files in the ../jetty/contexts folder, but I see that they did not get updated. Therefore, I'm guessing that it is no longer used.

In the jettystarter.log I saw a note "updateJettyConfigFilesPropertyForJetty9 - No Extra Jetty configuration files are specified in Sage.properties".
Do I need to create an extra Jetty configuration and reference it in Sage.properties?

[wayner]

Originally Posted by egeller

So what do I change to remove the password requirement?

It used to be in the XML files in the ../jetty/contexts folder, but I see that they did not get updated. Therefore, I'm guessing that it is no longer used.

In the jettystarter.log I saw a note "updateJettyConfigFilesPropertyForJetty9 - No Extra Jetty configuration files are specified in Sage.properties".
Do I need to create an extra Jetty configuration and reference it in Sage.properties?

I thought that there was no way of removing the password in the previous version of the web server. There is a way of forming the URL with the username and password if that would work for you.

[jhkoenig]

So the Jetty update went very well, along with the other plugins, except for the SageTV Web Interface. It now shows:
HTTP ERROR 404 Not Found
URI: /sage/Home
STATUS: 404
MESSAGE: Not Found
SERVLET: -

Any thoughts on what I did wrong?

[jusjoken]

Originally Posted by egeller

So what do I change to remove the password requirement?

It used to be in the XML files in the ../jetty/contexts folder, but I see that they did not get updated. Therefore, I'm guessing that it is no longer used.

In the jettystarter.log I saw a note "updateJettyConfigFilesPropertyForJetty9 - No Extra Jetty configuration files are specified in Sage.properties".
Do I need to create an extra Jetty configuration and reference it in Sage.properties?

The short answer is you can't. I was unable to find a clean programmatic was to toggle off the security and the security setup is embedded inside the war and jar.

Can you detail your use case for this and I can spend more time to figure it out in the new jetty 9 model.

K

[jusjoken]

Originally Posted by jhkoenig

So the Jetty update went very well, along with the other plugins, except for the SageTV Web Interface. It now shows:
HTTP ERROR 404 Not Found
URI: /sage/Home
STATUS: 404
MESSAGE: Not Found
SERVLET: -

Any thoughts on what I did wrong?

Did you launch that from the apps list or from an old favorite?

[jhkoenig]

Originally Posted by jusjoken

Did you launch that from the apps list or from an old favorite?

Either way fails. It seems to be a pathing issue.

What used to be at:
http://192.168.1.49:8080/sage/Home

is now at:
http://192.168.1.49:8080/nielm_sagew...sage/menu.html

but, of course, all of the links point to the old locations.

[egeller]

Originally Posted by jusjoken

The short answer is you can't. I was unable to find a clean programmatic was to toggle off the security and the security setup is embedded inside the war and jar.

Can you detail your use case for this and I can spend more time to figure it out in the new jetty 9 model.

K

My use case is simple. I have no need for authentication within the confines of my home network. In the past, when the web interface was updated, I usually needed to apply the fix, described below, upon each update of the plug-in.

Below are my notes from my server maintenance documentation. In short, changing
<Set name="authenticate">true</Set>
to
<Set name="authenticate">false</Set>
in three xml files in ..jetty/contexts did the trick.
Notes start here
[passwords to false Sage Server]
to remove password requirement modfiy app.xml; also nielm_websrv.xml; also bmt.xml
set authenticate to false.
http://forums.sagetv.com/forums/show...ord#post449493

[jusjoken]

Originally Posted by jhkoenig

Either way fails. It seems to be a pathing issue.

What used to be at:
http://192.168.1.49:8080/sage/Home

is now at:
http://192.168.1.49:8080/nielm_sagew...sage/menu.html

but, of course, all of the links point to the old locations.

I see. I believe you have an old temp folder in the jetty webapps folder that needs to be deleted. SageTV may need to be stopped to delete it. It is likely named nielm...

[jhkoenig]

Originally Posted by jhkoenig

Either way fails. It seems to be a pathing issue.

What used to be at:
http://192.168.1.49:8080/sage/Home

is now at:
http://192.168.1.49:8080/nielm_sagew...sage/menu.html

but, of course, all of the links point to the old locations.

Problem solved. It turns out that updating or deleting the old Web Server plugin did not delete the files on the server. I deleted the plugin, then deleted the folder, installed the plugin, and everything works great.

Thanks for the hard work! It is great to have all the updated code!

[wayner]

Great work Ken. Thanks for keeping this going for everyone.

For everyone that is not already doing this then please make sure that you support Ken on Patreon. https://www.patreon.com/user?u=58035567

[jusjoken]

Originally Posted by egeller

My use case is simple. I have no need for authentication within the confines of my home network. In the past, when the web interface was updated, I usually needed to apply the fix, described below, upon each update of the plug-in.

Below are my notes from my server maintenance documentation. In short, changing
<Set name="authenticate">true</Set>
to
<Set name="authenticate">false</Set>
in three xml files in ..jetty/contexts did the trick.
Notes start here
[passwords to false Sage Server]
to remove password requirement modfiy app.xml; also nielm_websrv.xml; also bmt.xml
set authenticate to false.
http://forums.sagetv.com/forums/show...ord#post449493

I agree and support this and can look into a solution but it is the item I spent the most amount of time on already and did not find a solution. But will try

K.

[wayner]

Originally Posted by egeller

My use case is simple. I have no need for authentication within the confines of my home network. In the past, when the web interface was updated, I usually needed to apply the fix, described below, upon

Here is how I deal with this issue in a driver I wrote for my home automation system that uses the WebRemote to control SageTV.

All URLs include the username and password. Depending on how you are doing things this might work for you.

http://sage:frey@192.168.1.251:8080/...tServerAddress

To get to the home page of the SageTV web UI you would use:
http://sage:frey@192.168.1.251:8080/sage/Home

You might be able to set up some other way, like a reverse proxy, to insert the userass as a prefix to the URL.

[Eternal]

completely broken for me on 32 bit sage 9.2.6.976

503 error as soon as I updated the plugin.

uninstalled all plugins that depended on jetty and deleted jetty folder and jar files and only installed jetty and the web interface and still 503. Url automatically adds the /apps to 127.0.0.1:8081 but nothing loads

solved: didnt want to redo all the settings and tuner info by nuking everything so did a clean install on a vm and installed all the exact same plugins then copied over the jar, jetty, webserver folders so it works now, not sure what the problem was

[jusjoken]

Originally Posted by Eternal

completely broken for me on 32 bit sage 9.2.6.976

503 error as soon as I updated the plugin.

uninstalled all plugins that depended on jetty and deleted jetty folder and jar files and only installed jetty and the web interface and still 503. Url automatically adds the /apps to 127.0.0.1:8081 but nothing loads

solved: didnt want to redo all the settings and tuner info by nuking everything so did a clean install on a vm and installed all the exact same plugins then copied over the jar, jetty, webserver folders so it works now, not sure what the problem was

Glad you worked it out and sorry for your pain...this was/is a massive update.

K

[DarkWolf77]

I seem to be getting an error updating SageTV Web interface to 4.0.0... I'm getting a FAILED resource download error for the sage-webui-jar-4.0.0.zip file. When I manually type the url into a browser, it's just timing out.


Edit: Nevermind! Seems that my firewall is the culprit. Disabling it for a second fixed it long enough to let it run.

[jusjoken]

Originally Posted by DarkWolf77

I seem to be getting an error updating SageTV Web interface to 4.0.0... I'm getting a FAILED resource download error for the sage-webui-jar-4.0.0.zip file. When I manually type the url into a browser, it's just timing out.

I imagine it was just an issue with bitbucket where the file is. I just tried it and the zip was available.

K