Jump to content

Evilginx2 Help ASAP


Divina

Recommended Posts

Hi,

I have a registered domain, which is hosted on ubuntu server. It has a valid certificate and is accessible.

I installed evilginx2 on that machine as well, but came to know it produces a port conflict (both web server and evilginx2 use port 443), so the setup is problematic.

Upon the evilginx2 command - 'phishlets enable okta' - I was able to successfully generate a certificate.

 

However, trying to operate evilginx2 on a different server (Debian), due to the ports conflict issue, -when evilginx2 tries to generate a certificate, it produces the following errors:

acme: Error -> One or more domains had a problem:
[example.mydomain.com] acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: <ip_address>: Invalid response from http://example.mydomain.com/.well-known/acme-challenge/bivLYVcw77MxEYT4YVRuraLD84wqS9zhDPWNYZ6EACM: 404, url:
[login.mydomain.com] acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: <ip_address>: Invalid response from http://login.mydomain.com/.well-known/acme-challenge/2vRb0_BMD1U2UOt9xjPHaMOV10mE3_dcuuBBZVg2wV0: 404, url:
[mydomain.com] acme: error: 403 :: urn:ietf:params:acme:error:unauthorized :: <ip_address>: Invalid response from https://mydomain.com/.well-known/acme-challenge/6I8p_RSElaMSL8l2Rf_5iigGCJJzTbMFPiKrD8D-MUI: 404, url:

 

Why cert generation works on the server holding the domain, but fails on the debian machine with evilginx?

 

any advice would help!

 

Link to comment
Share on other sites

From what I can see, using domain based authentication, it will only give the certificate to the server that is pointed at by the domain, so your Debian box isn't allowed the certificate as it can't show it owns the domain.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

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