suddenly the repo cannot load

[spants]

On the latest version - it was working fine and now I get an error loading repo message..... Tried reinstalling.

[DavidBuchanan314]

This is the same underlying issue as RootMyTV/RootMyTV.github.io#9 (LG broke SSL)

[cpetry]

I also have this problem

[Informatic]

This should be fixed now, webosbrew repo is now hosted behind cloudflare with their own certificates.

[Soukyuu]

I am still having this issue, both homebrew channel failing to load repo and rootmy.tv complaining about SSL. I am on 6.00.25, 55B7D device. Is there any steps I can rake besides fully resetting my TV?

[throwaway96]

@Soukyuu
W17H (M16P) firmware 06.00.25 (webOS 3.9.0) is vulnerable to RootMyTV v1 and v2, so if you can get past the SSL issue it should work. https://rootmy.tv does seem to be using Let's Encrypt, which old LG firmware doesn't support. A factory reset will not help. If the TV is already rooted, your best course of action is probably adding the CA used by Let's Encrypt to the system cert store (something like this). If it's not rooted, you can try https://rootmytv.inf.re/, which uses a different CA.

Further details: rootmy.tv and webosbrew.org both use Cloudflare. Until a few days ago, Cloudflare had been providing TLS with a CA certificate that was trusted on older webOS firmware. It seems that now the only certificates available via Cloudflare (unless you pay) are from Let's Encrypt, and their CA isn't trusted on older webOS firmware. And if you update your firmware, RootMyTV will no longer work. Currently https://rootmytv.inf.re/ is probably the best option.

Regarding RootMyTV: You can host RootMyTV on a local HTTP server (e.g., I've used python3 -m http.server) and then navigate to your local instance in the TV's browser. You could also use your PC's browser to view index.html locally (file:) and supply your TV's IP address (although I've never done that myself). By default it will try to get stage2.html from https://rootmy.tv, but you can edit the URL in index.html.

I believe com.webos.app.facebooklogin requires stage2.html to be served over HTTPS, but it's possible it uses a different cert store than the browser. You can change the priorities of the apps (com.webos.app.acrcard, com.webos.app.facebooklogin, com.webos.app.alibaba) so that a different one gets chosen. acrcard is apparently broken on 3.x, but it still may be worth a try. I do not believe alibaba is present on W17H.

Much of index.html is devoted to working around origin issues and establishing an SSAP connection. Instead of using it, you can also just connect to the TV using an SSAP client and send the SSAP request manually. The endpoint is always ssap://system.launcher/launch, and the payload will be:

{
"id":"<target app>",
"params":{"<param name>":"<stage2 URL>"}
}

Each target app has its own parameter name:

• com.webos.app.facebooklogin: server
• com.webos.app.acrcard: contentTarget
• com.webos.app.alibaba: target
  You can either try to use the RootMyTV hosted stage2.html URL (https://rootmy.tv/stage2.html) or host it yourself.