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: Error 500 when creating a "Periodic Scan" or "Cloaked Scan" #1322

Closed
1 task done
gabrielss4ntos opened this issue Jul 22, 2024 · 4 comments · Fixed by #1328
Closed
1 task done

bug: Error 500 when creating a "Periodic Scan" or "Cloaked Scan" #1322

gabrielss4ntos opened this issue Jul 22, 2024 · 4 comments · Fixed by #1328
Assignees
Labels
bug Something isn't working release/2.1.2

Comments

@gabrielss4ntos
Copy link

gabrielss4ntos commented Jul 22, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

I'm trying to set up timed and periodic scans for a target. However, I receive error 500 and cannot create. Any suggestions on how to get workaround this?
error_scheduling
error-creating-scheduling

I even enabled debugging, but I can't understand the problem, see screenshots.

Server side logs

web-1 | django.request | Internal Server Error: /scan/bugbounty/schedule/organization/4
web-1 | Traceback (most recent call last):
web-1 | File "/usr/local/lib/python3.10/dist-packages/django/core/handlers/exception.py", line 47, in inner
web-1 | response = get_response(request)
web-1 | File "/usr/local/lib/python3.10/dist-packages/django/core/handlers/base.py", line 181, in _get_response
web-1 | response = wrapped_callback(request, *callback_args, **callback_kwargs)
web-1 | File "/usr/local/lib/python3.10/dist-packages/rolepermissions/decorators.py", line 21, in wrapper
web-1 | return dispatch(request, *args, **kwargs)
web-1 | File "/usr/src/app/startScan/views.py", line 800, in schedule_organization_scan
web-1 | return HttpResponseRedirect(reverse('scheduled_scan_view', kwargs={'slug': slug, 'id': id}))
web-1 | File "/usr/local/lib/python3.10/dist-packages/django/urls/base.py", line 86, in reverse
web-1 | return resolver._reverse_with_prefix(view, prefix, *args, **kwargs)
web-1 | File "/usr/local/lib/python3.10/dist-packages/django/urls/resolvers.py", line 698, in reverse_with_prefix
web-1 | raise NoReverseMatch(msg)
web-1 | django.urls.exceptions.NoReverseMatch: Reverse for 'scheduled_scan_view' with keyword arguments '{'slug': 'bugbounty', 'id': 4}' not found. 1 pattern(s) tried: ['scan/(?P[-a-zA-Z0-9
]+)/scheduled/\Z']
web-1 | django.server | "POST /scan/bugbounty/schedule/organization/4 HTTP/1.0" 500 96254
proxy-1 | 172.30.15.206 - - [22/Jul/2024:21:15:05 +0000] "POST /scan/bugbounty/schedule/organization/4 HTTP/1.1" 500 96254 "https://localhost/scan/bugbounty/schedule/organization/4" "Mozilla/5.0

Expected Behavior

Be able to create periodic scans.

Steps To Reproduce

Try creating a "Periodic Scan" or "Cloaked Scan".

Environment

- reNgine:2.1.1
- OS: Ubuntu 22.04.3 LTS
- Python: 3.10.12
- Docker Engine: 25.0.4
- Docker Compose: 1.29.2
- Browser: Chrome 126.0.6478.183

Anything else?

No response

@gabrielss4ntos gabrielss4ntos added the bug Something isn't working label Jul 22, 2024
Copy link
Contributor

👋 Hi @gabrielss4ntos,
Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki
For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

@luca-regne
Copy link

+1

1 similar comment
@cerontrustly
Copy link

+1

@yogeshojha
Copy link
Owner

Hi @luca-regne @gabrielss4ntos @cerontrustly

Thank you guys for reporting, looks like a typo. I have fixed in above MR. Once pipeline passes I will merge this.

Feel free to git pull

Thanks ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release/2.1.2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants