sweeper707 Posted October 3, 2018 Share Posted October 3, 2018 Receiving the following error below. Anyone have any idea? Tried Ubuntu 18.x ,16.x /Windows 1803 and 1809 (latest) "acme/autocert missing server name" Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted October 3, 2018 Share Posted October 3, 2018 Hi @sweeper707, When using the -https flag, you'll need to specify a DNS name inside of the -hostname argument. The other thing you'll see from time to time is the TLS handshake errors or in general TLS errors. That's because you'll likely start being scanned by vulnerability scanners which try some common TLS vulnerabilities (none of which the server is affected by of course). Quote Link to comment Share on other sites More sharing options...
sweeper707 Posted October 4, 2018 Author Share Posted October 4, 2018 Thanks I actually tried hostname as well. I now realize you are not creating a self signed certificate but a lets encrypt and needed to allow http into the firewall. Quote Link to comment Share on other sites More sharing options...
Br@d Posted October 5, 2018 Share Posted October 5, 2018 I'm running into a similar issue but I also get some additional info... is there any documentation around the let's encrypt process? Quote Link to comment Share on other sites More sharing options...
sweeper707 Posted October 5, 2018 Author Share Posted October 5, 2018 (edited) 3 hours ago, Br@d said: I'm running into a similar issue but I also get some additional info... is there any documentation around the let's encrypt process? This is what I did but your is showing an i/o timeout issue. So make sure all the below is correct. Get a Public IP such as (64.15.17.23) for your server Get a public domain and point the dns record such as "cave.domain.com" to the IP 64.15.17.23 Allow the DNS propagation to take plus I usually wait around 24 hours as Let's Encrypt DNS seems to be delayed a bit Ensure your servers firewall inbound rules allow "http (80) and https (443)" run the server using the following syntax like ./c2_community64 -hostname="cave.domain.com" -https Edited: added last step #5. Edited October 5, 2018 by sweeper707 Quote Link to comment Share on other sites More sharing options...
Vulcan22 Posted December 1, 2019 Share Posted December 1, 2019 How do you get a public IP? (I am running it on a raspberry Pi, if you need to know that) Quote Link to comment Share on other sites More sharing options...
Irukandji Posted December 1, 2019 Share Posted December 1, 2019 (edited) This has been fixed.. Quote Change Log (2.1.0): General Update ACME LetsEncrypt generation to use the ACME2 standard. @Treebug842 Just google - what's my IP Edited December 1, 2019 by Jtyle6 what's my IP Quote Link to comment Share on other sites More sharing options...
df0cast Posted November 14, 2020 Share Posted November 14, 2020 Hello, Recently buy WIFI Pineapple and configure c2 cloud community im facing below issue, please assist how to fix it. ======================================================================================== root@srvDebian01:/home/dennis/tmp# ./c2-3.0.1_amd64_linux -hostname srvDebian01 -https [*] Initializing Hak5 Cloud C2 v3.0.1 [*] Hostname: srvDebian01 [*] DB Path: c2.db [*] First Start. Initializing... [*] Initial Setup Required - Setup token: XXX - XXX -XXXX 2020/11/14 00:12:09 http: TLS handshake error from 192.168.10.184:55758: acme/autocert: missing server name 2020/11/14 00:12:09 http: TLS handshake error from 192.168.10.184:55759: acme/autocert: missing server name 2020/11/14 00:12:10 http: TLS handshake error from 192.168.10.184:55763: acme/autocert: missing server name ========================================================================================= Quote Link to comment Share on other sites More sharing options...
chrizree Posted November 14, 2020 Share Posted November 14, 2020 Have you tried following this instruction? https://docs.hak5.org/hc/en-us/articles/360049664554-Cloud-C2-setup-with-self-signed-SSL-certificates Judging from your hostname, I guess it's locally hosted and not a public domain name which is needed if using the standard Let's Encrypt way of using certs 1 Quote Link to comment Share on other sites More sharing options...
df0cast Posted November 14, 2020 Share Posted November 14, 2020 Hi Chrizree, Thank you very much, I really really appreciate your response. Yes your correct I just tried to simulate/ install first on my local network first. Its fine if we can test on locally right? I will try your suggestion , thank again for that information. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.