BubbleUpnp Server access from foobar2000 iOS is broken ?

[Arnaud Vié]

Hi,

For several years I've been using BubbleUpnp Server to make music from my NAS available from outside.

Using BubbleUpnp for Android, the setup has always worked flawlessly, and still does - just by setting the URL to :
https://<myIp>:58051

(with proper port forwarding on my router of course)

Using foobar2000 on iOS, it used to work by creating a remote library with the URL :
http://<myIp>:58050/DeviceDescription.xml

(HTTPS never worked, possibly because foobar2000 does not trust the bubbleupnp certificate)

However, I recently changed to a new NAS and, since reinstalling BubbleUpnp server on it (using the QNAP package from your website that contains version 0.9-update50 ), everything works great with BubbleUpnp for android, but I couldn't make it work again with foobar2000.

Possibly related, when I load the DeviceDescription.xml URL in my browser, it redirects to SuperMediaServer/DeviceDescription.xml, then returns a 403 "Remote access is not allowed".
But the "Allow to access the server from the Internet" is enabled in the config - and remote access works fine with BubbleUpnp for Android.

Is that a recent regression ? (unfortunately, I don't remember what version of bubbleupnp was installed on the previous NAS when it worked)
And how come BubbleUpnp for android is not affected ? Is it not using the same URL ?

Regards,

Arnaud

[Bubblesoft]

Hi,

It has been a long time that I have not tested this functionality but IIRC you need to connect in foobar2000 on iOS to:

http://user:password@<myIp>:58050/DeviceDescription.xml

Where user/password are the credentials that was set in the BubbleUPnP Server web config in the 'Network and Security' page.

And yes, Android BubbleUPnP connects to BubbleUPnP Server differently.

[Bubblesoft]

This issue could be caused if foobar2000 on iOS recently changed its User-Agent.

I will check with the Android version of foobar2000 but it will have to wait a few days.