kgretzky / evilginx2

Standalone man-in-the-middle attack framework used for phishing login credentials along with session cookies, allowing for the bypass of 2-factor authentication
BSD 3-Clause "New" or "Revised" License
10.72k stars 1.94k forks source link

Cannot handshake client mail.x.com write tcp 172.21.x.x:443->61.149.x.x:10031: write: connection reset by peer #893

Open UIWP0 opened 1 year ago

UIWP0 commented 1 year ago

image

WARN: Cannot handshake client mail.x.com write tcp 172.21.1.1:443->61.149.1.1:10032: write: connection reset by peer Cannot handshake client mail.x.com tls: client using inappropriate protocol fallback

UIWP0 commented 1 year ago

My certificate generated using Let's Encrypt

UIWP0 commented 1 year ago

image I m so sad....

HiredHaxor commented 1 year ago

You have not set NAMESERVERS first...

UIWP0 commented 1 year ago

What do you mean by this? I set up a dns at godaddy.com txt. If you could please explain a little more. Thank you very much.

HiredHaxor commented 1 year ago

What do you mean by this? I set up a dns at godaddy.com txt. If you could please explain a little more. Thank you very much.

@EvilDeadOfficial TELEGRAM I will help you..

UIWP0 commented 1 year ago

What do you mean by this? I set up a dns at godaddy.com txt. If you could please explain a little more. Thank you very much.

@EvilDeadOfficial TELEGRAM I will help you..

OK

thec0nci3rge commented 1 year ago

For anyone hoping to get a real answer instead of a telegram invite.

If you are playing around locally, ensure to use the "-developer" switch when starting evilginx:

./evilginx -developer -p <path/to/phishlets>

jessslay commented 6 months ago

Doesnt take much research to find out what nameserver is. if u cant figure that out maybe this isnt for you