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

[Tool run error] Crtsh: Failed to connect to the database server: dial tcp 91.199.212.48:5432: connect: connection refused #154

Closed
s7x opened this issue Apr 29, 2019 · 15 comments

Comments

Projects
None yet
7 participants
@s7x
Copy link
Collaborator

commented Apr 29, 2019

Hi there!

After running a scan with a huge wordlist (dns-jhaddix.txt), I encounter this error when trying to launch another one:

Crtsh: Failed to connect to the database server: dial tcp 91.199.212.48:5432: connect: connection refused

Version used: version 2.9.9

Cheers!

@caffix

This comment has been minimized.

Copy link
Member

commented Apr 29, 2019

Looks like they blocked you

@jaikishantulswani

This comment has been minimized.

Copy link

commented Apr 29, 2019

@caffix I am also getting the same
Crtsh: Failed to connect to the database server: dial tcp 91.199.212.48:5432: connect: connection refused

@caffix

This comment has been minimized.

Copy link
Member

commented Apr 29, 2019

It's possible to push your luck with any of the data sources. I am making one improvement to the situation thanks to @s7x

caffix added a commit to caffix/OWASP-Amass that referenced this issue Apr 29, 2019

OWASP#154 data source that fail to start are removed from the enum
Co-authored-by: s7x <s7x@users.noreply.github.com>
@tja

This comment has been minimized.

Copy link

commented Apr 29, 2019

The same is happening to me. From several IPs, many of which I never used for recon before. I would assume the crt.sh server is having general issues.

@dhauenstein

This comment has been minimized.

Copy link
Collaborator

commented Apr 29, 2019

Maybe a fallback to web scraping makes sense when the db is down. IIRC crtsh db access is not planned to be very stable, so a fallback may be a good solution.

@m4xx101

This comment has been minimized.

Copy link

commented Apr 30, 2019

Getting this same error, does any one has explanation why is this happening.?

Crtsh: Failed to connect to the database server: dial tcp 91.199.212.48:5432: connect: connection refused

Here is the snap

Screenshot from 2019-04-30 23-40-07

@s7x

This comment has been minimized.

Copy link
Collaborator Author

commented Apr 30, 2019

Hi everyone. For now, until the release of the fix, you can still run the tool using the sources.

  • First do amass -list to get all the source names
  • amass -d [domain] -include [all sources except Crtsh]

Cheers!

@dhauenstein

This comment has been minimized.

Copy link
Collaborator

commented Apr 30, 2019

Or simply use -exclude crtsh :)

@m4xx101

This comment has been minimized.

Copy link

commented Apr 30, 2019

@s7x

This comment has been minimized.

Copy link
Collaborator Author

commented Apr 30, 2019

@dhauenstein Even better! Thanks for the tip!

@Teicu

This comment has been minimized.

Copy link

commented May 1, 2019

hi

same error here

Crtsh: Failed to connect to the database server: dial tcp 91.199.212.48:5432: connect: connection refused

@caffix

This comment has been minimized.

Copy link
Member

commented May 2, 2019

See if you're still experiencing this issue in version 2.9.10

@dhauenstein

This comment has been minimized.

Copy link
Collaborator

commented May 2, 2019

Please note: crt.sh seems to have some issues right now. The DB is not working, and it seems the website (now that every tool is scraping instead of using the DB) is not responding correctly all the time either. Hope they get this fixed soon, crt.sh is a valuable source for DNS recon..

@Teicu

This comment has been minimized.

Copy link

commented May 2, 2019

See if you're still experiencing this issue in version 2.9.10

works fine now, thank you. No more errors

Cheers

@s7x

This comment has been minimized.

Copy link
Collaborator Author

commented May 9, 2019

Working fine now. Closing the issue. Thanks everyone for your help & tests!

@s7x s7x closed this May 9, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.