Hello,
our tests in Firefox worked fine until saturday (May 4). Since then the Ranorex Plugin is always deactivated by Firefox with the error message "Ranorex Automation clould not be verified for use in Firefox and has been disabled" even after reinstallation.
We use Ranorex 9 and Firefox 60.3.0esr.
Why does this happen?
Firefox: Ranorex Automation clould not be verified for use in Firefox and has been disabled
Re: Firefox: Ranorex Automation clould not be verified for use in Firefox and has been disabled
This is a Firefox/Mozilla issue, one of their intermediate signing certificates apparently expired causing all extensions to be disabled. The issue should be fixed already by an update pushed by Mozilla. See here for more information:
https://blog.mozilla.org/addons/2019/05 ... n-firefox/
Regards,
Alex
Ranorex Team
https://blog.mozilla.org/addons/2019/05 ... n-firefox/
Regards,
Alex
Ranorex Team
Re: Firefox: Ranorex Automation clould not be verified for use in Firefox and has been disabled
Is there a quick workaround for the old version?
Re: Firefox: Ranorex Automation clould not be verified for use in Firefox and has been disabled
Hi,
There may be some workarounds available, but they are not recommended by Mozilla. This is what you can find in Mozilla's blog, related to this issue:
There may be some workarounds available, but they are not recommended by Mozilla. This is what you can find in Mozilla's blog, related to this issue:
There are a number of work-arounds being discussed in the community. These are not recommended as they may conflict with fixes we are deploying.
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Firefox: Ranorex Automation clould not be verified for use in Firefox and has been disabled
Enable the "Firefox studies" and wait a while (may be hours), this should eventually also re-enable extensions without updating, see the explanation by Mozilla in the blog:
https://blog.mozilla.org/addons/2019/05 ... n-firefox/
Regards,
Alex
Ranorex Team