[Bug]: Local API errors, Invidious API errors, Legacy formats not supported

[gellenburg]

Guidelines

• I have encountered this bug in the latest release of FreeTube.
• I have encountered this bug in the official downloads of FreeTube.
• I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
• I have searched the documentation for information that matches the description of the bug I want to file, without success.
• This issue contains only one bug.

Describe the bug

1. Just installed FreeTube 0.23.2 Beta AppImage from https://github.com/FreeTubeApp/FreeTube/releases/download/v0.23.2-beta/FreeTube-0.23.2-amd64.AppImage -

2. Went to click on a video -

3. Getting a bunch of API errors. (The same errors with 0.23.1 Beta, and the same errors that started cropping up sometime back in January.)

Note: I've tried this both with a VPN (Mullvad) and without (Tmobile 5G Hotspot). I have NOT tried with Tor.

I have also tried using the native .deb package and received the same results.

Expected Behavior

The video to play.

Issue Labels

API issue

FreeTube Version

0.23.2 Beta

Operating System Version

Linux Mint 22.1 Xia, AMD/x86 64

Installation Method

.AppImage

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

No response

Additional Information

It used to work fine then suddenly stopped working sometime in January.

Nightly Build

• I have encountered this bug in the latest nightly build.

[absidue]

Failed to fetch usually means something is wrong in your network configuration. Please make sure that you do not have a proxy configured in the proxy settings in FreeTube and that you have nothing blocking the jnn-pa.googleapis.com domain such as a PiHole on your network.

[gellenburg]

Failed to fetch usually means something is wrong in your network configuration. Please make sure that you do not have a proxy configured in the proxy settings in FreeTube and that you have nothing blocking the jnn-pa.googleapis.com domain such as a PiHole on your network.

Nope. No proxy. In fact, I nuked the config and manually imported my saved subscriptions. Haven't made any changes to the config.

Regarding the GoogleAPIs... Nope, no PiHole but I do use NextDNS.io, and it appears that that domain is blocked:

I've gone ahead and whitelisted the domain:

OK...

Getting farther...

[gellenburg]

These are all the domains that have been blocked in the past couple of minutes. Do any of these need to be enabled do you think?

The irony is YouTube works just fine in my browser. (Firefox with Ublock Origin and Sponsor Block).

[efb4f5ff-1298-471a-8973-3d47447115dc]

Do you get these new local api errors with or without vpn?