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

Can't access URL on SSL - This site can't be reached #405

Open
zjmc10 opened this issue May 31, 2019 · 1 comment
Open

Can't access URL on SSL - This site can't be reached #405

zjmc10 opened this issue May 31, 2019 · 1 comment
Labels

Comments

@zjmc10
Copy link

zjmc10 commented May 31, 2019

I can run campaigns successfully without SSL. When doing a test with SSL it fails with message this site can't be reached (after clicking the link in the phishing email).

I have application site url as http://domain.info.

Within the campaign I have phishing URL set as https://o365.domain.info and FQDN set as o365.domain.info.

Apart from that I've entered the three SSL files into the email settings page.

I've included copy of apachectl -S below:

VirtualHost configuration:
*:443 o365.domain.info (/etc/apache2/sites-enabled/20.conf:13)
*:80 is a NameVirtualHost
default server o365.domain.info (/etc/apache2/sites-enabled/20.conf:1)
port 80 namevhost o365.domain.info (/etc/apache2/sites-enabled/20.conf:1)
alias o365.domain.info
port 80 namevhost domain.info (/etc/apache2/sites-enabled/pf.conf:1)
ServerRoot: "/etc/apache2"
Main DocumentRoot: "/var/www/html"
Main ErrorLog: "/var/log/apache2/error.log"
Mutex ssl-cache: using_defaults
Mutex default: dir="/var/run/apache2/" mechanism=default
Mutex mpm-accept: using_defaults
Mutex watchdog-callback: using_defaults
Mutex ssl-stapling-refresh: using_defaults
Mutex ssl-stapling: using_defaults
Mutex proxy: using_defaults
PidFile: "/var/run/apache2/apache2.pid"
Define: DUMP_VHOSTS
Define: DUMP_RUN_CFG
User: name="www-data" id=33 not_used
Group: name="www-data" id=33 not_used

Any ideas on things to check would be greatly appreciated. Thanks!

@zeknox
Copy link
Member

zeknox commented May 31, 2019

Not quite sure what is causing this specific issue, but I would start to review some of the Apache logs as you hit the phishing site to see what type of errors get displayed if any. Tail the logs located at /var/logs/apache2/* and see if they yield any insight.

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

No branches or pull requests

2 participants