Universal Media Server | Forum

Hi guys.

Firstly well done on release 5.0. This is one of the best opensource projects I use, and appreciate all the hard work that goes into the product.

Ok. I upgraded to the latest version of Java:

02-08 12:47:28 Build: a77bd3a90 (2015-01-25)
02-08 12:47:28 Java: Java HotSpot(TM) 64-Bit Server VM 1.8.0_31 64-bit by Oracle Corporation
02-08 12:47:28 OS: Windows 8 64-bit 6.2
02-08 12:47:28 Encoding: UTF-8
02-08 12:47:28 Memory: 683 MB
02-08 12:47:28 Language: en_uk

..and also did a clean install of UMS 5.0.0

Not sure if the new Java install has changed the default on Windows Firewall but the rules for 1.8.0_31 had the 2 inbound rules for TCP and UDP as 'blocked' rather than 'allowed' which took me a little while to discover. But that's sorted.

However the issue I have now is with the Web Interface.

All is fine using Chrome browser on a Windows PC. However on both iPhone and iPad I get the first splash page off http on port 9001, but on pressing the 'Browse the media on' area the splash page gives me a 'no data received' and an ERR_EMPTY_RESPONSE from Chrome. Similar story on Safari browser with 'Safari cannot open page......'.

The debug.log gives me this:

DEBUG 13:39:46.071 [pool-4-thread-10] Setting web client ua: Mozilla/5.0 (iPad; CPU OS 8_1_2 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) CriOS/40.0.2214.69 Mobile/12B440 Safari/600.1.4
DEBUG 13:39:46.071 [pool-4-thread-10] Adding status button for Safari
DEBUG 13:39:53.217 [pool-4-thread-16] Got a browse request found id
DEBUG 13:39:53.217 [pool-4-thread-16] Cookie 'UMS' not found: null
DEBUG 13:39:53.221 [pool-4-thread-16] Reading MediaInfo: true (default: false)
DEBUG 13:39:53.221 [pool-4-thread-16] Cookie 'UMSINFO' not found: null

So looks like some cookie not getting set.

Any help welcome.


Also for info the HTML5 rendering on Web Browser works, but you cannot use the seek controls to skip to any part of the video, also not had any luck trying to push rendering to 3rd party device. I seem to get 10's of repeated rows in the renderer list.

Thanks
ItsJustAGnome

bump - is it just me with this issue?

any help out there?

Thanks

It seems to me that you have running a SW or have a browser setting which doesn't allow saving cookies on your device. Regarding the HTML5 rendering the seek controls doesn't work in case the video is not supported by the HTML5 and it must be transcoded.

I've double checked the cookie settings on 2 IOS devices using both chrome and safari browsers and have the same result, so its not a browser setting issue.
Can someone else on IOS 8.1.2 verify if this is an issue with UMS 5.0.0 on Win8.1 and java 8?

Thanks

ItsOnlyAGnome2 wrote:I've double checked the cookie settings on 2 IOS devices using both chrome and safari browsers and have the same result, so its not a browser setting issue.
Can someone else on IOS 8.1.2 verify if this is an issue with UMS 5.0.0 on Win8.1 and java 8?

Thanks

This is all I get for both my iPhone w/iOS 8.1.2 and on my chrome browser on my pc.

The web interface is at the port 9001. I hope we will change it to 80 to be accessible as the standard web browser port.

valib wrote:The web interface is at the port 9001. I hope we will change it to 80 to be accessible as the standard web browser port.

I'm confused. You want us to change it to port 80 manually or that's what you hope will happen in a future update?

It is our task to change it in the future. Now the web interface is at the port 9001. In your case 192.168.0.16:9001

ItsOnlyAGnome, I have exactly the same problem "All is fine using Chrome browser on a Windows PC. However on both iPhone and iPad I get the first splash page off http on port 9001, but on pressing the 'Browse the media on' area the splash page gives me a 'no data received' and an ERR_EMPTY_RESPONSE from Chrome. Similar story on Safari browser with 'Safari cannot open page......'."

I am running the newext UMS 5.0.1 on Ubuntu with Java 8, and accessing it with an iPhone 5s. Tried using both Safari and Chrome on the iPhone

Unfortunately it is not optimized for smartphones yet.