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

[BUG] ... #5859

Open
1 task done
meetgyn opened this issue Nov 27, 2024 · 1 comment
Open
1 task done

[BUG] ... #5859

meetgyn opened this issue Nov 27, 2024 · 1 comment
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@meetgyn
Copy link

meetgyn commented Nov 27, 2024

Is there an existing issue for this?

  • I have searched the existing issues.

Current Behavior

Version v3.3.6 is not working. I tested it on several Linux distributions like Kali, Parrot, and Debian, and it is giving the same response. However, version v2.9.3 is working perfectly. What changed in Nuclei?

Expected Behavior

Version ok v2.9.3
Image

Version v3.3.6
Image
I used the same target in both versions.

Steps To Reproduce

Nuclei -u https://xxxx.com.br
and I also tested it as follows:

nuclei -u https://wwww.com.br -t /root/nuclei-templates
No matter how I execute it, I only get the same results. The latest version of Nuclei is not working, and I need to understand why.

Relevant log output

Environment

- OS: Parrot 6.2 and Kali linux 2023-2
- Nuclei: v3.3.6 and v2.9.3
- Go: go version go1.22.9 linux/amd64 in Parrot
- Go: go version go1.21.5 linux/amd64 in kali linux

Anything else?

No response

@meetgyn meetgyn added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Nov 27, 2024
@nf-works
Copy link

nf-works commented Dec 19, 2024

From your second screenshot:

[INF] Targets loaded for current scan: 1
[INF] Skipped ... from target list as found unresponsive 30 times

If you only have one target and it is being skipped, it surely will not find anything.
Try increasing the timeout and/or max host errors and check if you can connect to the website when the error occurs.

This would also be a duplicate to #5234. Try this: #5234 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

No branches or pull requests

2 participants