Got status 503 from Moonlight init

[rafaelcara]

Hi, thanks for this amazing project.

"Got status 503 from Moonlight init" error happens when starting connection to host (Using OpenStream)

*I already tried without Remote Play and the same error happens

[TheElixZammuto]

Hi, does restarting both openstreamhost.exe and openstreamapp.exe resolve the issue?

Also OpenStream is not maintened anymore, you should use Sunshine or Maxximizer (which is a packaged version of Sunshine - https://community.maximumsettings.com/d/211-beta-launch-of-maxximizer-based-on-sunshine)

[perroboc]

I'm running the app from the store link in a windows 10 PC, connecting to a host with Windows 10 + nvidia 1660 super, using the latest version from sunshine (0.13.0). I get the same error:

Note that I'm testing both iOS and webOS clients and they connect successfully:

[2022:03:14:14:33:29]: Info: /CN=NVIDIA GameStream Client -- verfied
[2022:03:14:14:33:29]: Info: CLIENT CONNECTED
[2022:03:14:14:33:29]: Info:
Device Description : NVIDIA GeForce GTX 1660 SUPER
Device Vendor ID   : 0x000010DE
Device Device ID   : 0x000021C4
Device Video Mem   : 5992 MiB
Device Sys Mem     : 0 MiB
Share Sys Mem      : 8147 MiB
Feature Level      : 0x0000B100
Capture size       : 1920x1080
Offset             : 0x0
Virtual Desktop    : 1920x1080
[2022:03:14:14:33:29]: Info: Color coding [Rec. 601]
[2022:03:14:14:33:29]: Info: Color range: [MPEG]

But I don't get the connection strings from the UWP client, I only get the following:

[2022:03:14:14:35:19]: Info: /CN=NVIDIA GameStream Client -- verfied
[2022:03:14:14:35:19]: Info: /CN=NVIDIA GameStream Client -- verfied
[2022:03:14:14:35:21]: Info: /CN=NVIDIA GameStream Client -- verfied
[2022:03:14:14:35:21]: Info: /CN=NVIDIA GameStream Client -- verfied
[2022:03:14:14:35:22]: Info: /CN=NVIDIA GameStream Client -- verfied

EDIT: I compared the Request with the error between my Windows client (UWP) with an xbox controller attached, and my iOS client.

Here's the Request that works (iOS):

o=android 0 14 IN IPv4 192.168.1.36
s=NVIDIA Streaming Client
a=x-nv-video[0].clientViewportWd:1920
a=x-nv-video[0].clientViewportHt:1080
a=x-nv-video[0].maxFPS:60
a=x-nv-video[0].packetSize:1392
a=x-nv-video[0].rateControlMode:4
a=x-nv-video[0].timeoutLengthMs:7000
a=x-nv-video[0].framesWithInvalidRefThreshold:0
a=x-nv-video[0].initialBitrateKbps:20000
a=x-nv-video[0].initialPeakBitrateKbps:20000
a=x-nv-vqos[0].bw.minimumBitrateKbps:20000
a=x-nv-vqos[0].bw.maximumBitrateKbps:20000
a=x-nv-vqos[0].fec.enable:1
a=x-nv-vqos[0].videoQualityScoreUpdateTime:5000
a=x-nv-vqos[0].qosTrafficType:5
a=x-nv-aqos.qosTrafficType:4
a=x-nv-general.featureFlags:167
a=x-nv-general.useReliableUdp:13
a=x-nv-vqos[0].fec.minRequiredFecPackets:2
a=x-nv-vqos[0].drc.enable:0
a=x-nv-general.enableRecoveryMode:0
a=x-nv-video[0].videoEncoderSlicesPerFrame:1
a=x-nv-clientSupportHevc:0
a=x-nv-vqos[0].bitStreamFormat:0
a=x-nv-video[0].dynamicRangeMode:0
a=x-nv-video[0].maxNumReferenceFrames:0
a=x-nv-video[0].clientRefreshRateX100:0
a=x-nv-audio.surround.numChannels:2
a=x-nv-audio.surround.channelMask:3
a=x-nv-audio.surround.enable:0
a=x-nv-audio.surround.AudioQuality:0
a=x-nv-aqos.packetDuration:5
a=x-nv-video[0].encoderCscMode:0
t=0 0
m=video 47998

While here's the request that gets a 503 error:

o=android 0 14 IN IPv4 192.168.1.36
s=NVIDIA Streaming Client
a=x-nv-video[0].clientViewportWd:1920
a=x-nv-video[0].clientViewportHt:1080
a=x-nv-video[0].maxFPS:60
a=x-nv-video[0].packetSize:1024
a=x-nv-video[0].rateControlMode:4
a=x-nv-video[0].timeoutLengthMs:7000
a=x-nv-video[0].framesWithInvalidRefThreshold:0
a=x-nv-video[0].initialBitrateKbps:20000
a=x-nv-video[0].initialPeakBitrateKbps:20000
a=x-nv-vqos[0].bw.minimumBitrateKbps:20000
a=x-nv-vqos[0].bw.maximumBitrateKbps:20000
a=x-nv-vqos[0].fec.enable:1
a=x-nv-vqos[0].videoQualityScoreUpdateTime:5000
a=x-nv-vqos[0].qosTrafficType:5
a=x-nv-aqos.qosTrafficType:4
a=x-nv-general.featureFlags:135
a=x-nv-general.useReliableUdp:13
a=x-nv-vqos[0].fec.minRequiredFecPackets:2
a=x-nv-vqos[0].drc.enable:0
a=x-nv-general.enableRecoveryMode:0
a=x-nv-video[0].videoEncoderSlicesPerFrame:1
a=x-nv-clientSupportHevc:0
a=x-nv-vqos[0].bitStreamFormat:0
a=x-nv-video[0].dynamicRangeMode:0
a=x-nv-video[0].maxNumReferenceFrames:0
a=x-nv-video[0].clientRefreshRateX100:6000
a=x-nv-audio.surround.numChannels:2
a=x-nv-audio.surround.channelMask:3
a=x-nv-audio.surround.enable:0
a=x-nv-audio.surround.AudioQuality:0
a=x-nv-aqos.packetDuration:5
a=x-nv-video[0].encoderCscMode:0
t=0 0
m=video 47998

No differences save for the following: iOS:

a=x-nv-video[0].packetSize:1392
a=x-nv-general.featureFlags:167
a=x-nv-video[0].clientRefreshRateX100:0

Windows UWP:

a=x-nv-video[0].packetSize:1024
a=x-nv-general.featureFlags:135
a=x-nv-video[0].clientRefreshRateX100:6000

[nixRidge]

I'm running into to this issue with an Arch Linux host with Sunshine, it works when streaming to Moonlight on my Arch Linux laptop and Android phone, but I get this error on Xbox Series X, downloaded from the Store (can't enable devmode to install the latest version I'm afraid).

The host uses an RX 6700 XT and VA-API for encoding. The resolution is 1080p on host, and 4k on the Xbox/TV. Have tried forcing 1080p on the Xbox.

I did manage to make it work before (about two months or a month ago?), but after a GPU swap and reinstall of Arch Linux on the host between then and now, I get this error. The previous GPU was a GeForce GTX 1060 6GB and I used NVENC for encoding then.

I'm not sure what info from my setup could help, or what this error code even means, so please let me know if there's anything I can supply to help.

I've tried restarting Sunshine, my host and the Xbox (cold reboot), checked the config and reset it to defaults.

Details at a glance because I'm bad at writing concise posts:

Host OS: Arch Linux, Linux-Zen kernel GPU: RX 6700 XT Encoder: VA-API Resolution: 1920x1080 Network: Ethernet

Xbox Moonlight: Store version Resolution: 3840x2160 Network: Ethernet

[TheElixZammuto]

In general, a 503 error in Sunshine indicates that the Streaming Sessions used by sunshine are all used. In general force-closing the app in the Web UI (Troubleshooting -> Force Close) can help with this