Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSL certificate problem #1169

Open
mamun626 opened this issue Feb 12, 2025 · 8 comments
Open

SSL certificate problem #1169

mamun626 opened this issue Feb 12, 2025 · 8 comments

Comments

@mamun626
Copy link

i buy domain from namecheap.as a hostimg i am using digitalochean.
i set up everything with evilginix.
only problem is genareting SSL certificate from letsEncrypt.
so my qustion is if i buy SSL certificate from namecheap,becouse thay provide paid certificate.so it will work or not???please if any one know.

@AnisseHounaoui
Copy link

Can you share more details about the issue?

@mamun626
Copy link
Author

Image
Actually i am getting this error on evilginx2...so what will be soloution?if i buy SSL certificate it will be ok???

@AnisseHounaoui
Copy link

This problems I believe comes from misconfiguration in dns records. Did you setup evilginx nameservers in namecheap or did you rely on namecheap and added A records manually for each subdomain?

@mamun626
Copy link
Author

yes,i did setup evilginx name server on namecheap.i didn't do it by manual?

Image

@AnisseHounaoui
Copy link

Evilginx manages dns records for you. This is what you should do to fix the issue:

  1. Go to Advanced DNS -> Personal DNS Server ->Click Add nameserver, then add ns1 and ns2 with your evilginx IP :

Image

  1. After go to Domain ->Nameservers -> Custom DNS , and add ns1.<your_domain> and ns2.<your_domain>

Image

Then wait for around 12h and from time to time check if your records are propagated through all dns servers:

Image

nameserver should point to your evilginx server IP

@itsdayztar1
Copy link

Hello send dm to @itdayztar on telegram

@Kvngtheta
Copy link

Kvngtheta commented Feb 24, 2025

SOLUTION FOUND!!
generate your own certs using certbot
***this is great for testing or playing around if you are on a legit engagement self-signed certs might still get blocked

  1. Put your certificate and private key in: ~/.evilginx/crt/sites//
  • you might have to create the /crt/sites/<hostname/ directories
  1. Disable LetsEncrypt with: config autocert off

source: found this in the actual code

  • Feature: Added support to load custom TLS certificates from a public certificate file and a private key file stored in ~/.evilginx/crt/sites/<hostname>/. Will load fullchain.pem and privkey.pem pair or a combination of a .pem/.crt (public certificate) and a .key (private key) file. Make sure to run without -developer flag and disable autocert retrieval with config autocert off.
  • Feature: Added ability to disable automated TLS certificate retrieval from LetsEncrypt with config autocert <on/off>.

@mamun626
Copy link
Author

SSL certificate problem solve,but after running lures i am getting this,,,,

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants