Page 1 of 1

[Solved] UMS v5: Bubble UPnP Server doesn't see UMS server

Posted: Tue Jan 27, 2015 9:37 pm
by Airborne1
Hi folks,

after updating from latest v4 to v5, I noticed that Bubble UPnP server software does not see the UMS Server anymore...

Should I provide debug files?

BR.

Re: UMS v5: Bubble UPnP Server doesn't see UMS server

Posted: Wed Jan 28, 2015 7:08 pm
by AdamBomb
Im having the same problem. Also, when trying to queue a large folder in BubbleUPnP, it fails and no tracks are added. Did not happen in 4.4.0
Right now I am uninstalling and searching for a link to old version

Re: UMS v5: Bubble UPnP Server doesn't see UMS server

Posted: Thu Jan 29, 2015 11:31 am
by sombudy
Here's the problem (I think):
https://github.com/UniversalMediaServer ... ng+request
https://github.com/UniversalMediaServer ... t-63388840

Code: Select all

		// FIXME: this would also block an external cling-based client running on the same host
		boolean isSelf = ia.getHostAddress().equals(PMS.get().getServer().getHost()) &&
			nettyRequest.headers().get(HttpHeaders.Names.USER_AGENT) != null &&
			nettyRequest.headers().get(HttpHeaders.Names.USER_AGENT).contains("Cling/");

		// Filter if required
		if (isSelf || filterIp(ia)) {
			LOGGER.trace(isSelf ?
				("Ignoring self-originating request from " + ia + ":" + remoteAddress.getPort()) :
				("Access denied for address " + ia + " based on IP filter"));
			return;
		}
From: https://github.com/UniversalMediaServer ... lerV2.java

It seems that UMS is blocking Bubble because it is a cling-based client, but I don't see Cling/ in the useragent:

Code: Select all

TRACE 2015-01-28 16:30:16.674 [New I/O worker #18] Received on socket: User-Agent: Windows7/6.1 UPnP/1.0 BubbleUPnPServer/0.9-update4
TRACE 2015-01-28 16:30:16.674 [New I/O worker #18] Using default media renderer: SGS4
INFO  2015-01-28 16:30:16.674 [New I/O worker #18] Media renderer was not recognized. Possible identifying HTTP headers: User-Agent: Windows7/6.1 UPnP/1.0 BubbleUPnPServer/0.9-update4
sombudy wrote:After updating UMS from 4.40 to 5.00, BubbleUPnP Server has been unable to connect to UMS because it now ignores self-originating requests.

Code: Select all

Build: 9ea9f7856 (2015-01-10)
Java: Java HotSpot(TM) 64-Bit Server VM 1.8.0_31 64-bit by Oracle Corporation
OS: Windows 7 64-bit 6.1
Encoding: UTF-8
Memory: 1138 MB
Language: en

Code: Select all

DEBUG 17:51:29.695 [UPNP-AliveMessageSender] Sending ALIVE...
TRACE 17:51:29.697 [New I/O worker #13] Ignoring self-originating request from /MyIP:1625
TRACE 17:51:29.698 [New I/O worker #14] Ignoring self-originating request from /MyIP:1626
TRACE 17:51:37.319 [UPNPHelper] Sending discovery [MyIP:62704]: HTTP/1.1 200 OK<CRLF>CACHE-CONTROL: max-age=1200<CRLF>DATE: Mon, 26 Jan 2015 01:51:37 GMT<CRLF>LOCATION: http://MyIP:5001/description/fetch<CRLF>SERVER: Windows_7-amd64-6.1, UPnP/1.0, UMS/5.0.0<CRLF>ST: urn:schemas-upnp-org:service:ContentDirectory:1<CRLF>EXT: <CRLF>USN: uuid:UMS::urn:schemas-upnp-org:service:ContentDirectory:1<CRLF>Content-Length: 0<CRLF><CRLF>
TRACE 17:51:37.319 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:37.321 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:37.322 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:37.332 [New I/O worker #3] Ignoring self-originating request from /MyIP:1692
TRACE 17:51:37.333 [New I/O worker #4] Ignoring self-originating request from /MyIP:1693
TRACE 17:51:37.334 [New I/O worker #5] Ignoring self-originating request from /MyIP:1694
TRACE 17:51:37.335 [New I/O worker #6] Ignoring self-originating request from /MyIP:1695
TRACE 17:51:37.819 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:37.819 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:37.822 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:37.822 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:37.823 [New I/O worker #7] Ignoring self-originating request from /MyIP:1696
TRACE 17:51:37.824 [New I/O worker #8] Ignoring self-originating request from /MyIP:1697
TRACE 17:51:37.825 [New I/O worker #9] Ignoring self-originating request from /MyIP:1698
TRACE 17:51:37.826 [New I/O worker #10] Ignoring self-originating request from /MyIP:1699
TRACE 17:51:38.319 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:38.319 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:38.322 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:38.322 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:38.323 [New I/O worker #11] Ignoring self-originating request from /MyIP:1706
TRACE 17:51:38.324 [New I/O worker #12] Ignoring self-originating request from /MyIP:1707
TRACE 17:51:38.325 [New I/O worker #13] Ignoring self-originating request from /MyIP:1708
TRACE 17:51:38.327 [New I/O worker #14] Ignoring self-originating request from /MyIP:1709
TRACE 17:51:38.832 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:38.833 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:38.834 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:38.835 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:38.837 [New I/O worker #15] Ignoring self-originating request from /MyIP:1710
TRACE 17:51:38.839 [New I/O worker #16] Ignoring self-originating request from /MyIP:1711
TRACE 17:51:38.840 [New I/O worker #1] Ignoring self-originating request from /MyIP:1712
TRACE 17:51:38.840 [New I/O worker #2] Ignoring self-originating request from /MyIP:1713
TRACE 17:51:39.332 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:39.333 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:39.334 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:39.335 [UPNPHelper] Resending last discovery [MyIP:62704]
TRACE 17:51:39.336 [New I/O worker #3] Ignoring self-originating request from /MyIP:1717
TRACE 17:51:39.337 [New I/O worker #4] Ignoring self-originating request from /MyIP:1718
TRACE 17:51:39.337 [New I/O worker #5] Ignoring self-originating request from /MyIP:1719
TRACE 17:51:39.339 [New I/O worker #6] Ignoring self-originating request from /MyIP:1720
DEBUG 17:51:39.867 [cling-15] BubbleUPnPServer found: (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:Bubble, Descriptor: http://MyIP:1640/dev/Bubble/desc.xml, Root: true
DEBUG 17:51:49.695 [UPNP-AliveMessageSender] Sending ALIVE...
TRACE 17:51:49.697 [New I/O worker #7] Ignoring self-originating request from /MyIP:1780
TRACE 17:51:49.698 [New I/O worker #8] Ignoring self-originating request from /MyIP:1781
TRACE 17:51:49.698 [New I/O worker #9] Ignoring self-originating request from /MyIP:1782
TRACE 17:51:49.698 [New I/O worker #10] Ignoring self-originating request from /MyIP:1783
TRACE 17:51:49.700 [New I/O worker #11] Ignoring self-originating request from /MyIP:1784
TRACE 17:51:49.700 [New I/O worker #12] Ignoring self-originating request from /MyIP:1785
TRACE 17:51:49.700 [New I/O worker #13] Ignoring self-originating request from /MyIP:1786
TRACE 17:51:49.701 [New I/O worker #14] Ignoring self-originating request from /MyIP:1787
TRACE 17:51:49.701 [New I/O worker #15] Ignoring self-originating request from /MyIP:1788
TRACE 17:51:49.701 [New I/O worker #16] Ignoring self-originating request from /MyIP:1789
Link to BubbleUPnP Server:
http://www.bubblesoftapps.com/bubbleupnpserver/#faq

Please allow self-originating requests so I can use the latest version of UMS.
viewtopic.php?f=3&t=2901&p=14476#p14476


AdamBomb wrote:Im having the same problem. Also, when trying to queue a large folder in BubbleUPnP, it fails and no tracks are added. Did not happen in 4.4.0
Right now I am uninstalling and searching for a link to old version
Link to all versions of UMS:
http://sourceforge.net/projects/unimedi ... 0Releases/

Re: UMS v5: Bubble UPnP Server doesn't see UMS server

Posted: Fri Jan 30, 2015 1:21 am
by Airborne1
Hi,

an update of the Bubble UPnP Server is now available that fixes the problem (0.9-update4).

Tx.