https://goodhertz.com/la-210/

Anyone else have this issue?
It's free beta but saying no license



*Scratch that. Had to log in with a Goodhertz account

 

Last edited: May 9, 2026 at 6:41 PM

You have to create a Goodhertz account and register... for do that you have to erase the goodhertz entries in your hosts file.

 

Right, and then the next time you open your DAW after that; any other Ghz plugins you might have will be deauthorized. (depending on your firewall rules).

 

Thankfully, not the case. I blocked them with terminal, just in case.

 

Not really free in that respect then...

 

Ghz timebombing legit software is kinda of a trip

 

I really just plan on adding it to my account so I have access to it and putting the installer with the rest, but I don’t use much if any goodhertz so it’s fine not being registered yet… are there a limited number of activations for these cause I might only install in my MacBook

 

Most people do not block developers' web domains via hosts file because they are using legit software. Ghz are up there with DMG in relation to time bombs, home calling, and whatever other deauthorization methods they may use.

 

Same with legit Ujam UFX Reverb2. I block my DAW and the timebombs stopped. This goodhertz plugin is really good so I hope it works the same. Funny how the worst is Spitfire Labs free though. That has a special dark magic to it...

 

It is pretty good

 

You don't have to "erase it".
You could alter it temporarily, or allow temp access via BlueLife's Hosts Editor, or simply use a VPN to sign up.
Unless it requires constant connection, just signing up to download stuff should be fine.
I've done it hundreds of times.

 

I was using some cracked Acustica plugins with my legit ones by just having the cracked ones in a custom VST3 folder. I did this for a month or so before i ended up buying them, and never had an issue. Even when logging in to their authorizer. Now don't quote me, but I imagine something like that would be possible with these as well. Im not sure where all Ghz keeps any additional license files and so on, but if you know that, you can try moving the physical plugins to an external folder, temporarily moving any associated licenses, logging in and authorizing the free one, then logging out. Just a thought.

 

Close, but not exactly. You can definitely edit your hosts file, write the changes to the file, go download the demo/beta plugin, install it, like you suggest, and that will work fine. Then you re-edit your hosts file back so their domain is blocked again. If the demo/beta software wants to phone home, it will deauthorize. That's still better than the alternative.

VPN usually does not just route around your hosts file blocking domains. Using hosts file to block domains is not entirely foolproof either. Some software that a developer wants to leak data will just use different web domains to do so. A firewall where you can just do all this blocking at a more granular level, like Little Snitch does, gives you a lot more control. Hosts file is best as a last resort.

 

Yes, exactly.
I use WFC but we are talking about hosts file here.
I also add to the hosts file as a matter "completeness" and of keeping track.
But to simply register & download software, it's easiest for me to just use a VPN in my browser.
No need to edit anything.
Demo/beta software will not necessarily "de-authorize" just because it "wants to phone home".
It may just not launch, or it may give an error window, or it may run but fail to download content... or it may actually run fine and show a blank spot where an advertisement is intended.
it all depends on what it was written to do.

 

How would this work (vpn) if the plugin needs to connect from your DAW? You would still need to move or hide the other plugins no?

 

The issue with VPN not getting around your hosts file is that the hosts file operates before the network stack ever gets involved. At that point the system has already resolved the domain locally, so there’s nothing left for the VPN tunnel to route.

In OSI terms, it’s happening before you even get to the layers where routing and encapsulation (Layer 3 and below) matter. The VPN can only carry traffic once an IP destination exists, but the hosts file effectively short-circuits name resolution at the OS level and prevents that step from ever reaching the network path.