405 Not Allowed with curl #3750

somera · 2024-05-26T19:24:47Z

somera
May 26, 2024

Hi,

I can upload an CycloneDX 1.5 XML-BOM in the DT UI. Fine.

But whet I try curl like here https://docs.dependencytrack.org/usage/cicd/ I get always: "405 Not Allowed".

I created a new team:

$ curl -X "POST" 'http://192.168.178.231:7070/api/v1/bom' \
        -H 'X-API-Key: odt_Bn9jVlc63HpRFGdxRVq2i1rjrLU9ZwI9' \
        -H 'Content-Type: multipart/form-data' \
        -F 'projectame=raspi_mail_service' \
        -F 'projectVersion=master' \
        -F 'parentName=raspi_mail_service' \
        -F 'autoCreate=true' \
        -F "bom=@raspi_mail_service-bom.xml"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 76137  100   157  100 75980  51866  23.9M --:--:-- --:--:-- --:--:-- 36.3M<html>
<head><title>405 Not Allowed</title></head>
<body>
<center><h1>405 Not Allowed</h1></center>
<hr><center>nginx/1.25.5</center>
</body>
</html>

I run v4.11.1 in Docker.

...
  dtrack-frontend:
    image: dependencytrack/frontend
    depends_on:
      - dtrack-apiserver
    environment:
      - TZ=Europe/Berlin
      - API_BASE_URL=http://192.168.178.231:7071
    volumes:
      - "/etc/timezone:/etc/timezone:ro"
      - "/etc/localtime:/etc/localtime:ro"
    ports:
      - "7070:8080"
    restart: unless-stopped

I don't know what is wrong.

somera · 2024-05-26T20:38:18Z

somera
May 26, 2024
Author

ok, I found that I should use the API_BASE_URL=http://192.168.178.231:7071/api/v1/bom

0 replies

somera · 2024-05-26T20:44:18Z

somera
May 26, 2024
Author

ok, this

curl -X "POST" "http://192.168.178.231:7071/api/v1/bom" \
     -H 'Content-Type: multipart/form-data' \
     -H 'X-Api-Key: odt_Bn9jVlc63HpRFGdxRVq2i1rjrLU9ZwI9' \
     -F "project=404b5350-658c-49f8-b6cb-816f4ab1e4ca" \
     -F "bom=@raspi_mail_service-bom.xml"

works for me.

3 replies

thawzinmyo Sep 19, 2024

Hello @somera , now, I installed
DT on AKS using Helm Chart. I set up with LoadBalancer Type for service. After installation, I can access both API and Frond End from Internet. But, when I try to login to Front End, I can't log it in. There is an error 405 (Not Allowed). I google it and read many blogs but they did not pointed out the solution. Could you share me if you have some solution? I setup apiBaseUrl. Let me share my Helm Chart for testing!! Actually, it's default Chart file. I just added toleration and apiBaseUrl config.

common:
  nameOverride: ""
  fullnameOverride: ""
  image:
    registry: docker.io
    pullSecrets: []
  secretKey:
    createSecret: false
    existingSecretName: ""
  serviceAccount:
    create: true
    annotations: {}
    name: ""
    automount: false

apiServer:
  deploymentType: StatefulSet
  annotations: {}
  image:
    registry: ''
    repository: dependencytrack/apiserver
    tag: ""
    pullPolicy: IfNotPresent
  command: []
  args: []
  resources:
    requests:
      cpu: "2"
      memory: 5Gi
    limits:
      cpu: "4"
      memory: 5Gi
  podSecurityContext:
    fsGroup: 1000
  securityContext:
    capabilities:
      drop:
      - ALL
    runAsNonRoot: false
    allowPrivilegeEscalation: true
    readOnlyRootFilesystem: true
    seccompProfile:
      type: RuntimeDefault
  persistentVolume:
    enabled: false
    className: ""
    size: 5Gi
  extraEnvFrom: []
  extraContainers: []
  extraEnv:
    - name: EXTRA_JAVA_OPTIONS
      value: "-Xmx2g"
    - name: SYSTEM_REQUIREMENT_CHECK_ENABLED
      value: "false"
  tolerations:
    - key: "internal"
      operator: "Equal"
      value: "true"
      effect: "NoSchedule"
  probes:
    liveness:
      failureThreshold: 3
      initialDelaySeconds: 10
      periodSeconds: 15
      successThreshold: 1
      timeoutSeconds: 5
    readiness:
      failureThreshold: 3
      initialDelaySeconds: 10
      periodSeconds: 15
      successThreshold: 1
      timeoutSeconds: 5
  additionalVolumeMounts: []
  additionalVolumes: []
  service:
    type: LoadBalancer
    nodePort: ~
    annotations: {}
  serviceMonitor:
    enabled: false
    namespace: monitoring
    scrapeInternal: 15s
    scrapeTimeout: 30s
  initContainers: []
  nodeSelector: {}

frontend:
  replicaCount: 1
  annotations: {}
  image:
    registry: ''
    repository: dependencytrack/frontend
    tag: ""
    pullPolicy: IfNotPresent
  command: []
  args: []
  resources:
    requests:
      cpu: 150m
      memory: 64Mi
    limits:
      cpu: 500m
      memory: 128Mi
  securityContext:
    capabilities:
      drop:
      - ALL
    runAsNonRoot: false
    allowPrivilegeEscalation: true
    readOnlyRootFilesystem: false
    seccompProfile:
      type: RuntimeDefault
  extraEnv: []
    - name: EXTRA_JAVA_OPTIONS
      value: "-Xmx2g"
    - name: SYSTEM_REQUIREMENT_CHECK_ENABLED
      value: "false"
    - name: API_BASE_URL
      value: "http://my_public_ip:8080"
  extraEnvFrom: []
  extraContainers: []
  tolerations:
    - key: "internal"
      operator: "Equal"
      value: "true"
      effect: "NoSchedule"
  probes:
    liveness:
      failureThreshold: 3
      initialDelaySeconds: 5
      periodSeconds: 15
      successThreshold: 1
      timeoutSeconds: 5
    readiness:
      failureThreshold: 3
      initialDelaySeconds: 5
      periodSeconds: 15
      successThreshold: 1
      timeoutSeconds: 5
  additionalVolumeMounts: []
  additionalVolumes: []
  service:
    type: LoadBalancer
    nodePort: ~
    annotations: {}
  apiBaseUrl: "my_public_ip:8080"
  initContainers: []
  nodeSelector: {}

ingress:
  enabled: false
  annotations: {}
  hostname: "example.com"
  ingressClassName: ""
  tls: []
extraObjects: []

nscuro Sep 19, 2024
Maintainer

@thawzinmyo Please use code blocks when posting code snippets.

From your config:

apiBaseUrl: "my_public_ip:8080"

You need to make sure that this points to the public URL of your API server endpoint. You can verify whether you have the correct URL by opening my_public_ip:8080/api/version in your browser. It should return JSON with details about the API server. If you're not getting that, you're using the wrong URL.

thawzinmyo Sep 19, 2024

@nscuro , According to your answer, I tried to change the correct IP, actually, I have been configured many times with the correct IP but this time, I delete the Pod and Replica create it again. This time now, success! So, I think that I need to restart that Pod to effect! Now, it's working. Thank you so much.

Solution:

Insert valid IP or Hostname in values.yaml of Helm (Check API Server URL my_public_ip:8080/api/version)
After updating, restart or delete the API Pod.

thawzinmyo · 2024-10-25T03:31:06Z

thawzinmyo
Oct 25, 2024

Hello @nscuro , in previous ways, I configured api as a LoadBalancer type which referenced in FrontEnd apiBaseUrl. All worked. But, now, I am configuring DT behind Nginx Ingress Controller and I exposed as SSL and also configured api as a CLusterIP type. Can I use ClusterIP type for API? If I use ClusterIP, in FrontEnd config, how can I referenced apiBaseUrl? But, now, I configured api as service with SSL and I referenced it as DNS path? But, 405 Method Not Allowed issue appears again. I can't also call dtrack.example.com/api/version.

1 reply

thawzinmyo Oct 25, 2024

Now, I can solve it. My AKS's pod that are running behind Ingress Controller exposed as external service with SSL certificate. We need to do both API and FrontEnd with SSL, in my case, I did not expose for API Server So, I faced "Must be HTTPS", "405 Method Not Allowed" issue. So, I decided to expose and configured SSL behind Ingress Controller. After that, I can LogIn to DT. Thanks. In the config of API Helm Values, we need to configure apiBaseUrl: "https://domain.com" which is API Server URL expose as LoadBalancer for my scenario. Test with this API call after you configured https. https://youdoamin.com/api/version always.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

405 Not Allowed with curl #3750

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 3 comments 4 replies

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

405 Not Allowed with curl #3750

somera May 26, 2024

Replies: 3 comments · 4 replies

somera May 26, 2024 Author

somera May 26, 2024 Author

thawzinmyo Sep 19, 2024

nscuro Sep 19, 2024 Maintainer

thawzinmyo Sep 19, 2024

thawzinmyo Oct 25, 2024

thawzinmyo Oct 25, 2024

somera
May 26, 2024

Replies: 3 comments 4 replies

somera
May 26, 2024
Author

somera
May 26, 2024
Author

nscuro Sep 19, 2024
Maintainer

thawzinmyo
Oct 25, 2024