search

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.94k stars 1.97k forks source link

[HELP] failed to obtain certificates #205

Closed nonuser33 closed 5 years ago

nonuser33 commented 5 years ago

Hello!, I installed Evilginx2 from precompiled binary package. I added the nameservers (ns1 & ns2) and I have this error when I try 'phishlets enable instagram'

It's hosted on NameCheap.com (VPS + domain)

screen shot 2019-02-09 at 17 02 00

: phishlets enable instagram [20:01:35] [inf] enabled phishlet 'instagram' [20:01:35] [inf] setting up certificates for phishlet 'instagram'... [20:01:35] [war] failed to load certificate files for phishlet 'instagram', domain 'instagram.serverdata.website': open /root/.evilginx/crt/instagram.serverdata.website/instagram.crt: no such file or directory [20:01:35] [inf] requesting SSL/TLS certificates from LetsEncrypt... [20:01:39] [err] [www.instagram.serverdata.website] acme: Error 403 - urn:acme:error:unauthorized - Invalid response from http://www.instagram.serverdata.website/.well-known/acme-challenge/6Kjefk_OSZ1oSk58J4GN7-UjWuQzt41UPVvD-6De3j0: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n\n404 Not Found\n\n

Not Found

\n<p" Error Detail: Validation for www.instagram.serverdata.website:80 Resolved to: 199.193.6.158 Used: 199.193.6.158

[20:01:39] [err] [m.instagram.serverdata.website] acme: Error 403 - urn:acme:error:unauthorized - Invalid response from http://m.instagram.serverdata.website/.well-known/acme-challenge/ot5--vr5gIuz9IwgX-SXss3QaMvRLY8KMycDEbrkmtw: "<!DOCTYPE HTML PUBLIC \"-//IETF//DTD HTML 2.0//EN\">\n\n404 Not Found\n\n

Not Found

\n<p" Error Detail: Validation for m.instagram.serverdata.website:80 Resolved to: 199.193.6.158 Used: 199.193.6.158

[20:01:39] [!!!] failed to obtain certificates [20:01:39] [inf] disabled phishlet 'instagram'

nonuser33 commented 5 years ago

...

HackerTutor commented 5 years ago

Try with a different domain, maybe let's encrypt doesn't recognize .website as a TLD

nonuser33 commented 5 years ago

Try with a different domain, maybe let's encrypt doesn't recognize .website as a TLD

But that have no sense

arfben commented 5 years ago

@nonuser33 i have the same issue @kgretzky do u have a solution

nonuser33 commented 5 years ago

@kgretzky

nonuser33 commented 5 years ago

@nonuser33 i have the same issue @kgretzky do u have a solution

kgretzky does not give a solution, so use this alternative https://github.com/drk1wi/Modlishka It's better and 0 problems

jepunband commented 5 years ago

hmm.. no solution

HackerTutor commented 5 years ago

Try another server from different provider first, and try with a regular .com domain on both. Make sure you're using the latest version of golang.

nonuser33 commented 5 years ago

Try another server from different provider first, and try with a regular .com domain on both. Make sure you're using the latest version of golang.

That have no sense dude, stop

HackerTutor commented 5 years ago

What doesn't make sense?

On Tue, Feb 12, 2019, 2:44 PM nonuser33 notifications@github.com wrote:

Try another server from different provider first, and try with a regular .com domain on both. Make sure you're using the latest version of golang.

That have no sense dude, stop

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kgretzky/evilginx2/issues/205#issuecomment-462968731, or mute the thread https://github.com/notifications/unsubscribe-auth/AsKFeVNrNP9W5fHhhY-K25w6mc9n_EG5ks5vM0PggaJpZM4ayt0r .

nonuser33 commented 5 years ago

What doesn't make sense? … On Tue, Feb 12, 2019, 2:44 PM nonuser33 @.***> wrote: Try another server from different provider first, and try with a regular .com domain on both. Make sure you're using the latest version of golang. That have no sense dude, stop — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#205 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AsKFeVNrNP9W5fHhhY-K25w6mc9n_EG5ks5vM0PggaJpZM4ayt0r .

It doesn't matter if the domain is .com

HackerTutor commented 5 years ago

It could for let's encrypt.

On Tue, Feb 12, 2019, 4:15 PM nonuser33 notifications@github.com wrote:

What doesn't make sense? … <#m-4102132837596503944> On Tue, Feb 12, 2019, 2:44 PM nonuser33 @.***> wrote: Try another server from different provider first, and try with a regular .com domain on both. Make sure you're using the latest version of golang. That have no sense dude, stop — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#205 (comment) https://github.com/kgretzky/evilginx2/issues/205#issuecomment-462968731>, or mute the thread https://github.com/notifications/unsubscribe-auth/AsKFeVNrNP9W5fHhhY-K25w6mc9n_EG5ks5vM0PggaJpZM4ayt0r .

It doesn't matter if the domain is .com

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kgretzky/evilginx2/issues/205#issuecomment-462998530, or mute the thread https://github.com/notifications/unsubscribe-auth/AsKFeTgDqyUDg0eXNLNjKqPNQnAdOPoDks5vM1kNgaJpZM4ayt0r .

kgretzky commented 5 years ago

The issue is incorrect setup. Please read the blog before posting issues like this. The "solution" was there from the beginning.

I made a special FAQ entry for you in case you don't want to use Google: https://github.com/kgretzky/evilginx2/wiki/FAQ

nonuser33 commented 5 years ago

The issue is incorrect setup. Please read the blog before posting issues like this. The "solution" was there from the beginning.

I made a special FAQ entry for you in case you don't want to use Google: https://github.com/kgretzky/evilginx2/wiki/FAQ

I did that dude and I had that error

kgretzky commented 5 years ago

Read the error you posted again, there is clearly some other website running on the address you posted...

nonuser33 commented 5 years ago

Read the error you posted again, there is clearly some other website running on the address you posted...

Port 80 is closed I bought VPS + Domain on NameCheap and I added the nameservers (ns1 and ns2) with the IP of the vps

morenikejiolawaletimothy commented 5 years ago

Port 80 is closed I bought VPS + Domain on NameCheap and I added the nameservers (ns1 and ns2) with the IP of the vps

yes i'm facing this same problem now

0xArch3r commented 2 years ago

I had the same issue, another application was listening on port 80... Fixed that and it started up just fine!

jvolker1 commented 1 year ago

I had the same issue, another application was listening on port 80... Fixed that and it started up just fine!

How did you fix it?

sono9ine commented 1 year ago

I had the same issue, another application was listening on port 80... Fixed that and it started up just fine!

How did you fix it?

Hi, you can use "netstat -tunlp" to see which app is already listening on port 80, then kill it with it's PID, using "kill {PID}"