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

[rickgillyon]

Originally Posted by Thomas Wischgol

I only get a message "error in menu_items.js: check syntax".

What browser are you using?
Is it up-to-date?
You tried a reinstall?

[nielm]

Originally Posted by jimmyb

Thanks for your reply Gerry. That is what I thought I USED to do. Now what would cause it to stop? I can only log on when Sage is runing or sleeping.

This suggests that either
you are *not* running the service...
or
you have configured the webserver in SageClient.properties (used by the GUI frontend in service mode), not in Sage.properties (used by the service)
or
you ahve configured it on both, with different ports, and are using the wrong port.
or
the service is failing to start...

Run SageTV Service control app and see what the status is.
Or right click My Computer -> Manage -> Services+apps -> Services -> SageTV and check the status...

The GUI front end should auto-start the service if it is enabled...

[jimmyb]

Originally Posted by Thomas Wischgol

After upgrading to version 4.1.3 the menus of the web server do not work anymore. I only get a message "error in menu_items.js: check syntax". I checked the file and it looks okay to me. Is there anybody else having this problem?

Thomas

Rick if you read my previous posts up on the previuos page, I had the same problem. I was entering ......sage/home/ instead of ......sage/home (no trailing slash). Simple fix but was operator error.

[jimmyb]

Nielm - I guess it is working ... but

I have Sage.prop at port 8080 and per our previous discussions the Client.prop setup at 8090. I also purchased a Client license (if this effects anything).

With services running and Sagetv closed I can log on as 8080 and see all BUT I cannot watch Live TV (control Sage / Play TV) as I can when I log on using the Client port. When I log on as Client port 8090 I get an error message .." The connection was refused when attempting .........."\

If Sage is running I can then log on with client port 8090 and all works well including the Play TV feature. Is this the way it works?

[Thomas Wischgol]

Originally Posted by rickgillyon

What browser are you using?
Is it up-to-date?
You tried a reinstall?

I tried it with Mozilla and Internet Explorer, both are up-to-date. I reinstalled the webserver but this did not change anything. The only thing I noticed is that if I put additional html files into the webroot folder I only get an empty body when I try to access it through a web browser.

I checked the log files this morning and found this message:
Server socket: java.net.BindException: Address already in use: JVM_Bind

I get this message every time I restart Sage after I upgraded. This sounds like some kind of conflict somewhere but I do not really have an idea what it might be at this point. Any ideas?

Thanks,
Thomas

[Thomas Wischgol]

Originally Posted by Thomas Wischgol

I checked the log files this morning and found this message:
Server socket: java.net.BindException: Address already in use: JVM_Bind

I get this message every time I restart Sage after I upgraded. This sounds like some kind of conflict somewhere but I do not really have an idea what it might be at this point. Any ideas?

I just checked the processes that use port 8080 and it was SageTVServer. I enabled service mode during my last install and it seems to have copied to config files so that both the server and the client tried to start the webserver. After adjusting this issue, however, I still get the same error messages

Thomas

[mkanet]

I'm not sure what's going on. Can people see my posts here in this thread? Or perhaps nobody subscribed to this thread has answers to my questions about enabling SSL? I don't think my questions were that complicated. I already tried my best to figure this out on my own and through Wiki documentation...

Would somebody be kind enough to please help?

Originally Posted by mkanet

I need a little bit of help getting it to run in SSL mode.

In the Wiki documentation, it says to:

Set the property nielm/webserver/port=8443
Set the property nielm/webserver/ssl_args= with arguments from the following list
-keystoreFile (default %HOME%/.keystore
-keystorePass (default 123456)
-keystoreType (default JKS)
-algorithm (default SunX509)
-clientAuth (default false)
-port (default 8443)
-protocol (default TLS)
-backlog (default 1000)
-ifaddress (default none)


There is no sample provided for the ssl_args= command-line.

Can somebody please confirm that the below syntax is correct?
ssl_args= -keystoreFile %HOME%/.keystore, -keystorePass 123456

Also, the web pages I go to that are secure use port 443. Why is the
default port set to 8443? If I set it to 443, can I point my web browser to:

https://localhost/sage/Home

I'm guessing when typing HTTPS in the web browser, its not needed to also specify a port #. Right?

Thanks in advance!

[ellweber]

This is what my Sage Client Properties file contains:

nielm/webserver/aliases_file=aliases.properties
nielm/webserver/backlog=
nielm/webserver/bind_address=
nielm/webserver/cgibin_dir=
nielm/webserver/charset=UTF-8
nielm/webserver/enableSageEncoderOpts=false
nielm/webserver/log_access=false
nielm/webserver/log_referrer=false
nielm/webserver/log_user_agent=false
nielm/webserver/port=443
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 .keystore
nielm/webserver/throttles_file=throttles.properties
nielm/webserver/use_ssl=true
nielm/webserver/video_path_translation_file=paths.properties

This is a working intallation with SSL. The .keystore file is located in C:\Program Files\SageTV\SageTV

I just followed the documentation and particularly the .keystore generation proceedure found here: http://www.sage-community.org/index....i/WebserverSsl

Also, you might want to consider extending the validity beyend 900. I fell into that trap for few hours once!

Hope this helps a little.

Lynn

[mkanet]

Thank you Lynn! It looks like I have enough information now. It also looks like your config uses the standard port 443 verses 8443. I'm guessing its as simple as pointing a webbrowser to:

https://localhost/sage/Home ???

So currently, the only way to make this work is with an "unsigned certificate"?

Thanks again for helping!!

[gplasky]

Originally Posted by mkanet

Thank you Lynn! It looks like I have enough information now. It also looks like your config uses the standard port 443 verses 8443. I'm guessing its as simple as pointing a webbrowser to:

https://localhost/sage/Home ???

So currently, the only way to make this work is with an "unsigned certificate"?

Thanks again for helping!!

Also keep this in mind: Note: Setting the port number in both "nielm/webserver/port=" and "nielm/webserver/ssl_args=" can cause the webserver to not respond. Try to just set the port using the "nielm/webserver/port=" line when using SSL.

Gerry

[rickgillyon]

Originally Posted by mkanet

I'm not sure what's going on. Can people see my posts here in this thread?

Who said that?

[nielm]

Originally Posted by jimmyb

I have Sage.prop at port 8080 and per our previous discussions the Client.prop setup at 8090.
...
With services running and Sagetv closed I can log on as 8080 and see all BUT I cannot watch Live TV (control Sage / Play TV) as I can when I log on using the Client port. When I log on as Client port 8090 I get an error message .." The connection was refused when attempting .........."\

If Sage is running I can then log on with client port 8090 and all works well including the Play TV feature. Is this the way it works?

yep.

The webserver running in the server/service on port 8080 cannot control the client (as it is a separate process)

The webserver running in the client on port 8090 needs the client to be running for it to be running

[Homebuilder]

I had trouble accessing from the internet, I found a way that worked for me...I added :8080 to the address line

So instead of xxx.xxxxxxxx.net/sage/home

I used xxx.xxxxxxxx.net:8080/sage/home

I am behind a linksys router..not sure if thats why... but it now works.

[Homebuilder]

Hi,

Got my server up and running, yippie!!!

Really looking forward to exploring this more... Quick question, request or bug submission...

I put alot of files in my import folders....divx movies, tv series in divx... any way to just browse all items in folders? will it support folder in folder browsing?

When I do a search, my files do all come up, but so does all of my hauppauge inputs..example:

Hauppauge WinTV PVR PCI II Capture #2 Composite Fri, Dec 16
6:03 PM - 6:03 PM -

Hauppauge WinTV PVR PCI II Capture #2 Composite Fri, Dec 16
6:03 PM - 6:03 PM -

Hauppauge WinTV PVR PCI II Capture #2 Composite_2 Fri, Dec 16
6:03 PM - 6:03 PM -

Hauppauge WinTV PVR PCI II Capture #2 Composite_2 Fri, Dec 16
6:03 PM - 6:03 PM

etc etc etc etc...

This is an awesome plug in just as it is. If it is possible to browse files and folders like in windows, that would be great, if not, is it possible to not have tuner inputs show on searches?

Thanks again for a great tool!

[mkanet]

I followed the instructions on Wiki PERFECTLY. I quadruple checked the steps to make sure I have no errors. I checked my browser settings for SSL and recreated .keystore several times.

I even tried to do it the way mentioned above (putting keystore file in sage dir). I immediately get the error popup below:


So, what am I doing wrong? I'm pulling my hair out trying to figure out why following the directlons EXACTLY doesnt work.

PLEASE help. I'm completely stuck!

EDIT: I about to just give up. I tried it one last time and everything started working!!! Maybe something got stuck who knows? Lesson learned: Following directions PERFECTLY does work

[mkanet]

Okay, I found out the problem. But I need help to solve the problem:

If I use port 8443 (or ANY other port except for 443), I am able to login via SSL.

However, if I change "nielm/webserver/port=8443" to "nielm/webserver/port=443", the web browser acts as if there is no server to be found.

Would having IIS installed complicate things? I disabled IIS, but still got a message saying unable to connect.

[gplasky]

Port 443 is also used by RPC. Do you remote desktop into that machine?

Gerry

[mkanet]

Yes, I remote control to my machine.

Hmm.. that's strange, the remote control port that I had to open up on my router was 3389 in order for Remote Desktop to work. Are you "sure" what you're saying is true?

[gplasky]

Originally Posted by mkanet

Yes, I remote control to my machine.

Hmm.. that's strange, the remote control port that I had to open up on my router was 3389 in order for Remote Desktop to work. Are you "sure" what you're saying is true?

Sorry-my mistake. Another source just listed it as RPC over HTTP. That port is used for Exchange.
TCP Port 443 - HTTPS HTTP SSL
TCP Port 443 - HTTPS World Wide Web Publishing Service
TCP Port 443 - HTTPS SharePoint Portal Server
TCP Port 443 - RPC over HTTP Exchange Server 2003

Those are the default uses of that port by Microsoft. I'm assuming you're not running Sharepoint on that server either.

Gerry

[mkanet]

I dont have Sharepoint, Frontpage extensions for authoring, nor exchange.

Edit: Opps.. Well, I have IIS running, with the WWW publishing service for http... It looks like XP's SSL service it turned off and set to manual

Last Edit: I'm going to run a port scan to see if there's something using 443 currrently. I'm not sure if this is the case, but makes most sense to me. I have a gut feeling it's somehow related to IIS (even though XP SSL service it not active).

Whatever it is, ONLY port 443 isn't allowed and gives the error.