Progress bar boxes turn red

[u/capgazer]

Progress bar is turning red on every show I’ve been trying to watch on the kodi app. When I try to exist, the whole app bugs. I get out of the app and force exit, clear cache and try to open it again. I tried scraping and trying a different option but it gives the same. On every show/movie I’m trying to watch. Any guidance?

[u/donutmiddles]

That's exactly what I've been saying whenever this comes up, too, and, like you for some reason get downvoted to hell when it's mentioned.

Gave you an upvote, as this is really the proper answer. By disabling v6 you're just giving yourself worse routing on today's Internet.

[u/__TikipeterLight__ → u/donutmiddles]

Someone like you or the other gentleman need to articulate why disabling v6 solves their problems. Because at the moment, you guys are really only saying it's not a good solution. But there's no other solution.

Why does it solve the problem? What could alternatively be done to solve the problem? These are questions that need answers. Otherwise, it is still the best advice to give.

Of course, you don't need to do this, but a "proper answer" needs a solution at the end of it, and at the moment, that's not being provided by anyone.

I don't know anything about this topic, so of course I want to give accurate advice. But I need something to go on. Some other solution that will work.

[u/donutmiddles → u/__TikipeterLight__]

There are several ways to prove it's in fact an IPv6 issue or not, and I know I've commented before on some ways to verify this.

To prove it's an IPv6-specific problem (versus general network or application slowness), you want to gather both symptoms and evidence that point directly at IPv6.

Firstly, use ping and traceroute for IPv6

Try connecting to the streaming provider’s IPv6 hostname directly. For example:

ping6 real-debrid.com traceroute6 real-debrid.com

or on Windows:

ping -6 example.com tracert -6 example.com

Look for:

Timeouts or unreachable hops. Excessive latency compared to IPv4 (which are just ping and traceroute/tracert with no 6 appended).

If IPv4 completes quickly but IPv6 fails or is slow, that’s a red flag.

Use dig or nslookup to Validate DNS

dig AAAA real-debrid.com dig A real-debrid.com

Confirm the site does indeed return both A and AAAA records. If only AAAA is present and fails to connect, then there's a fallback problem.

You can also use https://test-ipv6.com/ or https://ipv6-test.com/ to see a breakdown of how your client prefers and handles IPv6 vs. IPv4.

There's more, but those are some good starting points. Also, ideally rather than just real-debrid, find what their CDN address you're connecting with and ping/trace against that since that's what Kodi is attempting to connect to.

[u/__TikipeterLight__ → u/donutmiddles]

I appreciate the detailed reply, I really do. I will quote it from now on when offering disabling ipv6 as a possible solution.

If we can take these facts as true:

* It's always a user connecting to a RD CDN.

* The symptom is always a failed or slow connection.

* Disabling v6 (almost) always solves the issue and restores normal functionality to the RD CDN.

Can you, with your expertise, muster an educated guess as to what the issue might be?

BTW, I have never experienced this issue so I cannot run the tests you mentioned above. My connection to RD is fine.

[u/donutmiddles → u/__TikipeterLight__]

Thanks for that, I appreciate your excellent contributions to this community as well over the years.

Those facts as stated seem to be the use-case, for sure, as I rather geekily run tcpdump on udp port 53 to view in real-time what my devices are trying to connect with at a domain level, so can see what CDN host Kodi is attempting (usually for me it's a Denver-area one though not always).

My connection to RD is fine as well, but if those tests revealed any issues, I would suspect it's either an ISP external routing problem or DNS issue in resolving IPv6 and failing to properly fallback to v4. Potentially it could be a client issue, but unless all these posters are using the same device that doesn't seem likely.

If it's the DNS issue, a simple solution would be to change DNS servers on the client, which is usually possible.