Serviio

Posted: **Sat Dec 22, 2018 4:01 pm**

I've installed Serviio 1.9.2 on Synology DS416 (the console says that a new version is available, but it doesn't seem that it is for Synology). Evaluation license since I really want to see it working with Alexa. Opened console, enabled remote access and tested it - two green ticks. MediaBrowser will play music to my PC.
When I try to link the server to the Alexa skill, I see "The provided credentials are not valid. Try again.". I _have_ tried again, but no luck.
I would have thought that the remote access test was definitive, but it appears not.
How can I diagnose what's going on? Thanks!

Posted: **Fri Dec 28, 2018 10:51 pm**

philAtkin wrote:I've installed Serviio 1.9.2 on Synology DS416 (the console says that a new version is available, but it doesn't seem that it is for Synology). Evaluation license since I really want to see it working with Alexa. Opened console, enabled remote access and tested it - two green ticks. MediaBrowser will play music to my PC.
When I try to link the server to the Alexa skill, I see "The provided credentials are not valid. Try again.". I _have_ tried again, but no luck.
I would have thought that the remote access test was definitive, but it appears not.
How can I diagnose what's going on? Thanks!

I'm having the same problem...
Both insecure & secure ports are greenlit, I've got outside access to my server...
I can't link the server in the alexa app & I also get "The provided credentials are not valid. Try again."....
I am running serviio in a docker though....

Does anybody have a solution to this issue?

Thanks

Posted: **Sun Dec 30, 2018 4:54 pm**

Alexa is only available when you actually purchase the Pro, not in the evaluation period.

Posted: **Mon Dec 31, 2018 5:28 pm**

I guess that's a perfectly understandable (though regrettable) decision on your part. Maybe it could be stated on the website, where the evaluation process and/or the Alexa skill are described.

Personally, I've had a lot of annoying experiences with Alexa apps that "don't quite work", and I wanted to make sure that this one did before committing the time to setting up Serviio again.

Posted: **Tue Jan 01, 2019 2:00 pm**

Fair enough. I have to limit the cloud resources, but you could make the purchase and if not happy I'll refund you.

Posted: **Sat Jan 05, 2019 10:27 pm**

Hi All

for the life of me i cant login to serviio when registering my Alexa skill. I have the pro version 1.10 running on linux mint. it appears that either my serviio ID or password is incorrect.
external port 23424, external secure port 23524. I can access my console fine via my DNS name when outside of my home network, so that cant be the issue.

I can provide my serviio id if required

Can you please help

Posted: **Thu Jan 10, 2019 1:36 pm**

DM me your serviio id and I'll check

Posted: **Thu Jan 17, 2019 9:28 pm**

Hi Petr

Here your are:

tjHtx1BYb3

Thanks for your help on this

Mark

Posted: **Fri Jan 18, 2019 8:26 pm**

Are you a Serviio Pro user?

Posted: **Fri Jan 18, 2019 9:41 pm**

Hi zip

yes i am: Serviio PRO v 1.10
and fully licensed..

cheers

mark

Posted: **Mon Jan 21, 2019 12:36 pm**

It works fine on my DS1515 however you will need a valid certificate from a trusted source for it to work, this is a requirement of AMAZON not Serviio.

Posted: **Mon Jan 21, 2019 10:22 pm**

a7mag3ddon wrote:It works fine on my DS1515 however you will need a valid certificate from a trusted source for it to work, this is a requirement of AMAZON not Serviio.

it's all sorted by Serviio backend, no need for it on your end

Posted: **Mon Jan 21, 2019 10:22 pm**

markahearn wrote:Hi zip

yes i am: Serviio PRO v 1.10
and fully licensed..

cheers

mark

Can you PM me your log pls?

Posted: **Wed May 22, 2019 11:02 pm**

Same here....cannot link alexa skill - "The provided credentials are not valid. Try again."

I upgraded to version 2 PRO today believing this would fix my issues with the skill and trying to play through alexa. It did fix my connectivity issue! Now when I "check conectivity" both insecure and secure get check marks! yay....at least I made a little progress.

What do I need to do to link the account?

I did create a user and password in 2.0 and those are the user and pw I'm trying to link the acct with.

Posted: **Wed May 22, 2019 11:08 pm**

Made a little progress....the serviio ID had a zero in it...the zero looks like a lower case o. Might consider changing the font for the ID value

Anyway, now the message reads "There was a problem connecting to your serviio server. Please check the Remote settings in your Serviio Console".

Will check the router and see that it has the port forwarded.

Posted: **Wed May 22, 2019 11:14 pm**

after adding the ports to the router for forwarding the secure connection now gets an red X

please help? I feel like I've gone full circle with this!

Posted: **Thu May 23, 2019 3:41 pm**

you can check if the ports are opened using a tool like this: https://www.yougetsignal.com/tools/open-ports/

ports 23424 (unsecure) and 23524 (secure)

Posted: **Sat May 25, 2019 10:05 am**

I had used https://www.yougetsignal.com/tools/open-ports/ site recently to validate the ports and I just did again and got the same results.

23424 reports open
23524 reports as "invalid"

I checked my router's configuration and I DO have both ports defined in port forwarding. Also, I looked in the router's log and it shows both ports as forwarded too, so I have to believe it's something on the server. Also, on the server there is no firewall running (it's a raspberry pi 2-B), and I check the open ports on the server and it shows;

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 444/sshd
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 822/smbd
tcp 0 0 0.0.0.0:8895 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:23423 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:23424 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:23523 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:23524 0.0.0.0:* LISTEN 29841/java
tcp 0 0 127.0.1.1:44331 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 822/smbd
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 414/vncserver-x11-c
tcp6 0 0 :::22 :::* LISTEN 444/sshd
tcp6 0 0 :::445 :::* LISTEN 822/smbd
tcp6 0 0 :::139 :::* LISTEN 822/smbd
tcp6 0 0 :::5900 :::* LISTEN 414/vncserver-x11-c

So it seems like all the pieces are in place but something is still missing

Posted: **Sat May 25, 2019 7:40 pm**

MarcB wrote:I had used https://www.yougetsignal.com/tools/open-ports/ site recently to validate the ports and I just did again and got the same results.

23424 reports open
23524 reports as "invalid"

I checked my router's configuration and I DO have both ports defined in port forwarding. Also, I looked in the router's log and it shows both ports as forwarded too, so I have to believe it's something on the server. Also, on the server there is no firewall running (it's a raspberry pi 2-B), and I check the open ports on the server and it shows;

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 444/sshd
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 822/smbd
tcp 0 0 0.0.0.0:8895 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:23423 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:23424 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:23523 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:23524 0.0.0.0:* LISTEN 29841/java
tcp 0 0 127.0.1.1:44331 0.0.0.0:* LISTEN 29841/java
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 822/smbd
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 414/vncserver-x11-c
tcp6 0 0 :::22 :::* LISTEN 444/sshd
tcp6 0 0 :::445 :::* LISTEN 822/smbd
tcp6 0 0 :::139 :::* LISTEN 822/smbd
tcp6 0 0 :::5900 :::* LISTEN 414/vncserver-x11-c

So it seems like all the pieces are in place but something is still missing

If that site is reporting your port as closed, it's nothing to do with Serviio. The port forwarding is all in your firewall. I tested my firewall using the same site, and it too reports port 23524 as invalid. The difference is that I have that port closed, so that's the expected result. I recognize your firewall log shows it open, but for some reason it's not actually working. However, I tried adding port 23524 to my firewall and testing again, and it still reported invalid port. So there's something wrong with that particular port scanner. I found another site (https://www.ipfingerprints.com/portscan.php), and it correctly reports port 23524 as open. Please check your port again with this site and let us know if it shows open with that one.

Posted: **Sun May 26, 2019 1:11 pm**

Thank you DLNA Master! The site you suggested (https://www.ipfingerprints.com/portscan.php) DID report the port as "open".

So I guess now the question is why when I ask the serviio skill to do anything Alexa tells me it can't do that.

For instance, "Alexa, play The Beatles on this echo" will return the message "I can't find The Beatles". And for the record I've tried several artists, albums, and songs all with the same results. And YES...I do have these artists, etc on my server and can play them from other sources and see them in the MediaBrowser.

Am I missing something?

Serviio

Can't link Alexa skill

Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill

Re: Can't link Alexa skill