• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • credentials-plugin
    • None
    • Jenkins version 2.89.3
      Credentials Plugin version 2.1.16

      When I try to add credentials for example login/password for docker registry, nothing happens and I get following error in console (domain name changed to example.com):

       Mixed Content: The page at 'https://example.com/job/dfo-pm-staging_backend_develop/configure' was loaded over HTTPS, but requested an insecure form action 'http://example.com/descriptor/com.cloudbees.plugins.credentials.Cred...ials.SystemCredentialsProvider$ProviderImpl/context/jenkins/addCredentials'. This request has been blocked; the content must be served over HTTPS.

      I can change form url to https instead of http using developer tools and then it submits correctly. How do I fix this issue?

          [JENKINS-50160] Can't add credentials through https

          sounds like your reverse proxy is not set up correctly.

          Stephen Connolly added a comment - sounds like your reverse proxy is not set up correctly.

          Anton Anonymous added a comment - stephenconnolly my nginx config    

          Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

          Stephen Connolly added a comment - Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

          Denys Digtiar added a comment -

          refruity The X-Forwarded-Proto is the header your reverse proxy also needs to set, as far as I know.

          Denys Digtiar added a comment - refruity The X-Forwarded-Proto is the header your reverse proxy also needs to set, as far as I know.

          Piotr Bladek added a comment -

          I ran into same problem, Im using jenkins behind apache2 https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache

          In my case solution was to setup following HTTPS proxy headers properly:

          RequestHeader set X-Forwarded-Proto "https"
          RequestHeader set X-Forwarded-Port "443"

           

          Piotr Bladek added a comment - I ran into same problem, Im using jenkins behind apache2  https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Apache In my case solution was to setup following HTTPS proxy headers properly: RequestHeader set X-Forwarded-Proto "https" RequestHeader set X-Forwarded-Port "443"  

            Unassigned Unassigned
            refruity Anton Anonymous
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: