Version 63.0.1, YouTube videos not showing on Mac
I'm using YouTube from a Mac with OS Mojave version 10.14, Firefox version 63.0.1. YouTube videos just aren't showing up for me, either on the YouTube site or embedded. This is true:
- for multiple videos;
- after deleting YouTube's cookies from my browser;
- whether I'm signed into YouTube or not;
- whether I disable AdBlock (and my other handful of extensions) or not;
- whether I started Firefox in Safe Mode or not.
I've attached a couple of screenshots of what YouTube looks like for me. Most of the time it loads correctly, but the video just doesn't appear. Sometimes (e.g. after disabling all add-ons and refreshing) it loads the other, whiter, even less interactive option. Oh! And it works fine in Safari on the same device.
Help would be much appreciated please!
글쓴이 Balladeer 수정일시
선택된 해결법
Well, I don't know what happened, but it seems to be solved today, without me trying anything further on my end. I don't know whether it's a problem with Firefox, or YouTube, or what, but it appears to have been corrected.
Colour me confused, but I suppose this is solved? Hooray?
문맥에 따라 이 답변을 읽어주세요 👍 0모든 댓글 (5)
Start your Computer in safe mode with network support. Then start Firefox. Try Secure websites. Is the problem still there?
http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode Starting Any Computer In Safe Mode; Free Online Encyclopedia
Hi Fred, no dice from starting it in Safe Mode. I went straight to YouTube upon it finally starting up and clicked on a video, and got the same lack of video.
When you say 'secure websites', do you mean embedded ones? YouTube itself is https. Or am I misunderstanding you?
Any website whose address starts with; https:// (Like Mozilla) is secured.
I called for more help.
https://support.mozilla.org/en-US/kb/fix-common-audio-and-video-issues
선택된 해결법
Well, I don't know what happened, but it seems to be solved today, without me trying anything further on my end. I don't know whether it's a problem with Firefox, or YouTube, or what, but it appears to have been corrected.
Colour me confused, but I suppose this is solved? Hooray?
As long as it works. It could have been a corrupt file that was removed.