Hey team, this is Tommy from Culture Amp and we ar...
# pact-broker
t
Hey team, this is Tommy from Culture Amp and we are using pactflow. I got the ssl error as the screenshot when I tried to publish a pact while @Viet Anh Tran ran the same command I send to him and it’s working on his laptop. Does anyone have some ideas?
t
For pactflow support try #CLS16AVEE - but generally - • Do you have a VPN? • Do you have custom SSL certificates (and are they set correctly on your machine?)
✅ 1
m
This is almost certainly a client language problem. What client are you using?
t
Yeah, the vpn is a compulsory one - netskope. Every one at culture amp is using it. I dont think I have a custom SSL certificates… I am going to ask in #CLS16AVEE
m
I don’t think it’s a PactFlow issue. Our certs are standard public issue
v
What client are you using?
we are just using
pactfoundation/pact-cli:latest
docker image
m
This smells of corporate proxy that is intercepting your requests and breaking the certificate chain
t
Ah anyway, we can talk in here. 😅 as so many people here now
😆 1
v
hmm I am also working at the same company as Tommy but not getting this error thinking2
m
Can you please add the verbose flag and share the results? This will help us see what is going on.
b
You should be able to set the SSL_CERT_FILE or SSL_CERT_DIR environment variables to provide it with the correct certificate.
m
They shouldn’t need to do that Beth, because it’s a PactFlow account. I suspect corporate proxy, so they should just need to skirt around it
I published this yesterday, hopefully it helps 👇 (howtossl)
🙌🏼 1
s
v
Hey team, thanks for your comments. We have checked with security and it is one of the security apps blocking it
m
Not surprising, glad you got to the bottom of it! (and thanks for letting us know)
👍 1