Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Landing pages loading extremely slow #373

Open
mcjon3z opened this issue Jan 17, 2018 · 1 comment
Open

Landing pages loading extremely slow #373

mcjon3z opened this issue Jan 17, 2018 · 1 comment

Comments

@mcjon3z
Copy link

mcjon3z commented Jan 17, 2018

Zeknox, this is really more of a solution rather than an ongoing problem - just wanted to put it in an issue here in case it may save somebody else a couple hours of beating their head into their desk.

The problem I was experiencing was that the campaign landing pages on an active campaign were loading very slow - 10-15 seconds of "waiting on page" before they would display. I noticed that if I did not specify the UID in the URL which prompts the rewrite to the 404 page, the pages loaded immediately. I started commenting out lines of PHP code that is inserted by PF and identified the callback line to the logging page was where everything was hanging up:
$result = file_get_contents($url, false, $context);

I also noted that the $url parameter is populated from the application site URL:
$url = "<%= GlobalSettings.first.site_url %>" . '/reports/results/';

The root of my issue is that I was using a public DNS alias (.com) for the application site URL in the global settings that was not resolvable by the PF server, so basically it was trying to call back to itself and could not resolve its own IP address. I was under the assumption that the application site URL needed to be resolvable by the victims for tracking images and such, but searching through the code all of the references to the site_url seem to be used internally or passed through via proxypass. I suppose the default value of https://phishingfrenzy.LOCAL should have tipped me off! I changed this value to the internal IP address of the PF server and now everything appears to be functioning properly.

May want to consider documenting the proper use of this variable in the setup instructions / config page as it will definitely break stuff if it is not configured properly. The "stats aren't tracking visitors" section of the getting started docs would leave me to believe that this URL should be externally accessible to the victims.

Let me know if I'm missing something glaring here!

@zeknox
Copy link
Member

zeknox commented Feb 8, 2018

I concur, we could add some additional verbiage on this topic in the Getting Started guide or maybe even the Troubleshooting guide for anyone else who runs into the issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants