Try 140.4.0 ESR as a work around to give them time to figure out what they broke unless you depend on a feature in 144. [1] Works for me on Linux and Windows. Or try starting 144 in safe mode to disable all addons as a test.
I signed out, flushed all data, disabled all extension but it did not help.
Incognito mode works though..
Hmm.. in normal mode, I see that https://rr5---sn-t0a7ln7d.googlevideo.com is called but gets ns_error_unknown_host but in incognito mode rr5 is not called and all works. Changing to dns over https did not help. But I heard about the AWS outage today and that it has something to do with DNS so i think there's the issue. Though am not sure why incognito works.
Try 140.4.0 ESR as a work around to give them time to figure out what they broke unless you depend on a feature in 144. [1] Works for me on Linux and Windows. Or try starting 144 in safe mode to disable all addons as a test.
[1] - https://ftp.mozilla.org/pub/firefox/releases/140.4.0esr/
I signed out, flushed all data, disabled all extension but it did not help.
Incognito mode works though..
Hmm.. in normal mode, I see that https://rr5---sn-t0a7ln7d.googlevideo.com is called but gets ns_error_unknown_host but in incognito mode rr5 is not called and all works. Changing to dns over https did not help. But I heard about the AWS outage today and that it has something to do with DNS so i think there's the issue. Though am not sure why incognito works.
The only other thing I could suggest is use the web console network tab to see what requests may be hanging or timing out when not in Incognito mode.
Works for me on Firefox for Android with version 143.0.4. And I just updated to 144.0 and tried again, and that is working also.
Phone is not a problem, desktop is.
Just had a chance to try version 144.0 for desktop on Windows, and that's working for me also.
I also have problems with Firefox. I guess it is something Google related...