Riggs Posted September 25, 2023 Share Posted September 25, 2023 I just paid to upgrade my C2 license to Professional tier, but noticed that my C2 server is now unable to validate licensing. I noticed that https://c2.hak5.org is (at the time of this post) throwing an SSL error so I'm guessing this might be why: My original community license C2 is now stuck in a licensing prompt loop and I can't spin up a fresh C2 as during setup all I'm getting are infinite 500 and 418 errors (lol). Any staff around that might be able to resolve this please? Link to comment Share on other sites More sharing options...
Irukandji Posted September 25, 2023 Share Posted September 25, 2023 No staff here (work for hak5). Only way to contact them is here. https://hak5.customerdesk.io Link to comment Share on other sites More sharing options...
Riggs Posted September 25, 2023 Author Share Posted September 25, 2023 21 minutes ago, Irukandji said: No staff here (work for hak5). Only way to contact them is here. https://hak5.customerdesk.io Thanks, I've just raised a support request and added a link to this post. Link to comment Share on other sites More sharing options...
Riggs Posted September 25, 2023 Author Share Posted September 25, 2023 Another user has reported the same issue on Discord. It looks like the https://c2.hak5.org cert expired 2 days ago: https://crt.sh/?id=9739993486 I suspect like this is a wider issue possibly affecting all Hak5 C2 instances. For now, if you have a live Hak5 C2 running and are not experiencing any issues, I would recommend you do NOT click re-activate or upgrade, as this will likely cause your Hak5 C2 to try to contact the https://c2.hak5.org licensing server and you'll end up with the same problem we have. Link to comment Share on other sites More sharing options...
dark_pyrro Posted September 25, 2023 Share Posted September 25, 2023 It will contact the server at least during normal startup as well, so those that want to start an "untouched" C2 server will have problems as well. I seem to remember that it checks it periodically when running as well, but I might remember that wrong. As I said on Discord, it affects instances that has been installed years ago as well, so it's not directly related to upgrades specifically (I also tried with the 3.2.0 binary and it does the same thing, i.e. doesn't start since it can't verify the license against the Hak5 infrastructure). Link to comment Share on other sites More sharing options...
Riggs Posted September 25, 2023 Author Share Posted September 25, 2023 Looks like all resolved now. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.