WARN: Cannot handshake client www.amazon.com EOF help me out in this
this can be solved by using wildcard ssl on server side
i will already try with lets encrypt it does not helpful can you please guid me with steps
root@ubuntu-test:~# ll
total 15128
drwx------ 9 root root 4096 May 14 09:06 ./
drwxr-xr-x 23 root root 4096 Jul 12 10:23 ../
-rw------- 1 root root 2701 Jul 11 17:10 .bash_history
-rw-r–r-- 1 root root 3169 Apr 15 19:55 .bashrc
drwx------ 3 root root 4096 May 13 17:33 .cache/
drwx------ 3 root root 4096 Jul 12 11:36 .evilginx/
-rwxr-xr-x 1 root root 15430265 Apr 2 2024 evilginx*
-rw------- 1 root root 20 May 14 09:06 .lesshst
drwxr-xr-x 3 root root 4096 May 12 16:38 .local/
drwxr-xr-x 2 root root 4096 May 14 11:37 phishlets/
-rw-r–r-- 1 root root 161 Apr 22 2024 .profile
drwxr-xr-x 4 root root 4096 Jul 12 11:31 redirectors/
drwx------ 2 root root 4096 Jul 8 07:22 .ssh/
drwxr-x— 5 root root 4096 May 20 19:12 .vscode-server/
-rw-r–r-- 1 root root 218 May 20 17:57 .wget-hsts
Sir I didn’t get cert folder how I can resolve it
are u using my source ? it is in my source only .
Yes I m using your source so can you help me out brother how I can get cert folder
Sir please help me out in this
In my source code that folder is already there.
From where your using the source code? GitHub ?
Are you using source code from following package ?
Hi Fluxx,
Is this modified source already available for people who paid for you’re evilGinx course such as myself? Where can it be found if this is the case, within Telegram group chat?
( Also please verify my posts, they are pending rn ).
no its not part of the course .
its part of modified source package .