I've been trying to figure out why Chromium throws TLS handshake errors and completely refuses to work when connected to a wireguard server, but only while conn

I've been trying to figure out why Chromium throws TLS handshake errors and completely refuses to work when connected to a wireguard server, but only while connected to some networks. So when I'm in my university's WiFi using wg+Chromium I'm fine, but when I use my Android's hotspot, Chromium refuses to work with wg due to TLS handshake errors. Very weird, I really wonder what causes this. Some routing settings on my Galaxy?! Other people seem to report similar issues, presumably with different networks[0]. The workaround suggested in the OP is to go to chrome://flags/#enable-tls13-kyber and disable it. Everything works again. 0. https://old.reddit.com/r/mullvadvpn/comments/1c006a9/has_chrome_totally_throttled_mullvad/ https://old.reddit.com/r/mullvadvpn/comments/1c006a9/has_chr...