For my Android devices, I access the Twonky media server using BubbleUPnP, which works nicely, and is cheap for multiple licences.
Now, in a recent upgrade, they added Cloud access for commercial clouds, but I don’t use commercial clouds, and the ‘Cloud’ option cluttered up the Library pane. So I asked the developers to add a switch to remove it, jokingly saying MyCloud access would be nice. They replied very promptly to point me to an existing switch…
But, whilst nosing through the settings again, I remembered I have BubbleUPnP Server installed on my little Android Media Box, which provides a proxy server for Twonky. And part of that proxy service is https cloud access to the Twonky media server.
After a little playing (there’s a disconnect between the terms used in the Server and Client apps), I think I now have remote access enabled for my cloud-accessible MyCloud; whilst I’m still local to my network, the client app is reporting successful access to the externally-visible IP address, and the remote proxy server appears as an available media server.
The steps:
Create a window in my firewall to support this service.
Configure the Server (select which media servers to make available remotely, enable remote access, create access user and password, note public IP address from Status page)
Check that the Server can access the internet (i.e. the firewall is set up correctly)
Configure the client using the ‘Setup Network Wizard’ (enter public IP address and port, user and password, and name the proxy server, select allowable connection bearers)
Test and confirm the proxy access settings.
The security of this…? hmmm. I guess the firewall holes are no different from what is needed for MyCloud remote apps.