search

dhleong / playactor

play around with your playstation devices
147 stars 12 forks source link

Registration Error after Enter the Pin #41

Closed tommyMX closed 2 years ago

tommyMX commented 2 years ago

Error: Registration error: 403: Forbidden: Other Error at Object. (/usr/local/lib/node_modules/playactor/dist/remoteplay/protocol.js:88:19) at Generator.next () at fulfilled (/usr/local/lib/node_modules/playactor/dist/remoteplay/protocol.js:5:58) at processTicksAndRejections (internal/process/task_queues.js:97:5)

dhleong commented 2 years ago

That's https://github.com/dhleong/playactor/issues/21

tommyMX commented 2 years ago

Closing every ticket is no help

there is no solution in 21

dhleong commented 2 years ago

I'm sorry there's no solution at the moment, but having two different tickets tracking the same issue is not the answer.

tommyMX commented 2 years ago

Yes I understand…

But on some systems I found that’s working in some forums but seems not everywhere..

Hope it will be fixed soon…

thx

Am 12.01.2022 um 18:02 schrieb Daniel Leong @.***>:

I'm sorry there's no solution at the moment, but having two different tickets tracking the same issue is not the answer.

— Reply to this email directly, view it on GitHub https://github.com/dhleong/playactor/issues/41#issuecomment-1011260805, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIUIJXUQKVQPTRLB4XX76FDUVWX2NANCNFSM5LZHELMQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.

dhleong commented 2 years ago

Yep, for example I cannot reproduce the issue—I’ve (almost) never had any problems, which makes it very difficult for me to fix. The other ticket is tracking this issue so if you or anybody else can find a consistent way to reproduce it (that I can then reproduce myself) that might help me to solve it.

I’m aware of the issue so just saying “I also experience this” without adding any new information (IE: “I can always get this error when….”) is just distracting and unhelpful. It also will send an email to other people that are following the ticket, so it’s noise for them, too.

Not trying to discourage contribution—I always appreciate the help—just trying to guide you towards more helpful ways to contribute.

Also FWIW I’m out of town and on medical leave for some time, so it’ll be difficult for me to work on this even if someone can provide a consistent repro….

On Jan 12, 2022 at 12:04:24 PM, tommyMX @.***> wrote:

Yes I understand…

But on some systems I found that’s working in some forums but seems not everywhere..

Hope it will be fixed soon…

thx

Am 12.01.2022 um 18:02 schrieb Daniel Leong @.***>:

I'm sorry there's no solution at the moment, but having two different tickets tracking the same issue is not the answer.

— Reply to this email directly, view it on GitHub < https://github.com/dhleong/playactor/issues/41#issuecomment-1011260805>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AIUIJXUQKVQPTRLB4XX76FDUVWX2NANCNFSM5LZHELMQ . Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android < https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

You are receiving this because you authored the thread.

— Reply to this email directly, view it on GitHub https://github.com/dhleong/playactor/issues/41#issuecomment-1011262675, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGHIFWVC2UGK52PIBRRJATUVWYBRANCNFSM5LZHELMQ . You are receiving this because you modified the open/close state.Message ID: @.***>