-
-
Notifications
You must be signed in to change notification settings - Fork 84
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 add device #163
Comments
Try going to |
UPDATE: I managed to resolve this by manually adding the device, and then this will fail, but it will allow me to access the screen, which will allow me to install apps. After accessing this screen, I follow the process of adding a device again, using the same steps in the first post. This then connected immediately, without any issues. |
Hello, I have the same problem on my LG TV with WebOS 05.50.15 (software version 4.4.2-11) Strange thing; the dev-manager application show port 9922; however on the console under which I started the application, I have the following error message: So although I setup dev-manager to use port 9922, the application seems to try accessing port 9991. And my WebOS TV is not listening on that port: Am I doing something wrong or is my WebOS version not supported ? Thanks a lot |
Dev Manager downloads the RSA key from an HTTP server on port 9991. This is what "Key Server" refers to. Make sure you are using the correct IP address for your TV (which you can confirm by using a web browser to connect to port 3000 via HTTP; you should see "Hello world" if you have SSAP enabled). You can also try disabling and re-enabling Dev Mode to fix the key server. |
Thanks for your reply. I am using the correct IP address; confirmed with the below screenshot. I have also tried to remove / re-install developper apps several times; rebooted multiple times and enabled / disabled dev mode as many times, but still no luck. I also tried to root my tv with rootmy.tv but my webos is unfortunately not vulnerable. I'm out of idea. The only thing I havn't tried so far is to reset my TV to factory settings. Any clue or hints of what else I could try ? Thanks a lot |
Also my nmap scan gives the following results:
And
I've again tried to disable / enable key server on the TV several times, but same results :-( |
Most likely the dev mode app has problems. And to ensure everything's reset, you'll need to first turn off dev mode, let the device reboot, then uninstall the dev mode app and reinstall that. If you tried that but it still doesn't work, maybe a factory reset will be the only solution. Without root we can't really figure out what's going on :( |
Thanks guys. I will give it a try and let you know. |
I tried uninstalling / reinstalling dev mode but no luck. I am discussing the point with LG support forum. Hopefully they may have a solution to provide before trying the factory reset. Thanks anyway ! |
I see LG suggested the same thing. Your TV wasn't previously rooted, right? |
No, it wasn't previously rooted. |
I have just factory reseted my TV but unfortunately that doesn't fix the issue. It seems to me the developper mode application is bugged for my TV model. Whatever I try port 9991 remains closed and I can't retrieve the private key. |
For the sake of reference: Model: OLED55B8PLA |
Not really necessary (or probably desirable) to post the serial and DRM stuff... The firmware version and SoC/OTAID would be more useful. |
How I got rid of "failed to fetch private key":
It worked for me and a couple other people, hope it works for you! |
@cackslop million thanks man ! That actually works. I could install jellyfin with homebrew, which was my initial goal. Thanks again !!! |
@cackslop you are the man, thanks a ton man. that worked. |
Had the same issue as @wisukind and this fixed it for me. |
I've been having the same issue now on my TV. It's on the latest WebOS23. I've done all of this below, and I've tried the EULA thing and nothing is working.
I can get the RSA key by running:
However, I don't get anything at port 3000, 9991, or 9922 in the browser. I get "connection reset", "404 not found", and "Invalid HTTP response" respectively. At the end of all of this, all I really want to achieve it being able to stop the LG TV from dropping into it's stupid clock/firework screensaver. I have my own media server screensavers that I would like to use instead. LG is so scared of warranty claims that they just refuse to give you any screensaver options. |
@justbest23 Dev Mode won't give you access to modify screensaver. However, if you want to use some other apps from homebrew channel, dev mode should still work without having root. Being able to get private key means that the key server and EULA stuff is working fine. But you may have entered a wrong passphrase. |
Hi @mariotaku the code is 100% not wrong. It's a 6 character password and it refuses to accept it. Not sure why. |
This works!!!! |
Describe the bug.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Connect to TV
Screenshots
Additional context
I have managed to connect to the TV using a different application.
I'm also able to ping my TV, but I get a constant failure to fetch the private key.
Add any other context about the problem here.
This is my first time trying to connect.
Connecting to the same wifi network. The TV and laptop are connected to the same router via a wireless connection.
I have switched from a 5G network to a 2.4G network just to rule this out (not sure if it makes a difference).
The text was updated successfully, but these errors were encountered: