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

This site can’t be reached172.xxxxxxxx took too long to respond. #2511

Open
NyamumboC opened this issue Jun 23, 2022 · 5 comments
Open

This site can’t be reached172.xxxxxxxx took too long to respond. #2511

NyamumboC opened this issue Jun 23, 2022 · 5 comments

Comments

@NyamumboC
Copy link

NyamumboC commented Jun 23, 2022

Thanks for reaching out! We're happy to help resolve issues as quickly as possible.

Please use this template when creating a new issue. If you do not follow this template format, your issue may be closed without comment.

Before filing a new issue, please use the search bar at the top of the browser to search for similar issues. Also, please make sure you have read our documentation, which covers how to use Gophish.

What version of Gophish are you using?:

V.0.11.0
Brief description of the issue:

When using AWS VPS IP to launch I get - This site can’t be reached 172.xxxx took too long to respond.

What are you expecting to see happen? :

Gophish landing page.
What are you seeing happen?

Site took too long to respond.
If this question is related to email templates or landing pages not working as expected, please provide your template or landing page below:

Insert code here

Please provide any terminal output that may be relevant below:

"admin_server": {
                "listen_url": "0.0.0.0:3331",
                "use_tls": true,
                "cert_path": "gophish_admin.crt",
                "key_path": "gophish_admin.key"
        },
        "phish_server": {
                "listen_url": "0.0.0.0:80",
                "use_tls": false,
                "cert_path": "example.crt",
                "key_path": "example.key"
        },
        "db_name": "sqlite3",
        "db_path": "gophish.db",
        "migrations_prefix": "db/db_",
        "contact_address": "",
        "logging": {
                "filename": "",
                "level": ""
![Screenshot 09](https://user-images.githubusercontent.com/90630395/175260260-8bc74a30-b7b6-4ca4-a580-c8f954aaf260.jpg)

Insert output here

Screenshot 09

Please provide as many steps as you can to reproduce the problem:

  • Step 1 -
  • So when i use 127.0.0.0 it opens well but it fails when using the VPS IP. What could be the issue?
  • Step 2 -
@NyamumboC
Copy link
Author

NyamumboC commented Jun 23, 2022

Does anyone know what might be causing this issue? I'm using AWS Ubuntu VPS and running this on Ubuntu using the free code camp tutorial

@rzmpzgeviii
Copy link

rzmpzgeviii commented Jun 25, 2022

according to ur config file is ur listening server on "0.0.0.0:80" so make sure to use "0.0.0.0:80" when creating a test campaing.

This will only be working locally on ur computer so test it by googling http://0.0.0.0:80 and if it works u should see a "404 error" that means it works.

@glennzw
Copy link
Collaborator

glennzw commented Jun 25, 2022

@rzmpzgeviii is spot on. Make sure: (i) you're hitting port 80 on your VPS and (ii) firewall/acl rules are setup to allow port 80 inbound.

@NyamumboC
Copy link
Author

NyamumboC commented Jun 26, 2022

Hi, thank you for your reply. Unfortunately, when I google http://0.0.0.0:80 I get 'this site can't be reached.'. I only get a 404 page not found when I http://myamazonubuntuvps.

@glennzw
Copy link
Collaborator

glennzw commented Jun 26, 2022

Yup sounds like you need to add some AWS rules to allow inbound port 80:

https://aws.amazon.com/premiumsupport/knowledge-center/connect-http-https-ec2/

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

No branches or pull requests

3 participants