# Allowing custom certificates in okteto cli

**URL:** <https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828>\
**Category:** Help\
**Created:** [May 21, 2023, 2:09pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828 "2023-05-21T14:09:12Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![harley84](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/harley84/32/378_2.png) [@harley84](https://community.okteto.com/u/harley84)\
**Post date:** [May 21, 2023, 2:09pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/1 "2023-05-21T14:09:12Z")

</div>

Hi, I’m going over Getting Started on Okteto Cloud with PHP tutorial and getting the “certificate signed by unknown authority” error when running “okteto init”. I believe it’s related to the custom zscaler CA that our company defines.  
How can I have okteto cli to trust custom CA?  
Thanks in advance

> ➜ php-getting-started git:(main) okteto init  
> i Using … @ [cloud.okteto.com](http://cloud.okteto.com) as context  
> ✓ Okteto manifest (okteto.yml) deploy and build configured successfully  
> ? Do you want to launch your development environment? [Y/n]: y  
> i Building ‘Dockerfile’ in tcp://buildkit.cloud.okteto.net:443…  
> [+] Building 0.0s (0/0)  
> x Error building service ‘hello-world’: error building image ‘[registry.cloud.okteto.net/.../php-hello-world:1.0.0](http://registry.cloud.okteto.net/.../php-hello-world:1.0.0)’: build failed: failed to dial gRPC: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: x509: certificate signed by unknown authority”

---

<div class="post-metadata">

**Author:** ![jona](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/jona/32/353_2.png) [@jona](https://community.okteto.com/u/jona)\
**Post date:** [May 22, 2023, 1:21pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/2 "2023-05-22T13:21:07Z")

</div>

Hello! Thank you for reaching out. With the release of **CLI 2.17** expected on **June 21st** , we are adding the feature for Okteto CLI to be able to use system trusted CAs.

---

<div class="post-metadata">

**Author:** ![harley84](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/harley84/32/378_2.png) [@harley84](https://community.okteto.com/u/harley84)\
**Post date:** [May 22, 2023, 1:59pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/3 "2023-05-22T13:59:25Z")

</div>

Thanks @jona  
Is there any workaround in the meanwhile? June 21st is a long time from now and it prevents us from evaluating the tool

---

<div class="post-metadata">

**Author:** ![harley84](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/harley84/32/378_2.png) [@harley84](https://community.okteto.com/u/harley84)\
**Post date:** [May 22, 2023, 2:16pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/4 "2023-05-22T14:16:50Z")

</div>

Maybe there’s a beta version we can try that has it fixed?

---

<div class="post-metadata">

**Author:** ![jona](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/jona/32/353_2.png) [@jona](https://community.okteto.com/u/jona)\
**Post date:** [May 22, 2023, 3:10pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/5 "2023-05-22T15:10:22Z")

</div>

I am currently talking with the team internally to see what are the best options as a workaround and will update you soon. Thank you!

---

<div class="post-metadata">

**Author:** ![jona](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/jona/32/353_2.png) [@jona](https://community.okteto.com/u/jona)\
**Post date:** [May 22, 2023, 5:41pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/6 "2023-05-22T17:41:40Z")

</div>

Hello, you will be able to make use of this feature by using out Dev Release Channel as explained here: [okteto/RELEASE.md at master · okteto/okteto · GitHub](https://github.com/okteto/okteto/blob/master/docs/RELEASE.md#release-channels)

The feature was merged into our master branch today and will be released at 4am UTC and should be available starting tomorrow. Please let us know if you need additional help or if you have other questions, thank you!

---

<div class="post-metadata">

**Author:** ![jona](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/jona/32/353_2.png) [@jona](https://community.okteto.com/u/jona)\
**Post date:** [May 22, 2023, 6:34pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/7 "2023-05-22T18:34:57Z")

</div>

Actually, we were able to manually publish the feature in our Dev channel so if you would like to try before tomorrow you should be able to do so. Let us know if you run into any issues!

```auto
export OKTETO_CHANNEL=dev
curl https://get.okteto.com -sSfL | sh

```

---

<div class="post-metadata">

**Author:** ![harley84](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/harley84/32/378_2.png) [@harley84](https://community.okteto.com/u/harley84)\
**Post date:** [June 26, 2023, 2:02pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/8 "2023-06-26T14:02:46Z")

</div>

Hi @jona ,  
Sorry for resurrecting this thread but seems like the problem is still there and the workaround no longer works, can you please check?

```auto

➜ php-getting-started git:(main) okteto version
okteto version 2.16.3 
➜ php-getting-started git:(main) okteto version update
 ✓ The latest okteto version is already installed
➜ php-getting-started git:(main) okteto deploy --build
 i Using harley84 @ cloud.okteto.com as context
..
[+] Building 0.0s (0/0)                                                                                                                                           
 x Error building service 'hello-world-dev': error building image 'registry.cloud.okteto.net/harley84/php-getting-started-hello-world-dev:okteto': build failed: failed to dial gRPC: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority"

➜ ~ export OKTETO_CHANNEL=dev
curl https://get.okteto.com -sSfL | sh

> Using Release Channel: dev
> Using Version: 2.16.4-beta.1
> Downloading .../2.16.4-beta.1/okteto-Darwin-arm64
  % Total % Received % Xferd Average Speed Time Time Time Current
                                 Dload Upload Total Spent Left Speed
100 74.9M 100 74.9M 0 0 9068k 0 0:00:08 0:00:08 --:--:-- 14.9M
> Installing /usr/local/bin/okteto
> Okteto successfully installed!
➜ ~ okteto deploy --build    
 i Using harley84 @ cloud.okteto.com as context
 x Couldn't detect any manifest (okteto manifest, pipeline, compose, helm chart, k8s manifest)
➜ ~ cd ~/Desktop/okteto/php-getting-started 
➜ php-getting-started git:(main) okteto deploy --build                  
 i Using harley84 @ cloud.okteto.com as context
 i Building 'Dockerfile' in...
[+] Building 0.0s (0/0)                                                                                                                                                                                                                       
 x Error building service 'hello-world': error building image 'registry.cloud.okteto.net/harley84/php-hello-world:1.0.0': build failed: failed to get status: rpc error: code = Unavailable desc = connection error: desc = "transport: authentication handshake failed: x509: certificate signed by unknown authority"
➜ php-getting-started git:(main) okteto version  
okteto version 2.16.4-beta.1 

```

---

<div class="post-metadata">

**Author:** ![andreafalzetti](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/andreafalzetti/32/456_2.png) [@andreafalzetti](https://community.okteto.com/u/andreafalzetti)\
**Post date:** [June 27, 2023, 11:58am UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/9 "2023-06-27T11:58:16Z")

</div>

Hi @harley84,

from the logs shared I can see you have tried using `2.16.3` which still does not include the fix - which will make it into the `2.17.0` release.

You correctly tried to use the `dev` channel again, however yesterday we created a new beta release for `2.16.4` which ends up in the same release channel (dev). That version doesn’t include the fix you need.

As the time I am posting this, if you try again downloading the `dev` channel again, you should get the latest build from the master branch which includes the fix you need.

However, because we don’t know when you will see and try this, and we might create new beta releases in the meantime, I would suggest downloading a specific build, equivalent to the current latest dev build: `ebe5d55`

You can download this binary, directly using these links, depending on your OS:

- Darwin-x86\_64: [https://downloads.okteto.com/cli/dev/ebe5d55/okteto-Darwin-x86\_64](https://downloads.okteto.com/cli/dev/ebe5d55/okteto-Darwin-x86_64)
- Darwin-arm64: [https://downloads.okteto.com/cli/dev/ebe5d55/okteto-Darwin-arm64](https://downloads.okteto.com/cli/dev/ebe5d55/okteto-Darwin-arm64)

If you use Linux, just use the suffix: “okteto-Linux-x86\_64”

I hope this helps. Don’t hesitate to reach out again if you experience any issue.

Andrea

---

<div class="post-metadata">

**Author:** ![andreafalzetti](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/andreafalzetti/32/456_2.png) [@andreafalzetti](https://community.okteto.com/u/andreafalzetti)\
**Post date:** [July 5, 2023, 1:18pm UTC](https://community.okteto.com/t/allowing-custom-certificates-in-okteto-cli/828/10 "2023-07-05T13:18:09Z")

</div>

Hi @harley84,

The Okteto CLI `2.17.0` has been released today, if you want to update, just run:

`curl https://get.okteto.com -sSfL | sh `

or

`brew upgrade okteto`

Let us know how it goes!

Andrea
