-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'Other Error' during registration #21
Comments
Thanks for the report! This may be tricky to debug since I can't reproduce but I'll do my best. Out of curiosity, do you have a passcode set for logging into your account on the device? By the way, I went through and redacted a few more things in you message and deleted the comment revision history for you. Anything that says "decrypted" should definitely be redacted. We're still sort of in "beta" right now so full debug logs are very noisy—please be careful when posting them! I'll try to make sure those are automatically redacted moving forward, but it was helpful for local testing in development since there's some specific byte-level stuff going on under the hood. |
Thanks for the cleanup. No passcode needed to login on my console. |
I occasionally get the 403 error as well, but I haven't had time to look into it further to try to notice a pattern. |
I decided to take another crack at this, since all I have been able to do with my broken credentials is wake. I ran Eventually, however, I was able to get a successful registration, which resulted in a working set of credentials. I can't really explain why this particular attempt worked, as I don't believe I did anything different. However, if anyone else is also having this problem, persistence seems to be the key! |
I have the same issue. |
I also get this error, but only intermittently. I have this sitting on a Raspberry Pi behind a Homebridge switch, and sometimes it will fail, and when I check the logs it's this "Registration error" (even though it's already registered?). But then strangely it will sort itself out as sure enough the next day it will start working for both waking and sleeping without me having to change anything. I might put on debug mode sometime and see if I can get any more details. |
Hi, is there any progress from April? Its clear that more people have this kind of problem. Thx. |
So actually a bug and it isn’t working ? |
i got the same issue, but found a solution. The auth link to login ps5 must be the same account as your ps5 account. |
This is not actually a bug. You have to open it first PS5 Remote Play |
I also have this problem after entering the pin code: |
Leaving this here in case it helps anyone else. I encountered this issue today. In the end I made it work by doing the following. 1: Delete the credentials.json file @dhleong not sure if it's possible (haven't looked through the source code) but is there possibly some sort of altered code-path when using the --debug flag? |
No, that flag simply enables the debug output. If you do the same but omit |
When attempting to register with my PS5, I always receive the following error after entering the Remote Play code:
The registration does however seem to be (at least partially) successful, as playactor is able to create and use its credential file afterwards.
I'm running playactor 0.2.1 using node v14.16 on Debian.
Full debug of
playactor login --debug
, used for registration, attached:The text was updated successfully, but these errors were encountered: