iPhone > Safari webkit > WireGuard tunnel home network > PiHole DNS (Quad9 upstream) > WireGuard tunnel ProtonVPN endpoint

That is the flow of my current network.

Edit: I ran curl from my server

┌─[user@debian] - [~/compose] - [Thu Aug 13, 12:26]
└─[$]> curl -v https://angieguardian.org/
* Host angieguardian.org:443 was resolved.
* IPv6: (none)
* IPv4: 77.61.56.117
*   Trying 77.61.56.117:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* Recv failure: Connection reset by peer
* TLS connect error: error:00000000:lib(0)::reason(0)
* OpenSSL SSL_connect: Connection reset by peer in connection to angieguardian.org:443 
* closing connection #0
curl: (35) Recv failure: Connection reset by peer

┌─[user@debian] - [~/compose] - [Thu Aug 13, 12:27]
└─[$]> curl -v angieguardian.org 
* Host angieguardian.org:80 was resolved.
* IPv6: (none)
* IPv4: 77.61.56.117
*   Trying 77.61.56.117:80...
* Connected to angieguardian.org (77.61.56.117) port 80
* using HTTP/1.x
> GET / HTTP/1.1
> Host: angieguardian.org
> User-Agent: curl/8.14.1
> Accept: */*
> 
* Request completely sent off
* Recv failure: Connection reset by peer
* closing connection #0
curl: (56) Recv failure: Connection reset by peer

Can confirm my PiHole is resolving the requests and forwarding them to Quad9.

Yeah something ain’t right here chief. Now I have to ask, what was the LLM policy in regards to the development of this software?

Seems a little odd that the fediverse uses Cloudfare.

You need to be more descriptive, use in what regard? Both are capable DNS providers but as far as I’m aware, Cloudflare is also a domain registrar.

Also each instance of Lemmy is configured differently, perhaps Lemmy.zip uses cloudflare but that isn’t the case for every instance of Lemmy.

Chiming back in 3 hours later, just downloaded the latest release from Freetubes website, i can confirm that with my invidious instance that everything seems to be working fine. While my invidious instance is a private one, ill share it with you in the meantime until your normal setup gets back in order, shoot me a DM.

I’m not home to verify my Freetube however, I just checked my invidious instance and can confirm that the first video I attempted to play errored.

I am updating my Invidious instance to see if it still persists, perhaps the instances you’re using are out of date, I know invidious updates quite frequently to stay on-top of YouTube changes.

Edit; Updating invidious appeared to resolve my errors, I can only assume the instances you’re using are out of date. I’ll check Freetube when I get home.

Freetube is capable of utilizing the Invidious APi and provides more functions such as sponsor blocking or click-bait thumbnail removal.

Lots of customization features that I highly suggest pairing with Invidious.

Freetube either runs off of YouTube’s APi directly or an Invidious API to proxy requests to Youtube, how is your application configured? If you’re using Invidious have you tried another instance?

Have you read any of the issue reports on their GitHub? it seems like issue #9526 might be what you’re looking for.