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

SEC_ERROR_BAD_DER on argo instannce #277

Closed
chmouel opened this issue Feb 14, 2022 · 4 comments · Fixed by argoproj-labs/argocd-operator#582
Closed

SEC_ERROR_BAD_DER on argo instannce #277

chmouel opened this issue Feb 14, 2022 · 4 comments · Fixed by argoproj-labs/argocd-operator#582

Comments

@chmouel
Copy link

chmouel commented Feb 14, 2022

Describe the bug

I have installed Openshift Gitops Operator following the procedure from :

https://docs.openshift.com/container-platform/4.9/cicd/gitops/installing-openshift-gitops.html

when trying to get to the argos instance I am getting this firefox ssl error :

An error occurred during a connection to openshift-gitops-server-openshift-gitops.apps.paac.devcluster.openshift.com. security library: improperly formatted DER-encoded message.

Error code: SEC_ERROR_BAD_DER

my openshift router has a letsencrypt certificate on it and properly encrypted, it seems that argos route doesn't reuse it ?

image

tried with firefox97 and with safari 15.3

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

image

Additional context
Add any other context about the problem here.

@vrutkovs
Copy link

Same error here due to some odd self-signed cert. Chrome lets me bypass the error

@valumar
Copy link

valumar commented Feb 18, 2022

The same for OpenShift version 4.8.26 and Red Hat OpenShift GitOps 1.4.1

@vrutkovs
Copy link

Workaround:

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
spec:
  server:
    route:
      tls:
        insecureEdgeTerminationPolicy: Redirect
        termination: reencrypt

@mbaldessari
Copy link

I suspect that by default we should let haproxy/router be in charge of encryption (it would work with letsencrypt certificates and it is fundamentally haproxy's job to deal with certs). So switching the route default to reencrypt just makes more sense I think.

To track why firefox changed behaviour (it happened first with FF94) I opened https://bugzilla.redhat.com/show_bug.cgi?id=2058661

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants