That is not the issue. The certificate for the plugin is no longer trusted due to a change in the Chrome browser. This is a known issue. It works with the Edge browser.
Testing this is easy: when you try the same in a Chrome Incognito window the issue also appears, which rules out cache and cookie issues.
