mcgurksean

Results 4 comments of mcgurksean

Any update on this issue, guys? I am having a similar issue pulling from `registry-name.artifactory.company-name.com` where I get the error message: `certificate is valid for *.company-name.com, company-name.com, not registry-name.artifactory.company-name.com` So,...

BTW, I think that I have solved this by amending the server_name part of the nginx configuration to: `server_name ~(?.+)\.artifactory.company-name.com artifactory.company-name.com ~(?.+)\-artifactory.company-name.com; `

@thomsonac Did you get this to work? I am getting the same error message when I run my job where the job itself is executed on another node.

N.B. This is the case when you choose the 'push' command from here: ![377fb48a-30bc-4d2a-a35e-5203b6507aa8](https://github.com/jfrog/jfrog-azure-devops-extension/assets/1913745/8d9595c3-69e9-437e-9f88-bab1c624e1cf) When this command is chosen, the ability to add additional arguments is not available.