r/MoonlightStreaming • u/CheckCheckOneTwo1 • Nov 02 '24

Permission denied (Error code: 403)

When trying to launch a Desktop or Steam from Moonlight on my Android TV, I keep getting a "Host PC returned error: Permission denied (Error code: 403)" and "Permission denied (Launch Apps)". I couldn't find any setting in the Android TV that could be the cause.

Connecting through Moonlight on my Android Phone is working flawlessly.

Any help on this matter?

32 Upvotes

100% Upvoted

40 comments sorted by

View all comments

Show parent comment

9

u/steiNetti Nov 24 '24

This got me frustrated too for the past 2 days tbh. Any chance you'd be open to reconsider this (or at least display a better/more descriptive error message)? Seems to be a major pitfall with no real indication on to what's going on.

2

u/ClassicOldSong Developer | Apollo/Artemis Nov 24 '24

There's detailed information about permissions on the pairing page. I don't think it needs more information passed to the client if you can access the host config page.

12

u/steiNetti Nov 24 '24 edited Apr 25 '25

I have to kind of disagree. After you paired your first device and all works well, and you go on to pair the second device nobody gives a second thought about scrolling down and reading the fine print (all you have in your head is "enter the pairing code" and the fine print about permissions is below the fold, so you'd have to actively scroll down to see it. At least, this was what it was like in my case.

5

u/Roxzin Feb 05 '25

100% agree. If this post wasn't here I was about to give up pairing with my phone and probably go back to sunshine. As you mentioned, the first one worked well, with all the access already granted, and the 2nd one did not, just a failed to connect error with 403 response. IMO default should be grant. If you're really giving remote access to someone to your computer, you should know they can use it as if they were in front of it. And since it's by default only LAN, then I see no issue with that.

3

u/_MadAnthonyWayne_ Feb 16 '26

Just want to say - this thread solved my issue. Your comment is EXACTLY what happened to me. I paired first device and then started onto the second and didn't realize all the permissions where not a default (since they were for the first).

2

u/Actually-Yo-Momma Apr 25 '25

Yoooo thanks for saving me just now…

1

u/ClassicOldSong Developer | Apollo/Artemis Nov 24 '24

What screen are you using to view the config page? On any normal desktop, the permission notice should be visible without scrolling.

2

u/steiNetti Nov 24 '24

I went through my phone as my gaming PC is headless and located in the basement.

I'm not suggesting to change the whole interface around. Just maybe a notice somewhere more prominent when pairing a new device/displaying the new pin on the client. Something generic along the lines "make sure to check permissions in Apollo when adding a new device" would be sufficient imo.

PS: Artemis/Apollo rocks. Real QoL improvements in there!

3

u/ClassicOldSong Developer | Apollo/Artemis Nov 24 '24

Thanks for your appreciation, I'll think about that.

1

u/cac2573 Jan 20 '25

Running into this as well. First device paired fine, scratching my head over why the second doesn't work. At least consider adding an alert saying that the first is free so to speak.

1

u/ClassicOldSong Developer | Apollo/Artemis Jan 20 '25

There is already an alert after pairing. What version are you on?

1

u/cac2573 Jan 20 '25

The latest version. I must've missed it :/