Jump to content

C2 https acme error


Flatlinebb
 Share

Recommended Posts

I get an error when I try to access the c2 site on my VPS. There are no other web servers running on it, I use it for VPN server only.

Using the following command line (with hostname and IPs obfuscated):

./c2_community-linux-64 -db ./c2.db -hostname "xxx.xxxxxxx.xxx" -https

I get the following text when I try to access the website over https:

[*] Initializing Hak5 Cloud C2
[*] Running Hak5 Cloud C2
2019/11/11 11:07:59 http: TLS handshake error from xxx.xxx.xxx.60:6846: 403 urn:acme:error:unauthorized: Account creation on ACMEv1 is disabled. Please upgrade your ACME client to a version that supports ACMEv2 / RFC 8555. See https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430 for details.

 

Link to comment
Share on other sites

We're aware of the issue and will be releasing an update with ACMEv2 soon. Account creation should work again today. Let's Encrypt is doing 24 hour brownouts to call attention to the upgrade. In the meantime either wait the 24 hours for the v1 service to come back online, or provide your own keys using the appropriate command line parameters. 

  • Like 1
Link to comment
Share on other sites

On 11/12/2019 at 3:50 PM, Darren Kitchen said:

We're aware of the issue and will be releasing an update with ACMEv2 soon. Account creation should work again today. Let's Encrypt is doing 24 hour brownouts to call attention to the upgrade. In the meantime either wait the 24 hours for the v1 service to come back online, or provide your own keys using the appropriate command line parameters. 

I followed another post and made keys that got the server up and running. However, i'm curious if the C2 generated device.config file will still work to get my devices connected? or wait for update?

 

Link to comment
Share on other sites

The ACME / Lets Encrypt issue has been solved with the 2.1.0 update.

 

On 11/20/2019 at 3:02 AM, UnLo said:

I'm curious if the C2 generated device.config file will still work to get my devices connected? or wait for update?

You don't need to re-enroll your devices in the C2 after the update, if that's what you mean.

  • Upvote 1
Link to comment
Share on other sites

2 hours ago, Foxtrot said:

The ACME / Lets Encrypt issue has been solved with the 2.1.0 update.

 

You don't need to re-enroll your devices in the C2 after the update, if that's what you mean.

Really? I won't need to completely make new config files now that I've created a server with let's encrypt and ver 2.0? If I upgrade server to 2.1 it will just work? Impressive. 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...