|
SageTV v9 Customizations This forums is for discussing and sharing user-created modifications for the SageTV version 9 application created by using the SageTV Studio or through the use of external plugins. Use this forum to discuss plugins for SageTV version 9 and newer. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
SageTV Web Interface
I've installed the version 3.1 plugin via the main menu. When I choose 'View web site 1' or 'View web site 2' nothing happens.
Is there a how-to on setting this thing up? Last edited by youngster; 12-19-2016 at 08:24 AM. |
#2
|
||||
|
||||
navigate to your server at http://[server's ip]:8080/sage/Home
Case does matter on the sage/Home default username:password is sage:frey
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
#3
|
|||
|
|||
Doesn't work for me at all. I get HTTP ERROR 404 /sage/home NOT_FOUND
Is there really no documentation on how to setup this plugin? UPDATE: I got it working by leaving off 'home' from the pathname. Last edited by youngster; 12-21-2016 at 10:07 AM. |
#4
|
||||
|
||||
It is being re-written at some point to work with java 8. For now you can go to your IP port 8080 and it will show you what web pages are available
__________________
SageTV Server: unRAID Docker v9, S2600CPJ, Norco 24 hot swap bay case, 2x Xeon 2670, 64 GB DDR3, 3x Colossus for DirecTV, HDHR for OTA Living room: nVidia Shield TV, Sage Mini Client, 65" Panasonic VT60 Bedroom: Xiomi Mi Box, Sage Mini Client, 42" Panasonic PZ800u Theater: nVidia Shield TV, mini client, Plex for movies, 120" screen. Mitsubishi HC4000. Denon X4300H. 7.4.4 speaker setup. |
#5
|
||||
|
||||
As posted above, it is case sensitive, so home is not the same as Home.
__________________
Server: Ryzen 2400G with integrated graphics, ASRock X470 Taichi Motherboard, HDMI output to Vizio 1080p LCD, Win10-64Bit (Professional), 16GB RAM Capture Devices (7 tuners): Colossus (x1), HDHR Prime (x2),USBUIRT (multi-zone) Source: Comcast/Xfinity X1 Cable Primary Client: Server Other Clients: (1) HD200, (1) HD300 Retired Equipment: MediaMVP, PVR150 (x2), PVR150MCE, HDHR, HVR-2250, HD-PVR |
#6
|
|||
|
|||
Well I tried both home and Home, of course. Neither worked. If I left off home entirely from the path it worked just fine.
|
#7
|
||||
|
||||
Check to be sure Windows Firewall is allowing the required ports to be open to the network.
Also if you are trying access from 'outside' your network then a forwarding rule will need to be applied to your router. Just random thoughts I have ...
__________________
SERVER: Intel Core i7-3770 CPU @ 3.40GHz - UnRaid Server 6.8.0/DVB LibreELEC with Docker stuckless-sagetv-server-java9 MOTHERBOARD: ASRock-Z77 Extreme4 / 32GB RAM CACHE DRIVE: SSD 1TB ARRAY: 24TB/7 DRIVES PARITY: 8TB EXTERNAL DEVICES: 4x HD-PVR's Firewire Channel Changing TUNERS:NO LONGER RECORDING LIVETV CLIENTS: 2xHD300 2xHD200 SONY ANDROIDTV MINI-CLIENT |
#8
|
||||
|
||||
Quote:
Is it possible I uninstalled a plugin or altered a support file? I've never had a problem with the Web Interface until now...
__________________
Sage 9 server = Gigabyte AMD quad-core - 4 gigs - integrated ATI HD4200 chipset - SSD boot, Hitachi Deskstar show drives. HD-PVR - Colossus - Win7 32 bit. HD200/300’s networked. HDHomerun tuner. "If you've given up on Weird Al, you've given up on life" - Homer Simpson Last edited by tvmaster2; 01-05-2017 at 01:06 PM. |
#9
|
||||
|
||||
Quote:
HTTP ERROR: 503 Problem accessing /sage/home. Reason: SERVICE_UNAVAILABLE Powered by Jetty:// I checked to make sure my ports are still open (yes), that the password and user are properly entered (yes), but I am missing something. Or, did a Java update kill it? any clues would be helpful - thanks
__________________
Sage 9 server = Gigabyte AMD quad-core - 4 gigs - integrated ATI HD4200 chipset - SSD boot, Hitachi Deskstar show drives. HD-PVR - Colossus - Win7 32 bit. HD200/300’s networked. HDHomerun tuner. "If you've given up on Weird Al, you've given up on life" - Homer Simpson |
#10
|
|||
|
|||
Do you have java 7 installed on that machine as I had trouble with the web interface until I reinstalled it on the machine with sage tv installed on it and then it finally worked for me.
|
#11
|
||||
|
||||
I believe I am up to Java 8. Maybe that's it....
__________________
Sage 9 server = Gigabyte AMD quad-core - 4 gigs - integrated ATI HD4200 chipset - SSD boot, Hitachi Deskstar show drives. HD-PVR - Colossus - Win7 32 bit. HD200/300’s networked. HDHomerun tuner. "If you've given up on Weird Al, you've given up on life" - Homer Simpson |
#12
|
|||
|
|||
I had the same problems as you with only java 8 on the machine with sage tv on it and once i installed java 7 the web interface worked again
I bet that will fix it with your machine too as that plugin still uses java 7 i believe. |
#13
|
|||
|
|||
when I try to install via the main menu it says FAILED
|
#14
|
|||
|
|||
Quote:
I have tried to access it from machines both on 1.7 and 1.8 java. The SageTV server has 1.7u80. When I put in http://home ip:8080 I get: Error 404 - Not Found. No context on this server matched or handled this request. Contexts known to this server are: / ---> org.mortbay.jetty.handler.ContextHandler@f44f81{/,file:/C:/Program%20Files%20(x86)/SageTV/SageTV/jetty/static} /stream ---> org.mortbay.jetty.webapp.WebAppContext@e15d63{/stream,C:\Program Files (x86)\SageTV\SageTV\jetty/webapps/MediaStreaming.war} If I put in http://192.168.1.101:8080/sage/Home, I get: HTTP ERROR: 404 Problem accessing /sage/Home. Reason: NOT_FOUND Powered by Jetty:// It appears like jetty is unable to find a file that should be there. I've tried uninstalling and reinstalling the plugins to no effect. What logs would be helpful to produce? There's a jetty log and sagetv log. Jetty log shows these requests are definitely received, so it's not a firewall issue: 192.168.1.230 - - [19/Jan/2017:08:21:58 +0000] "GET /sagem/m/menu.jsp HTTP/1.1" 404 1284 "-" "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36" 192.168.1.230 - - [19/Jan/2017:08:22:00 +0000] "GET /sage/Home HTTP/1.1" 404 1277 "-" "Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36" sagetv log shows the same thing, not much more detail: Thu 1/19 0:21:58.325 [16468404@qtp-33058319-8 - /sagem/m/menu.jsp@fb49b4] :EBUG: REQUEST /sagem/m/menu.jsp on org.mortbay.jetty.HttpConnection@14f2964 Thu 1/19 0:21:58.339 [16468404@qtp-33058319-8 - /sagem/m/menu.jsp@fb49b4] :EBUG: RESPONSE /sagem/m/menu.jsp 404 Thu 1/19 0:22:00.095 [16468404@qtp-33058319-8 - /sage/Home@fb49b4] :EBUG: REQUEST /sage/Home on org.mortbay.jetty.HttpConnection@14f2964 Thu 1/19 0:22:00.098 [16468404@qtp-33058319-8 - /sage/Home@fb49b4] :EBUG: RESPONSE /sage/Home 404 @tvmaster2, did you figure it out for you? Though it seems like yours is slightly different, a 503 vs 404 error.
__________________
Server: SageTV 9.2.6x64 on Win10 x64 Home, i7-2600, 8gb RAM, OpenDCT, Java 1.8, 20TB storage Display: EVGA GT 1030 fanless to Sony LED TV via DVI-HDMI Capture Devices: HDHR Prime for Comcast, HDHR Dual for OTA (retired) Clients: Nvidia Shield Android miniclient Last edited by waylo; 01-19-2017 at 02:40 AM. |
#15
|
||||
|
||||
Quote:
This is what I am greeted with: HTTP ERROR: 503 Problem accessing /sage. Reason: SERVICE_UNAVAILABLE Powered by Jetty:// PS - and it's kinda pissing me off that I can't get access remotely anymore to check recordings, schedule new ones, etc, from either a browser or my Android phone. And when I try and look at basic installation instructions linked from the plugin, most of the pages are 404. So that helps
__________________
Sage 9 server = Gigabyte AMD quad-core - 4 gigs - integrated ATI HD4200 chipset - SSD boot, Hitachi Deskstar show drives. HD-PVR - Colossus - Win7 32 bit. HD200/300’s networked. HDHomerun tuner. "If you've given up on Weird Al, you've given up on life" - Homer Simpson Last edited by tvmaster2; 01-19-2017 at 01:46 PM. |
#16
|
|||
|
|||
I'm looking through some older SageTV threads about this issue. It seems like Jetty is just not behaving as expected.
Some of the older threads with workthroughs (searching for webserver + 404): https://forums.sagetv.com/forums/showthread.php?t=63283 https://forums.sagetv.com/forums/showthread.php?t=57387 https://forums.sagetv.com/forums/showthread.php?t=63509 Since some of my error logs do show SageTV looking for a missing jetty/static, I will try making a directory there with an index.html file, listed in the first referred thread. Other troubleshooting I will do involve Java heap not being large enough. Another suggestion was to go UP to v1.8 java (might break the directory link but the apps will work). (But I literally did not change anything with Java or my system before my Sagetv9 upgrade). EDIT: 1. I made a jetty/static directory and put in a sample index.html. All this does is make a webpage with link to the webapp locations, which still don't work. I think there's something limiting jetty from expanding and making these apps functional when SageTV runs. Many other old thread posts by @stuckless advise removing the app directories within /jetty/webapps and letting them be re-formed when SageTV runs. The folders are remade but the contents stay EMPTY. 2. My java heap has already been enlarged to 1024.
__________________
Server: SageTV 9.2.6x64 on Win10 x64 Home, i7-2600, 8gb RAM, OpenDCT, Java 1.8, 20TB storage Display: EVGA GT 1030 fanless to Sony LED TV via DVI-HDMI Capture Devices: HDHR Prime for Comcast, HDHR Dual for OTA (retired) Clients: Nvidia Shield Android miniclient Last edited by waylo; 01-19-2017 at 08:22 PM. |
#17
|
||||
|
||||
Quote:
__________________
Sage 9 server = Gigabyte AMD quad-core - 4 gigs - integrated ATI HD4200 chipset - SSD boot, Hitachi Deskstar show drives. HD-PVR - Colossus - Win7 32 bit. HD200/300’s networked. HDHomerun tuner. "If you've given up on Weird Al, you've given up on life" - Homer Simpson |
#18
|
|||
|
|||
Are you in a client or the server? I think it may display differently.
__________________
Server: SageTV 9.2.6x64 on Win10 x64 Home, i7-2600, 8gb RAM, OpenDCT, Java 1.8, 20TB storage Display: EVGA GT 1030 fanless to Sony LED TV via DVI-HDMI Capture Devices: HDHR Prime for Comcast, HDHR Dual for OTA (retired) Clients: Nvidia Shield Android miniclient |
#19
|
||||
|
||||
server
__________________
Sage 9 server = Gigabyte AMD quad-core - 4 gigs - integrated ATI HD4200 chipset - SSD boot, Hitachi Deskstar show drives. HD-PVR - Colossus - Win7 32 bit. HD200/300’s networked. HDHomerun tuner. "If you've given up on Weird Al, you've given up on life" - Homer Simpson |
#20
|
|||
|
|||
I looked and also did not see an uninstall option. On my system, it is used by sagex-services, BMT, sagetv mobile web interface, media streaming services, and Sagetv web interface, so it's linked to many other plugins. Not sure if uninstalling all of them would open that option.
EDIT: Okay, I figured it out. For some reason with the upgrade, something happens to jetty in that it just won't recognize/initialize those plugins. (Also, an additional extension sagex-api wasn't running). I have the plugin "remove plugin and dependencies" installed, a fantastic tool for determining what dependencies are associated with each plugin. As noted above, I had several plugins associated with jetty. I uninstalled all of them, making sure to select the "Uninstall plugin and unneeded dependencies" option. Eventually, jetty was uninstalled. Restart Sage, and re-install the plugins you had previously uninstalled. Done!
__________________
Server: SageTV 9.2.6x64 on Win10 x64 Home, i7-2600, 8gb RAM, OpenDCT, Java 1.8, 20TB storage Display: EVGA GT 1030 fanless to Sony LED TV via DVI-HDMI Capture Devices: HDHR Prime for Comcast, HDHR Dual for OTA (retired) Clients: Nvidia Shield Android miniclient Last edited by waylo; 01-19-2017 at 11:06 PM. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
SageTV Web Interface | Praktikant | SageTV Germany | 0 | 07-23-2011 10:06 AM |
SageTV Web Interface (BMT) | micjgeoghegan | Batch Metadata Tools | 1 | 12-29-2010 03:49 PM |
Causes for sluggish SageTv interface? | tvmaster2 | Hardware Support | 13 | 07-27-2009 10:09 PM |
New SageTV Interface | matrix35 | SageTV Software | 183 | 12-08-2007 02:51 AM |
SageTV interface suggestions | malore | SageTV Software | 2 | 08-08-2003 10:24 AM |