Hello. I've suddenly started having 'ssl handshake failed' error when I try to run imaginando VS2 and I also can't get into my account with them, just a black screen. It is all working on my other computer though. I've had a look at fixes but none work. I've checked my virus protection and it's not blocked. It's not happening with any other plugin.

Any thoughts on what might be happening? Or any suggestions on what I can do appreciated?

Thanks

Rob

 

is your computer up-to-date ? root security certificates do expire indeed

 

Check Your Windows/Mac System Time and Date
This sounds deceptively simple, but it is the number one cause of sudden SSL handshake failures.

• SSL certificates are highly sensitive to time. If your computer's system clock is off by even a couple of minutes compared to Imaginando’s server, the security handshake will instantly fail.
  
  
• The Fix: Go to your system clock settings, toggle "Set time automatically" off and then back on, and force a sync.
  

 

Thanks. I had checked the time but not switched it on and off. Didn't work. System's up to date.

I have installed software from the sister site, needed to run any plugin they've been working on. I'm wondering if it's something to do with that.

 

Here are the new "Team R2R" activation tools, which must be installed for newer R2R software.

TEAM R2R INM810 inMusic Activator v1.0.1-R2R
TEAM R2R R2R-WAIFU v1.8.0-R2R
TEAM R2R RLM Activator v1.0.0-R2R
TEAM R2R Root Certificate-R2R
TEAM R2R Steinberg Silk Emulator v1.5.0
TEAM R2R System v1.3.1-R2R
TEAM R2R Turbo Activate Activator v1.0.0-R2R

Spoiler: The new R2R Tools:

TEAM R2R INM810 inMusic Activator v1.0.1-R2R
INM810 is modern auto activator for inMusic Brands software. INM810 uses
"software-unlock.dll", the inMusic official library to get computer
information and encrypting account login data.
The license and account information generated by INM810 doesn't conflict with
legit inMusic login and authorization.
Using R2R System, INM810 and R2R patched releases will bring the best
reliabilty to the inMusic software.

TEAM R2R R2R-WAIFU v1.8.0-R2R
A witch says,
Love your new R2R-WAIFU!
R2R-WAIFU is a DLL level emulation of WIBU CodeMeter Core API and WUPI. Simple and fast solution ever and using just 100+ KB for everything. R2R-WAIFU is compatible only with R2R releases. It does not affect original CodeMeter and protected applications.
R2R-WAIFU is compatible only with R2R releases. It does not affect original CodeMeter and protected applications.
TEAM R2R RLM Activator v1.0.0-R2R
RLM (Reprise License Manager) is used by big players like Maxon, BorisFX,
Serato

TEAM R2R Root Certificate-R2R
A witch says,
Recent years, we have more troubles with un-signed binary.
From 10,000 release, we decided to sign our tools (emulator, system DLL, other utility) with our own signature.
If you are a heavy R2R release user, this certificate may help you!
Note that we sign only installable binary. We don't sign one time medicine like patch or keygen. Test tool is also included
Nice google keywords :
"Windows root certificate install"
"certmgr import root certificate"

TEAM R2R Steinberg Silk Emulator v1.5.0
Witches bring the true emulator of Steinberg Activation Manager (official code
name : Silk). It supports all current Silk powered applications till now.
* Works with R2R Steinberg releases.
* R2R release doesn't affect the legit Silk installation (both applications
and Activation Manager).
* Emualated by single DLL less then 10KB DLL. No background process will run
like original Activation Manager.
* Super efficiency, More than 5 sec faster on some computers.
Read included R2R.txt to check how to install and how legit Silk works.
v1.5.0 - IDE update. Internal blacklisting function.

TEAM R2R System v1.3.1-R2R
R2R System contains essential tools and runtimes for our releases.
v1.3.1
- New : EZKG_GetFileInfoIndex() is available. It returns index value of
BY_HANDLE_FILE_INFORMATION.
- New : EZKG_GetMacAddress() is available.
- Fixed : Fixed crash in EZKG_RandomBytesFromTable().
- Fixed : Fixed graphic handle leak, redrawing issue in WitchWand.
------------------------------------------------------------------------------
Comments for this update :
* New EZKG funcs are used in STL release.

TEAM R2R Turbo Activate Activator v1.0.0-R2R
A witch says,
As you already noticed, R2R is now focusing on "efficiency" for both crackers
and users. Our new internal automation system and R2R System are drastically
reducing the boring job from us. We've released more than 200 releases incl.
some big bundles (with single installers + batch!) in 4 weeks.

 

Thanks. It's legit software. However, I did try the R2R refill packs for VS2 which didn't work properly.

Are all those files on the sister site? I know I've got latest RLM activator installed.

 

Yes! Newer versions are likely available!

 

Updated everything but still the same.

 

Imaginando VS2 v2.0.0 U2B Mac [MORiA]

4 User say:

~ asks for license
~ asks for licence in the daw but works in standalone for me
~ works in Rosetta
~ Demo mode here, too...

 

are you able to use SSL successfully via web browsers? if yes, that would indicate that the problem is not with your system per se. Sounds more like a problem with the release, or internal bug with the app itself...

 

SSL handshake issues can be ISP related, meaning that the issue is not in your end. Try using a VPN or a phone through mobile data and see if it works.

 

Honestly, not surprising. SSL has always been kind of a prick. Go with Neve, almost always handshake guaranteed.

 

there is no rule saying that whatever registration and authorisation processes will also work for unofficial copies, which often are decrypted or cracked or the network functions removed or whatever.

in some cases, like protools, you can not even mix legit and non-legit products if they are different software.

if you want to be on the safe side, either use the factory installers for a regular authorisation - or go the "pay for the software but install the crack" route, which is the best thing you can do anyway.

 

The other correctly working machine effectively serves as a "Known Good" template, proving that your ISP, router, and the plugin's server are all working correctly. Sometimes a machine caches a "bad" handshake attempt or an expired certificate.

Go to Control Panel > Internet Options > Content tab and click Clear SSL State. Restart the plugin, maybe even reboot.

Spoiler

Clearing the SSL State is arguably the best first step for a non-technical person because it is safe, instant, and requires no technical configuration of the operating system.
It acts like a "refresh" button for your computer's active secure connections without deleting passwords or breaking other settings. If the "bad" machine simply has a hung session or a cached error from a previous failed attempt, this will often fix it immediately.
How to do it:

1. Click the Start button and type "Internet Options".
2. Go to the Content tab.
3. Click the Clear SSL State button.
4. You should see a message saying "The SSL cache was successfully cleared."
5. Restart your DAW or the audio plugin and try again.

Why it's the right place to start:

• Zero Risk: Unlike editing the Registry or changing Firewall rules, you cannot "break" anything by clearing the SSL state.
• Eliminates the "Glitch" Factor: It forces the machine to perform a brand-new handshake with the server from scratch, ignoring any old, corrupted data it might be holding onto.
• It's Fast: It takes about 10 seconds.

If that doesn't work, the next "easy" check is to ensure the Date and Time on the broken machine perfectly match the working machine, as even a 2-minute difference will cause an SSL handshake to fail.

For those of us reading AI and trying to summarize and guessing (so others don't know you already went and looked) ;) , you might as well just spoiler the whole thing anyway instead of getting differences between two local machines on the same network so easily ruled out wrong. lol.

Spoiler

The most likely culprits in this "one works, one doesn't" scenario are:
1. Differences in Cipher Suite Priority
Windows doesn't just need to have a cipher; it needs to try the correct one in the right order. If the working machine has a specific cipher at the top of its list and the failing machine has it at the bottom (or disabled), the server may time out or reject the handshake. [1]

• Action: Compare the lists on both machines using PowerShell:
  Get-TlsCipherSuite | Select-Object Name
• Fix: Use IIS Crypto to "Copy" settings from the working machine to the broken one by using the Save Template and Load Template features. [1]

2. Missing or Untrusted Root Certificates
The failing machine might be missing a specific Intermediate or Root Certificate required by the plugin's server. [1]

• Action: Check the "Trusted Root Certification Authorities" in the Certificate Manager (certmgr.msc for user, certlm.msc for local machine).
• Tip: Windows usually updates these automatically via Windows Update, but if updates are paused or a specific "Root Certificate Update" failed on one machine, it won't trust the server's identity. [1, 2]

3. Application-Specific Firewall Rules
Even if the general firewall is "on" for both, there may be a specific outbound rule blocking your plugin or its host DAW on only one machine. [1, 2]

• Action: Open Windows Defender Firewall with Advanced Security (wf.msc) and check Outbound Rules. Look for any red "block" icons associated with your plugin's .exe or your DAW. [1, 2]

4. Third-Party "SSL Inspection"
If you use antivirus software (like Avast, Bitdefender, or Kaspersky), they often "inject" themselves into SSL connections to scan for malware. [1, 2]

• Action: If one machine has "Web Shield" or "SSL Scanning" enabled and the other doesn't, that is your culprit. These tools replace the server's certificate with their own, which many audio plugins reject for security reasons. [1]

5. Clear the "SSL State"
Sometimes the machine caches a "bad" handshake attempt or an expired certificate.

• Action: Go to Control Panel > Internet Options > Content tab and click Clear SSL State. Restart the plugin after doing this. [1, 2]

To pinpoint the exact cause, try to find the plugin's log file (usually in %APPDATA% or the plugin's installation folder). Does it mention a specific error like "Unknown CA" or "No shared cipher"?