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

Can't connect via LAN to moonlight-tv client #154

Open
therecluse26 opened this issue Nov 28, 2024 · 4 comments
Open

Can't connect via LAN to moonlight-tv client #154

therecluse26 opened this issue Nov 28, 2024 · 4 comments

Comments

@therecluse26
Copy link

Hi, I'm trying to connect to my wolf server running on the same network as my LG TV running the moonlight-tv client, and when I put in the IP address of my wolf host, on the client I receive cURL error: HTTP response code said error and in my wolf logs I get Received HTTPS request from a client which wasn't previously paired.

I am never prompted to do a pairing or anything. Is this an issue with wolf or with moonlight-tv? The only reason I ask here is that after digging through the code, it seems to actually be more of a potential SSL cert issue, but I'm not 100% sure on that.

Additional context: I have successfully paired this to the Linux desktop Moonlight app.

@ABeltramo
Copy link
Member

Could you add an env variable to the Wolf container:

WOLF_LOG_LEVEL=DEBUG

and post the full logs when trying to pair from the TV? I really need some more info to understand what's going on..

@therecluse26
Copy link
Author

@ABeltramo I already had that enabled, the log that I sent you is literally the only line that gets logged

@maximushugus
Copy link

I have the same issue with the Received HTTPS request from a client which wasn't previously paired. I cannot pair the LG TV running moonlight because I do not get a pin either. I have a working linux desktop also working with moonlight on this TV.
I do not see any relevant info on the debug logs.

@ABeltramo
Copy link
Member

I don't have an LG TV to test this myself so I'd need someone to post the full logs from Wolf to get a sense of what's going on. Since debug might be not low enough, could you guys share the full Wolf logs, from the start when trying to pair with the following env variable:

WOLF_LOG_LEVEL=TRACE

?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants