[FIX] “A network error has occurred” on TizenTube Cobalt (Tizen 9.0 Samsung TVs)

If you installed TizenTube Cobalt on a newer Samsung TV (Tizen 9.0, e.g. 2025/2026 models) via Apps2Samsung and get "A network error has occurred" the moment you launch the app, here's what's actually going on and how to fix it.

The real cause

It's not your DNS, your router, your certificate settings, or anything you configured wrong. On Tizen 9.0, the native Cobalt player has trouble connecting to 127.0.0.2 — the special "loopback" address TizenTube's local proxy server uses by default. The proxy service itself runs fine on the TV, Cobalt just can't reliably reach it at that specific address.

I confirmed this by testing the proxy port directly from another device on the network (http://[TV-IP]:8101) — it responded (not "connection refused"), proving the service was alive. The only thing broken was Cobalt's connection to 127.0.0.2 specifically.

The fix — point Cobalt at your TV's real IP instead of 127.0.0.2

No DNS server, no router hacking, no alternate builds needed. Just:

1. Reserve a static IP for your TV in your router's DHCP settings (look for "DHCP Binding" or "DHCP Reservation" — map your TV's MAC address to a fixed IP). This keeps the IP from changing later.
2. Unzip the .wgt file you downloaded (TizenTubeCobalt.wgt or the TizenTubeProxyAddress version) — just rename the extension to .zip and extract it.
3. Open config.xml in a text editor and find this line:

​

 --proxy=http://127.0.0.2:8101 

(or --proxy=http://tizentube:8101 if you used the ProxyAddress version)

Change it to your TV's real, reserved LAN IP, e.g.:

 --proxy=http://192.168.1x.1xx:8101 

1. Re-zip everything back into a .wgt (select all the files inside the folder — not the folder itself — compress to zip, then rename .zip to .wgt).
2. Reinstall via Apps2Samsung using the edited file — Release dropdown → "Custom WGT File" → select it. Make sure Force Samsung Certificate and Partner Signing are both enabled.
3. Fully power cycle the TV (unplug it, not just standby) and launch TizenTube.

That's it — no more network error.

Why this works

The app just needed a real, reachable IP address instead of the special loopback one that Cobalt struggles with on this Tizen version. Since the IP is now reserved via DHCP, it won't change on reboot, so the fix sticks permanently.

Hope this saves someone else the hours I spent on it. Happy to answer questions in the comments.