# Excon SSL Verify issue for ONEBOX

**URL:** <https://meta.discourse.org/t/excon-ssl-verify-issue-for-onebox/128747>\
**Category:** Self-hosting\
**Tags:** onebox\
**Created:** [9월 17, 2019, 2:31오전 UTC](https://meta.discourse.org/t/excon-ssl-verify-issue-for-onebox/128747 "2019-09-17T02:31:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [9월 17, 2019, 4:30오후 UTC](https://meta.discourse.org/t/excon-ssl-verify-issue-for-onebox/128747/3 "2019-09-17T16:30:15Z")

</div>

Looks like by default [excon bundles its own certificate bundle](https://github.com/excon/excon/issues/212) but since other people had similar issues, he’s added the ability to configure it in the environment? And it’ll use the system one if the certificate is in properly.

It might need the hash link to work. Can you try the following and see if it solves the problem?

- do both:
  - add your custom cert to `/etc/ssl/certs` _inside_ the container

  - add the hash link: e.g.

---

_[View the full topic](https://meta.discourse.org/t/excon-ssl-verify-issue-for-onebox/128747)._