Page 1 of 1

Remote access

PostPosted: Sat Jun 08, 2024 3:07 pm
by Pratt
With the release of 2.4 I am looking at the Pro features during the 14-day grace period and attempting to figure out remote access, without success.

I'm using Windows 11. My music files stream perfectly on my home network. The network setting for my Serviio media server is a bound IP address: 10.0.x.xxx.

In Serviio's console under Users I added a username and password. Under Remote I checked Automatically configure your router to allow incoming internet connections. I entered my internet IP address, 99.230.x.xxx, under External address. External port shows 23424. External secure port shows 23524. When I click Connectivity Status it shows green checkmarks beside insecure connectivity and secure connectivity.

I downloaded ServiiGo to my phone. When I click Add server It finds my Media server and shows the correct IP address, 10.0.x.xxx. When I tap on the server all of the information looks correct. When I then tap the button Add server, it asks for the username and password which it accepts. But then it responds Failed to open a connection to the server.

What am I doing wrong?

Thank you.

Re: Remote access

PostPosted: Sat Jun 08, 2024 8:24 pm
by Pratt
Update: I added port forwarding to Port 23424 so now I connect but ServiiGo shows no content and Serviio Media Browser also shows empty folders. So still something wrong. Suggestions appreciated.

Re: Remote access

PostPosted: Sun Jun 09, 2024 2:01 am
by atc98092
Starting with Serviio 2.0, remote access users must have a user name in Serviio AND that user must be given access to each shared library folder. Open up your shared library in the console and click Edit on one. You will see a section labeled "Users with access" and each user name will be listed there. You must put a checkmark on each library location you wish to share with that user name, then save the changes.

Re: Remote access

PostPosted: Sun Jun 09, 2024 1:15 pm
by Pratt
Thank you very much! That was the missing piece!

Re: Remote access

PostPosted: Tue Jun 11, 2024 2:53 pm
by Pratt
Dan,

Thank you for your help. Remote access using MediaBrowser and ServiiGo works perfectly. However, while streaming music using ServiiGo, three security risks to the device housing Serviio and the music files on my home network were detected and blocked. So, how safe is remote access using Serviio?

I note that port forwarding 23424 works on both MediaBrowser and ServiiGo but port forwarding 23524, the secure port, works only on MediaBrowser. Is it safer to use MediaBrowser on 23524 than ServiiGo on 23424?

Thanks.

Re: Remote access

PostPosted: Tue Jun 11, 2024 6:16 pm
by atc98092
I can't help with ServiiGo. It's not provided or supported by the Serviio developer, and I don't have any Android devices that ServiiGo supports so I've never used it. You would have to ask Will (the ServiiGo developer) about that.

I have never bothered with using the secure port for MediaBrowser. There's no simple way to add a security certificate to the HTTP server that Serviio uses, and I don't want the expense of purchasing a commercial certificate and the hassle of configuring and using a self-issued certificate. If someone hacks my Serviio PC, they won't find much. :)

Re: Remote access

PostPosted: Sun Jun 23, 2024 8:10 pm
by nobody511
Pratt wrote:Dan,

Thank you for your help. Remote access using MediaBrowser and ServiiGo works perfectly. However, while streaming music using ServiiGo, three security risks to the device housing Serviio and the music files on my home network were detected and blocked. So, how safe is remote access using Serviio?

I note that port forwarding 23424 works on both MediaBrowser and ServiiGo but port forwarding 23524, the secure port, works only on MediaBrowser. Is it safer to use MediaBrowser on 23524 than ServiiGo on 23424?

Thanks.


ServiiGo also works with the built in SSL Webserver of Serviio. However, sometimes with my android it refuses to connect or wont connect because of problems verifying the certificate, even when I checked "allow self signed certificates (not recommended)". Well, a self signed certificate is not less secure then any other certificate if you trust it. Unless you think someone hijack your browser/client when you connect to the external IP of your Box, it makes no difference.
The problem I experience with the SSL connection might be not appear with your Android. Just try it out.
Check the boxes: SSL support plus the allow self signed.... Enter the Servers name/IP as: server.ip.addr.comain:23524
enter username and password. Save.
You then you should connect with SSL - encrypted.