Chrome 42 removed support for NPAPI by default. This disables a number of plug-ins, including Java. You can bypass the browser’s Java plug-in by doing the following:
Contact your application owner to have access enabled.
If this does not fix the problem, contact your application owner.
Many organizations have policies governing inactive or unregistered accounts. Please contact your application owner to have your account enabled.
SecureLink customers can control access to their environment by disabling remote access until needed. If your connect option is grayed out, your access has been temporarily disabled and will have to be enabled by your customer.
Check your browser version – SecureLink supports the following browser versions:
* – There are minor defects in the layout of the user interface when viewed with IE7, due to its incomplete support for modern standards – these visual artifacts do not impact connectivity † – Chrome for Mac is 32-bit only and therefore incompatible on Mac OS X Lion or Mavericks, which use the 64-bit Java 7 plug-in – modern Macs with Java 7 should use Firefox – see Chrome issue 18323
Verify your Java version
Clear your cache
You can clear the Java cache in most cases by going to the Windows Control Panel – Java- Temporary Internet Files – Delete Files. To clear the browser cache in most I.E. versions, go to Tools – Internet Options – General Tab – Temporary Internet Files Section – Delete files. To clear the browser cache in Firefox you choose Tools – Options – Privacy – Private Data Section – Settings and check the Cache option, then click OK. Or you can simply choose Tools – Clear Private Data, which will clear private settings.
Delete your SlinkSW directory
Your first option is to contact your customer’s application owner or SecureLink Administrator for assistance. Additionally, you may contact SecureLink support by sending an email to email@example.com. It will be helpful (and almost always help us resolve your issue more quickly) to include the logs from your connection attempts when contacting SecureLink support. The instructions below will help retrieve these logs.
Retrieving Connection Logs