-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Comments
I'm also getting error 503 this is on both Android and Linux Moonlight clients and from Linux and Windows Sunshine servers. |
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 |
I edited the config file but it still say that provided device doesn't
support required NVENC features
Il gio 9 nov 2023, 05:12 thatsysadmin ***@***.***> ha scritto:
… 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 which your
machine doesn't have.
In your config file, try changing output_name to 0 or 1. See if you get
an output from either one.
—
Reply to this email directly, view it on GitHub
<#1765 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6ICDA5QSY4QGBOZKLY5C6DYDRJ3HAVCNFSM6AAAAAA6F5BYR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBTGEZTINJXGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
With that configuration change I specified, What does the log look like now? Also: what does 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 |
This is the log: This is the nvidi-smi output: 'xorg-x11-drv-nvidia-470xx-cuda' How can i disable the resolution block? |
This isn't
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. |
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! |
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! |
This issue was closed because it has been stalled for 10 days with no activity. |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue 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
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: