Playon auth issues?

I just joined Playon on my iPad using signon with Apple to create my account. I’m trying to add Playon to my Channels DVR, when I try to authorize entering my apple creds Playon returns an error. I am certain that I am using the correct Apple creds.

I had this issue or at least a similar one as well. I as able to link my PlayOn account that I created using my appleid into Channels using the Chrome browser. If I used Safari I couldn't get past the login screen.

Thank you - Tried Chrome and Edge browsers. Both react the same. Server error: Bad Request The server will not or cannot process the request

1 Like

What is the URL in the url bar when this error is seen?

playonrecorder.com/login/apple/callback

I am having this problem as well. I submitted diagnostics, 58f3828d-b208-41e1-b839-ed8854a7a9df

Sounds like an issue on the PlayOn side, esp if its only happening with apple auth. Did you try reaching out to their support?

I have created a ticket with them as well. Waiting to hear back.

I created a ticket as well. Waiting for response

I am having this same issue. I can log directly into playon.tv with apple credentials no problem with the same browser, but I get the error when trying to link to Channels.

Same issue when trying to log in to PlayOn. Please let us know what their support team says. Thanks!

Same issue here getting " Server Error: 400 (Bad Request)"

We've spoken with PlayOn. They're investigating.

Hi there -- My name is Skip Sullivan and I'm the support lead for PlayOn. I wanted to let you know we were able to reproduce this morning and we're working on it. Thank you to those who reported it.

3 Likes

I just tried again and I was able to add PlayOn as a source I am waiting to see if it automatically syncs. Manual sync seems to work.

1 Like

Automatic Syncs appear to be working with PlayOn integration.

got an email that the authorization issue has been solve by Playon. I tried again and I am now authorized using Apple. Yeah!!!
\

2 Likes

Hi all -- thanks for bearing with us while we investigated and fixed this issue. It should be working properly now.

5 Likes