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

After integrating DefectDojo with Jira, all pages in DefectDojo become inaccessible following a Docker Compose restart. #11606

Open
1 of 3 tasks
NguyenVanHung24 opened this issue Jan 21, 2025 · 1 comment
Labels

Comments

@NguyenVanHung24
Copy link

Slack us first!
The easiest and fastest way to help you is via Slack. There's a free and easy signup to join our #defectdojo channel in the OWASP Slack workspace: Get Access.
If you're confident you've found a bug, or are allergic to Slack, you can submit an issue anyway.

Bug description
I can't access to defectdojo, it alaway change path to my jira url

Steps to reproduce
Steps to reproduce the behavior:
1 Run defect dojo in local host:
2 Make it public by using ngrok
3 Config it and intergrate with defectdojo
4 After turn off docker compose and restart
5 Can not access to defectdojo

Deployment method (select with an X)

  • Docker Compose
  • Kubernetes
  • GoDojo

Environment information

  • Operating System: [WSL Ubuntu 22.01]
  • DefectDojo version:2.40.0

Logs
Use docker compose logs (or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).

Screenshots
If applicable, add screenshots to help explain your problem.

Image

Image

@mtesauro
Copy link
Contributor

I'm not sure what's going on with your DefectDojo + ngrok setup but the address bar in the screenshots looks like a large part of the problem. It seems like it's 2 URLs concatenated into a single URL which would result in the 404 page you're seeing.

I suspect there's something wrong with how ngrok is setup. I'd suggest calling the URL with something like curl -k -v so that you can inspect the HTTP you're getting from your setup. There's probably a 302/Redirect that's ending up in the 404 in your screenshots.

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