Web Access problem
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Web Access problem
Hello . I have a problem when open http://192.168.1.128:5001 web page is blank.
How to fix it ? I am using Centos 6.5.
Code: Select all
INFO 2014-06-10 03:19:28.948 [main] Using address /192.168.1.128 found on network interface: name:eth0 (eth0)
INFO 2014-06-10 03:19:28.948 [main] Created socket: /192.168.1.128:5001
INFO 2014-06-10 03:19:29.310 [main] Using the following UUID configured in UMS.conf: aa516dd3-42c5-4941-be0f-d5892d706ed8
INFO 2014-06-10 03:19:29.774 [main] The server is now available for renderers to find
INFO 2014-06-10 03:19:32.133 [New I/O worker #1] No IP filter specified, access granted to /192.168.1.106
INFO 2014-06-10 03:19:32.145 [New I/O worker #1] Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36, Cache-Control: max-age=0
INFO 2014-06-10 03:19:32.398 [New I/O worker #1] Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36
INFO 2014-06-10 03:19:33.210 [New I/O worker #1] Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36
INFO 2014-06-10 03:19:33.242 [New I/O worker #1] Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36, Cache-Control: max-age=0
-
SharkHunter
- Developer
- Posts: 648
- Joined: Fri Jun 01, 2012 9:36 pm
Re: Web Access problem
What are you trying to do?
The 5001 port is what DLNA renders use when communicating with the server. They send SOAP requests and other messages over that port. It's not meant to be used from a regular web browser. If you wan't a web interface use 4.0.0 where there is a web interface implemented.
The 5001 port is what DLNA renders use when communicating with the server. They send SOAP requests and other messages over that port. It's not meant to be used from a regular web browser. If you wan't a web interface use 4.0.0 where there is a web interface implemented.
We reject: kings, presidents and voting.
We believe in: rough consensus and running code.
We believe in: rough consensus and running code.
Re: Web Access problem
Is there a version in 4.2.0 or 5.0.0-a1 ?
I only see 5001 as listening ports even if I put this in ~/.config/UMS/UMS.conf
web_port = 9001
web_enable = true
What am I doing wrong ?
Thanks in advance.
I only see 5001 as listening ports even if I put this in ~/.config/UMS/UMS.conf
web_port = 9001
web_enable = true
What am I doing wrong ?
Thanks in advance.
Re: Web Access problem
Nevermind. I'm dumb. I had something else listening on port 9001... The console should of yelled something that it can't start the web interface because of that ..