This thread was archived. Please ask a new question if you need help.
Youtube (https)security certificate issue
I'm using latest firefox version with and recently I'm facing this strange issue ... everytime I try to visit youtube, to be specific, when not logged in on any google accounts .. I can visit http://www.youtube.com but when I try to login, in which case it redirects to https:// and It shows the following error(check image url):
And if I try to add exception, it shows this screen(check image url):
(PS: Couldn't find upload option here so I had to use otherimage hosts)
Also I tried changing windows time, adding auto time sync from windows site and also tried changing profile, disabling add on and testing and also tried removing cache/cookies from both google.com and youtube.com and so far nothing worked ... I can't seem to access youtube while logged in (https)
Also its only youtube, no other website shows this security certificate error!
please provide a solution to this asap, thanks!
finally i figured out the issue, it seems like i had a IP redirection setup at windows>hosts file for youtube a while back when youtube was blocked by the gov here.
so i removed it and everything seems to be working fine.Read this answer in context 👍 5
All Replies (20)
Ha, I use that same theme on my Firefox for Android, is there a chance that the certificate that was issued may be expired.
Check the certificate manager to see if there is a stored cert.
Also try navigating to [about:permissions] and search for youtube.com or s..ytimg.com
- Right click on the youtube page and select "Page Info"
- Click on Security
- Click on View Cookies
- Remove all and reload the page.
Please also see the troubleshooting steps Connection Untrusted Error Message
still the same ... it shows same error with cookies removed/being there ...
basically my issue falls under this:
"Certificate is only valid for (site name) (site name) uses an invalid security certificate. The certificate is only valid for (site name). (Error code: ssl_error_bad_cert_domain)
This error is telling you that the identification sent to you by the site is actually for another site. While anything you send would be safe from eavesdroppers, the recipient may not be who you think it is.
A common situation is when the certificate is actually for a different part of the same site. For example, you may have visited https://example.com, but the certificate is for https://www.example.com. In this case, if you access https://www.example.com directly, you should not receive the warning. "
but both with www and not with www results in same eror ...
gonna try removing the "cert8.db" file and lets see .. what happens ...
nope didn't work ... same ol error remains ...
come on .. no one know how to solve this?
Would this site be considered a third party cookie?Clear cookies and site data in Firefox orDisable third-party cookies in Firefox to stop some types of tracking by advertisers
Also if you have a copy of the cert (via add exception -> view certificate) it would be helpful to investigate cdn configuration. <keeler>
When you click Add Exception, you get a Google error page instead of a pop-up dialog? Or are you saying that after you added the exception, YouTube's home page won't load. That's mildly suspicious...
If you return to the Add Exception dialog and use the View button, how does the certificate compare with the attached screen shot?
Try to rename the cert8.db file in the Firefox profile folder to cert8.db.old or delete the cert8.db file to remove intermediate certificates that Firefox has stored.
If that helped to solve the problem then you can remove the renamed cert8.db.old file. Otherwise you can rename (or copy) the cert8.db.old file to cert8.db to restore the previous intermediate certificates. Firefox will automatically store intermediate certificates when you visit websites that send such a certificate.
If that didn't help then remove or rename secmod.db (secmod.db.old) as well.
im npt that much a tech geeky ... so if its not asking for too much, could one of you guys assist me with this using teamvirewer or skype screenshare please .... thanks in advance.
let me know if you're interfered.
You're up much earlier than me...
What if you try YouTube in a private window? You can launch a new private windows using Ctrl+Shift+p. Does it work any different or better there?
in private window ...with http .. works fine ... but with https ... results in same error .... what can i do with this darn issue ...
crying out loud .... someone please help !!!!
Try this temporarily: In order to change your Firefox Configuration please do the following steps :
- In the Location bar, type about:config and press Enter. The about:config "This might void your warranty!" warning page may appear.
- Click I'll be careful, I promise! to continue to the about:config page.
- Look for netwrok.websocket.allowInsecureFromHTTPS
but if it works in a private window, go to about:permissions and search for youtube.com. Click "Forget this site" and restart Firefox.
this is what i see:
please check the image ..
now what to do from here?
Who is the issuer of the certificate?
Check the date and time in the clock on your computer: (double) click the clock icon on the Windows Taskbar.
Check out why the site is untrusted and click "Technical Details to expand this section.
If the certificate is not trusted because no issuer chain was provided (sec_error_unknown_issuer) then see if you can install this intermediate certificate from another source.
You can retrieve the certificate and check details like who issued certificates and expiration dates of certificates.
- Click the link at the bottom of the error page: "I Understand the Risks"
Let Firefox retrieve the certificate: "Add Exception" -> "Get Certificate".
- Click the "View..." button and inspect the certificate and check who is the issuer of the certificate.
You can see more Details like intermediate certificates that are used in the Details pane.
If "I Understand the Risks" is missing then this page may be opened in an (i)frame and in that case try the right-click context menu and use "This Frame: Open Frame in New Tab".
- Note that some firewalls monitor (secure) connections and that programs like Sendori or FiddlerRoot can intercept connections and send their own certificate instead of the website's certificate.
- Note that it is not recommended to add a permanent exception in cases like this, so only use it to inspect the certificate.
here is the certificate in export format and an image ....
the cert url: http://fantchofinancial.com/cert/-.googlevideo.com
so no one can solve this issue? aww man .. this sucks
I can't figure out why you get a completely different certificate when you visit the site compared with the one I get (*.googlevideo.com vs. www.google.com). Considering that you get Google's 404 error on the URL that should serve the YouTube home page only after you log in, I am suspicious that this could indicate foul play.
Could it be a connection issue? By default, Firefox will piggyback on your IE LAN settings, but you can check and modify that here:
"3-bar" menu button (or Tools menu) > Options > Advanced > Network mini-tab > "Settings" button
The default is "Use system proxy settings" but you also could try "No Proxy".
It's possible that extensions also could influence how you connect to YouTube. If you haven't already, could you test the page in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions and some advanced features of Firefox. More info: Troubleshoot Firefox issues using Safe Mode.
You can restart Firefox in Safe Mode using either:
- "3-bar" menu button > "?" button > Restart with Add-ons Disabled
- (menu bar) Help > Restart with Add-ons Disabled
Not all add-ons are disabled: Flash and other plugins still run
After Firefox shuts down, a small dialog should appear. Click "Start in Safe Mode" (not Reset).
I filed a bug on this and I hope we can get more investigateion: https://bugzilla.mozilla.org/show_bug.cgi?id=1049190
For investigation, can you please add the certificates from the good computer and from the original computer having the issue. Thank you!