Skip to content
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

Error 503 after Fedora update #1765

Closed
3 tasks done
l3obak opened this issue Oct 18, 2023 · 9 comments
Closed
3 tasks done

Error 503 after Fedora update #1765

l3obak opened this issue Oct 18, 2023 · 9 comments
Labels

Comments

@l3obak
Copy link

l3obak commented Oct 18, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Is your issue described in the documentation?

  • I have read the documentation

Is your issue present in the nightly release?

  • This issue is present in the nightly release

Describe the Bug

Error 503 appears when i try to connect with moonlight, before the last Fedora update it was working perfectly.

Expected Behavior

No response

Additional Context

No response

Host Operating System

Linux

Operating System Version

Fedora 38 Linux 6.5.7-200.fc38.x86_64

Architecture

64 bit

Sunshine commit or version

0.21.0

Package

Linux - rpm

GPU Type

Nvidia

GPU Model

GeForce RTX 3070

GPU Driver/Mesa Version

Nvidia driver 535.113.01 NVML 12.535.113.01

Capture Method (Linux Only)

No response

Config

origin_pin_allowed = lan
output_name = 2
resolutions = [
    352x240,
    480x360,
    858x480,
    1280x720,
    1920x1080,
    2560x1080,
    3440x1440,
    1920x1200,
    3840x2160,
    3840x1600,
    2560x1600
]

Apps

No response

Relevant log output

[2023:10:18:19:44:04]: Info: Sunshine version: v0.21.0
[2023:10:18:19:44:04]: Info: Found display [wayland-0]
[2023:10:18:19:44:04]: Info: Found interface: wl_output(5) version 4
[2023:10:18:19:44:04]: Info: Found interface: wl_output(6) version 4
[2023:10:18:19:44:04]: Info: Found interface: zxdg_output_manager_v1(7) version 3
[2023:10:18:19:44:04]: Warning: Missing Wayland wire for wlr-export-dmabuf
[2023:10:18:19:44:04]: Info: Found display [wayland-0]
[2023:10:18:19:44:04]: Info: Found display [wayland-0]
[2023:10:18:19:44:04]: Info: Found interface: wl_output(5) version 4
[2023:10:18:19:44:04]: Info: Found interface: wl_output(6) version 4
[2023:10:18:19:44:04]: Info: Found interface: zxdg_output_manager_v1(7) version 3
[2023:10:18:19:44:04]: Info: Offset: 1366x0
[2023:10:18:19:44:04]: Info: Resolution: 2560x1440
[2023:10:18:19:44:04]: Info: Name: DP-3
[2023:10:18:19:44:04]: Info: Found monitor: Philips Consumer Electronics Company 27"
[2023:10:18:19:44:04]: Info: Offset: 0x0
[2023:10:18:19:44:04]: Info: Resolution: 1366x768
[2023:10:18:19:44:04]: Info: Name: HDMI-1
[2023:10:18:19:44:04]: Info: Found monitor: HKC OVERSEAS LIMITED
[2023:10:18:19:44:04]: Info: DP-3: Philips Consumer Electronics Company 27"
[2023:10:18:19:44:04]: Info: HDMI-1: HKC OVERSEAS LIMITED
[2023:10:18:19:44:04]: Info: // Testing for available encoders, this may generate errors. You can safely ignore those errors. //
[2023:10:18:19:44:04]: Info: Trying encoder [nvenc]
[2023:10:18:19:44:04]: Info: Screencasting with KMS
[2023:10:18:19:44:04]: Error: Couldn't create GBM device: [00003000]
[2023:10:18:19:44:04]: Info: System tray created
[2023:10:18:19:44:04]: Info: Screencasting with KMS
[2023:10:18:19:44:04]: Error: Couldn't create GBM device: [00003000]
[2023:10:18:19:44:05]: Info: Encoder [nvenc] failed
[2023:10:18:19:44:05]: Info: Trying encoder [vaapi]
[2023:10:18:19:44:05]: Info: Screencasting with KMS
[2023:10:18:19:44:05]: Error: Couldn't open a va display from DRM with device:  �
@SmurgBurglar
Copy link

I'm also getting error 503 this is on both Android and Linux Moonlight clients and from Linux and Windows Sunshine servers.
Here's the full error.
GeForce Experience returned error: Failed to initialize video capture/encoding. is a display connected and turned on? (Error 503)

@thatsysadmin
Copy link
Contributor

thatsysadmin commented Nov 9, 2023

How many displays do you have connected? Seems like you only have 2. Your config file seems to be telling Sunshine to target display 3. Your machine doesn't seem to have a tertiary display connected unless it's not being detected.

In your config file, try changing output_name to 0 or 1. See if you get an output from either one. For some context, the index starts at 0, so 0 = Display 1, 1 = Display 2, and so on and so forth.

@l3obak
Copy link
Author

l3obak commented Nov 11, 2023 via email

@thatsysadmin
Copy link
Contributor

thatsysadmin commented Nov 11, 2023

@l3obak

With that configuration change I specified, What does the log look like now? Also: what does nvidia-smi output by any chance? I also kind of want to say take out your resolutions block and let Sunshine figure it all out.

Another thing, (this might apply to @SmurgBurglar) are you trying to connect while the display is off but the machine is still rolling? Sunshine can't/won't capture displays if the displays are off. While it's dirty, running loginctl unlock-sessions via SSH and punching in your password usually wakes displays.

@l3obak
Copy link
Author

l3obak commented Nov 29, 2023

This is the log:
[2023:11:29:17:55:35]: Info: Sunshine version: v0.21.0
[2023:11:29:17:55:35]: Info: Found display [wayland-0]
[2023:11:29:17:55:35]: Info: Found interface: wl_output(5) version 4
[2023:11:29:17:55:35]: Info: Found interface: wl_output(6) version 4
[2023:11:29:17:55:35]: Info: Found interface: zxdg_output_manager_v1(7) version 3
[2023:11:29:17:55:35]: Warning: Missing Wayland wire for wlr-export-dmabuf
[2023:11:29:17:55:35]: Info: Found display [wayland-0]
[2023:11:29:17:55:35]: Info: Found display [wayland-0]
[2023:11:29:17:55:35]: Info: Found interface: wl_output(5) version 4
[2023:11:29:17:55:35]: Info: Found interface: wl_output(6) version 4
[2023:11:29:17:55:35]: Info: Found interface: zxdg_output_manager_v1(7) version 3
[2023:11:29:17:55:35]: Info: Offset: 1366x0
[2023:11:29:17:55:35]: Info: Resolution: 2560x1440
[2023:11:29:17:55:35]: Info: Name: DP-3
[2023:11:29:17:55:35]: Info: Found monitor: Philips Consumer Electronics Company 27"
[2023:11:29:17:55:35]: Info: Offset: 0x0
[2023:11:29:17:55:35]: Info: Resolution: 1366x768
[2023:11:29:17:55:35]: Info: Name: HDMI-1
[2023:11:29:17:55:35]: Info: Found monitor: HKC OVERSEAS LIMITED
[2023:11:29:17:55:35]: Info: DP-3: Philips Consumer Electronics Company 27"
[2023:11:29:17:55:35]: Info: HDMI-1: HKC OVERSEAS LIMITED
[2023:11:29:17:55:35]: Info: // Testing for available encoders, this may generate errors. You can safely ignore those errors. //
[2023:11:29:17:55:35]: Info: Trying encoder [nvenc]
[2023:11:29:17:55:35]: Info: Screencasting with KMS
[2023:11:29:17:55:35]: Info: Found monitor for DRM screencasting
[2023:11:29:17:55:35]: Info: Screencasting with KMS
[2023:11:29:17:55:35]: Info: Found monitor for DRM screencasting
[2023:11:29:17:55:35]: Info: SDR color coding [Rec. 601]
[2023:11:29:17:55:35]: Info: Color depth: 8-bit
[2023:11:29:17:55:35]: Info: Color range: [JPEG]
[2023:11:29:17:55:35]: Info: System tray created
[2023:11:29:17:55:35]: Info: Screencasting with KMS
[2023:11:29:17:55:35]: Info: Found monitor for DRM screencasting
[2023:11:29:17:55:35]: Info: SDR color coding [Rec. 601]
[2023:11:29:17:55:35]: Info: Color depth: 8-bit
[2023:11:29:17:55:35]: Info: Color range: [JPEG]
[2023:11:29:17:55:35]: Info: Screencasting with KMS
[2023:11:29:17:55:35]: Info: Found monitor for DRM screencasting
[2023:11:29:17:55:35]: Info: SDR color coding [Rec. 601]
[2023:11:29:17:55:35]: Info: Color depth: 8-bit
[2023:11:29:17:55:35]: Info: Color range: [JPEG]
[2023:11:29:17:55:35]: Warning: [av1_nvenc @ 0x2a68f40] Codec not supported
[2023:11:29:17:55:35]: Fatal: [av1_nvenc @ 0x2a68f40] Provided device doesn't support required NVENC features
[2023:11:29:17:55:35]: Error: Could not open codec [av1_nvenc]: Funzione non implementata
[2023:11:29:17:55:35]: Info: Screencasting with KMS
[2023:11:29:17:55:35]: Info: Found monitor for DRM screencasting
[2023:11:29:17:55:35]: Info: SDR color coding [Rec. 601]
[2023:11:29:17:55:35]: Info: Color depth: 8-bit
[2023:11:29:17:55:35]: Info: Color range: [JPEG]
[2023:11:29:17:55:35]: Warning: [av1_nvenc @ 0x376c780] Codec not supported
[2023:11:29:17:55:35]: Fatal: [av1_nvenc @ 0x376c780] Provided device doesn't support required NVENC features
[2023:11:29:17:55:35]: Error: Could not open codec [av1_nvenc]: Funzione non implementata
[2023:11:29:17:55:35]: Info: Screencasting with KMS
[2023:11:29:17:55:35]: Info: Found monitor for DRM screencasting
[2023:11:29:17:55:35]: Info: SDR color coding [Rec. 709]
[2023:11:29:17:55:35]: Info: Color depth: 10-bit
[2023:11:29:17:55:35]: Info: Color range: [JPEG]
[2023:11:29:17:55:35]: Info:
[2023:11:29:17:55:35]: Info: // Ignore any errors mentioned above, they are not relevant. //
[2023:11:29:17:55:35]: Info:
[2023:11:29:17:55:35]: Info: Found H.264 encoder: h264_nvenc [nvenc]
[2023:11:29:17:55:35]: Info: Found HEVC encoder: hevc_nvenc [nvenc]
[2023:11:29:17:55:35]: Info: Adding avahi service Sunshine
[2023:11:29:17:55:35]: Info: Configuration UI available at [https://localhost:47990]
[2023:11:29:17:55:36]: Info: Avahi service Sunshine successfully established.
[2023:11:29:17:55:44]: Error: A UPnP device has been found, but it wasn't recognized as an IGD

This is the nvidi-smi output:

'xorg-x11-drv-nvidia-470xx-cuda'
'xorg-x11-drv-nvidia-cuda'
'xorg-x11-drv-nvidia-340xx-cuda'
'xorg-x11-drv-nvidia-390xx-cuda'

How can i disable the resolution block?
All the test i runned was done with all the displays turned on.

@thatsysadmin
Copy link
Contributor

This is the nvidi-smi output:
'xorg-x11-drv-nvidia-470xx-cuda'
'xorg-x11-drv-nvidia-cuda'
'xorg-x11-drv-nvidia-340xx-cuda'
'xorg-x11-drv-nvidia-390xx-cuda'

This isn't nvidia-smi. It should output a fancy table.

How can i disable the resolution block?

origin_pin_allowed = lan
output_name = 2

Literally remove the configuration block; see above for example. You also might want to set the output to 0 and have just one display for troubleshooting.

@LizardByte-bot
Copy link
Member

It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!

@LizardByte-bot
Copy link
Member

It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks!

@LizardByte-bot
Copy link
Member

This issue was closed because it has been stalled for 10 days with no activity.

@LizardByte-bot LizardByte-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants