I am getting an Alert, that says, "The URL is not valid and cannot be loaded.
Can't think of anything else to say.
All Replies (3)
Start Firefox in Use Troubleshoot Mode in Firefox to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
- Don't make any changes on the Safe mode start window.
- https://support.mozilla.org/kb/Safe+Mode
i get the same message, "The URL is not valid and cannot be loaded.". i've narrowed it down a bit more. i've got a freshly installed firefox US 9.0.1 on a freshly installed windows xp pro sp3 US (fully patched). a freshly installed separate firefox 3 install is on this machine too, but that does not seem relevant. the problem only occurs when i load https-urls with invalid certificates (eg self-signed) in the case that i use a firefox with a non-default profile. so the "default" profile displays a "this page cannot be trusted" screen as expected, i can open the url. but in a different firefox instance/profile, when going to the same https url, i get the error popup. the firefox profile/instance is started like this: firefox.exe -P dev -no-remote.
i have reinstalled firefox 9 & 3 because of this issue. the problem stayed. i didn't remember whether i could load the https url with the default before the reinstall. perhaps i couldn't...
OK, more info. profiles seem to be shared between ff3 and ff9. that is, i can use a ff3 profile with ff9 and vice versa. if i create a new profile with ff3, launch ff3 with that profile, quit that ff3 instance, and then launch ff9 with that profile, i can access https-urls with invalid ssl certificates just fine. if i create the profile with ff9, or if i don't start ff3 with that profile at least once, i will get the error.
i think i ran ff3 once before running ff9 for the first time. that would mean i ran ff3 on the default profile. so it may even be the case that everyone with a freshly installed ff9 will have this problem...
update: i have to whitelist each invalid https url or certificate (don't know which) in ff3. then ff9 can open the page as expected. ff9 with non-yet-whitelisted invalid ssl certificates will raise the error.
Modified by mjl0