Did you disable all add-ons manually or use Safe Mode?

If you used Safe Mode, It could be the work of one of your add-ons, or it could be Hardware Acceleration. How to disable Hardware Acceleration {web link}

Type about:addons<enter> in the address bar to open your Add-ons Manager. Hot key; <Control> (Mac=<Command>) <Shift> A)

In the Add-ons Manager, on the left, select Extensions. Disable a few add-ons, then Restart Firefox.

Some added toolbar and anti-virus add-ons are known to cause Firefox issues. Disable All Of them.

If the problem continues, disable some more (restarting FF). Continue until the problem is gone. After, you know what group is causing the issue. Re-enable the last group ONE AT A TIME (restarting FF) until the problem returns.

Once you think you found the problem, disable that and re-enable all the others, then restart again. Let us know who the suspect is, detective.

I disabled them manually. This only happened after that certificate bug was fixed. Before that, all my addons worked perfectly. I have the same addons that I had BEFORE the certificate bug, I didn't add any new addons, toolbars or anti-virus software since getting the bug. The addons (before the certificate bug) worked perfectly fine with hardware acceleration on. This issue started SOLELY after the certificate bug was fixed. When my addons are enabled, I do not get any "unsupported version" message on any of my addons.

when you try private browsing mode, do websites load normally then (even with addons enabled)?

I took FredMcD's advice and disabled all my addons and then enabled them one at a time to see which one broke FF. It looks like UBlock Origin breaks FF. When that addons is enabled, FF will not connect to the internet. As soon as I disable it, FF connects. Oddly, once I connect and re-enable uBlock, my internet works fine and uBlock works fine. Its just that initial connection when FF first starts that causes the problem. I know 4 million+ users use uBlock so I know its a good addon, so i don't why it isn't working for me. Any advice?

By the way, FF worked fine with uBlock enabled BEFORE the certificate bug. So, it looks like the certificate bug fix broke uBlock. How, I don't know. I also deleted uBlock and reinstalled it but it still has the problem.

You should also contact UBlock support on this.

I posted on the uBlock reddit site, which is where they want you to post bugs. Thank you for your help

Please keep us posted.

Someone on the uBlock reddit site posted this:

Check for browser.tabs.remote.autostart in about:config. Should be true (Firefox multiprocessing enabled).

I tried this and it worked for me. Doesn't mean it would work for everyone but it is worth a try.

That was very good work. Well done. Please flag your last post as Solved Problem so others will know.