# Using ssl with TagoCore

**URL:** <https://community.tago.io/t/using-ssl-with-tagocore/1198>\
**Category:** TagoCore\
**Created:** [July 20, 2022, 12:52pm UTC](https://community.tago.io/t/using-ssl-with-tagocore/1198 "2022-07-20T12:52:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![benjie](https://avatars.discourse-cdn.com/v4/letter/b/eb8c5e/32.png) [@benjie](https://community.tago.io/u/benjie)\
**Post date:** [July 20, 2022, 12:52pm UTC](https://community.tago.io/t/using-ssl-with-tagocore/1198/1 "2022-07-20T12:52:58Z")

</div>

Hi,

I’ve installed tagocore on a server, and am now trying to apply ssl to it. I’m using an nginx reverse proxy to redirect port 443 to tagocore’s port which I have set using the --port option.

However, when trying to integrate with [tago.io](http://tago.io), it now tries to use port 8999 with https, which does not work, as the port is expecting plain http connections. I can’t use an nginx reverse proxy because the port is reserved by tagocore. Is there any way for me to change the port of the [tago.io](http://tago.io) integration so I can use a reverse proxy, or somehow get tagocore to use ssl it’s self?

Thanks

---

<div class="post-metadata">

**Author:** ![benachio](https://avatars.discourse-cdn.com/v4/letter/b/ecae2f/32.png) [@benachio](https://community.tago.io/u/benachio)\
**Post date:** [July 25, 2022, 12:06pm UTC](https://community.tago.io/t/using-ssl-with-tagocore/1198/2 "2022-07-25T12:06:52Z")

</div>

Hey Benjie,

Currently the port 8999 is static and we don’t have a configuration parameter for it.

Now that I think about it, other errors can come from this. For instance, if the port is already being used by another application, TagoIO integration will not be able to start the server when TagoCore starts.

I’ll talk with the team to try and figure out a way to change this port configuration. I’ll keep you posted.