4 ms·
Have you tried uninstalling Firefox, deleting any residual appdata, and installing again? Have you tried installing the same version of FF Nightly and FF on ano
by nabakin 5y ago
Have you tried uninstalling Firefox, deleting any residual appdata, and installing again? Have you tried installing the same version of FF Nightly and FF on another macOS computer?
- stjohnswarts 5y agoMuch less radical is just to use the command line options to create a new profile and see what happens. I have fixed obscure problems in firefox by blowing away the profile. 99% of what I need is stored in firefox sync so it's an easy process to delete an old profile and sync back up. Sounds like OP wants to get to the bottom of this though as a haX0r-ng project.
- pvinis 5y agoprofiles need no command line anymore. Just use `about:profiles`, it's pretty cool!
- soapdog 5y agoNot yet. I'm trying to figure out what is going on before destroying everything. I did try two different versions of Firefox on the same machine though (with different profiles).
- nabakin 5y agoI'd try installing your version of FF Nightly on another macOS computer to rule out that possibility. Maybe it's not a config issue but something to do with Nightly which is affecting your other, release FF
- floatingatoll 5y agoDid you reuse existing profiles on both versions, or in either case did you start a completely fresh profile? If you haven't yet tested with a newly-created profile (which doesn't require deleting your existing profile), then you need to do so in order to triage whether the problem is with Firefox-by-default or Firefox-and-your-profile.
- nabakin 5y agoSince it exists in both versions of FF, could you have anything installed which could be interfering with FF's communication with the rest of the internet? Are you on a network with a router which is able to modify your traffic (requires custom SSL certificate) (long shot)?