We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I took a look codes and there is page for clients.( server.resource["^/clients/?$"]["GET"] = getClientsPage;)
But it is empty page. Is there any way to get client's information or check client is connected?
No response
Windows
Windows 10 20H
64 bit
0.22
Windows - portable
Nvidia
RTX 3060
497.29
Not relevant.
The text was updated successfully, but these errors were encountered:
That endpoint would return clients.html if it existed. It was probably a placeholder that never got completed.
clients.html
You can parse the logs I guess... there's no other way to determine the connected clients right now.
Sorry, something went wrong.
Woudl be great to see some info, such as SMPT settings and email notifications.
@sambuev There's #2042 that will allow to see paired devices and unpair, is that what you're looking for?
If you want more information, there's currently nothing planned.
No branches or pull requests
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
I took a look codes and there is page for clients.( server.resource["^/clients/?$"]["GET"] = getClientsPage;)
But it is empty page. Is there any way to get client's information or check client is connected?
Expected Behavior
No response
Additional Context
No response
Host Operating System
Windows
Operating System Version
Windows 10 20H
Architecture
64 bit
Sunshine commit or version
0.22
Package
Windows - portable
GPU Type
Nvidia
GPU Model
RTX 3060
GPU Driver/Mesa Version
497.29
Capture Method (Linux Only)
No response
Config
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: