Another workaround: https://confluence.atlassian.com/display/GHKB/License+is+for+an+older+version+and+maintenance+has+expired+message+when+license+expires

This problem has not yet been resolved for me. I have a support case open and support folks are trying to help. My license had expired at GH 5.9.1, but after some fixes came, I upgraded UPM to 2.1.1 and GH to 5.9.3 (as per my current understanding I shouldn't have upgraded GH), later then rolled back to 5.9.1 but still no luck. Have tried clearing cache, removing work directory and all kinds of sequences. If anyone can suggest a fix, that would be great.

As Jason pointed out in his linked issue, I skipped a step in the fix process I described this morning.

Right, I should have added an extra step to my comment on GHS-4887. After updating to UPM 2.1.1+ (either 2.1.1 or 2.1.2 would contain the fix), your GreenHopper may still report itself as having a maintenance-expired license. This is because plugin licenses get cached and are only recomputed once a day.

To refresh your cached GreenHopper license you can do the following:

1. Copy your GreenHopper license in your UPM (Plugin Manager)
2. Remove the GreenHopper license in your UPM such that it says it is unlicensed
3. Paste (re-enter) the GreenHopper license and submit it.

So to resolve this problem, the complete solution should be:

1. Update to UPM 2.1.1+.
2. Do not update to a newer version of GreenHopper, as this may be build after your license's maintenance expiration date.
3. Clear your cached GreenHopper license if needed.

Cheers,
Ben

I posted a workaround for my issue in the linked jira issue.

Until the 12th (when we started having problems) our previous setup was as follows:

Jira 5.0.2
UPM 2.1.1
Greenhopper 5.9.3
(This SHOULD have worked and not caused any issues.)

Then on the 12th (when the maintenance expired and we started having problems) we changed it to:
Jira 5.0.2
UPM 2.1.2
Greenhopper 5.9.3

Then when 5.9.4 was released we updated to:
Jira 5.0.2
UPM 2.1.2
Greenhopper 5.9.4

Then also tried:
Jira 5.0.2
UPM 2.1.1
Greenhopper 5.9.4
just for good measure.
None of these setups worked.

Thanks for the help, but the bug has already been filed and linked to this issue, however i have not received ANY news on it.

Jason, Kevin,

To fix the problem, please update your Universal Plugin Manager (UPM) to 2.1.1 and do not update your GreenHopper version. You can update to UPM 2.1.1 from with your JIRA's UPM (Plugin Manager).

UPM 2.1.1 fixes the bug where GreenHopper's maintenance expiration is erroneously reported. However, if you update to a newer version of both the Plugin Manager and GreenHopper then it is possible that your new GreenHopper version will be built after your license maintenance expiration date, which will correctly be reported as a maintenance expiration error.

If this does not resolve your issue, please file a ticket at https://support.atlassian.com.

Cheers,
Ben

I have the same issue. Our maintenance expired yesterday and now get the same screen as reported here.

Sounds like it would be worth raising this with https://support.atlassian.com Jason, they can help you work out what's going on

Could anyone help me out with the versions i would need to fix this bug?
As was the case with Vitaliy Rybin, our licence expired yesterday (12.04.12) at which point we were already running with Greenhopper 5.9.3, Jira 5.0.2 and UPM 2.1.1
We had just upgraded everything on the 02.04.2012, so all the versions are current, however Greenhopper suddenly (12/Apr/12 4:00 PM to be exact) will only redirect us to the plugin manager.
in the log is see "com.atlassian.extras.common.LicenseException: You cannot update to GreenHopper version 5.9.3. Updates are no longer available." --> it was already at version 5.9.3
any ideas?

UPM 2.1.1 has been released with a fix for this issue. You can update to UPM 2.1.1 from within your JIRA's UPM (Plugin Manager).