# Api Zrok returns error 500

**URL:** <https://openziti.discourse.group/t/api-zrok-returns-error-500/2343>\
**Category:** Support\
**Created:** [March 25, 2024, 1:37pm UTC](https://openziti.discourse.group/t/api-zrok-returns-error-500/2343 "2024-03-25T13:37:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![taki-eddine](https://avatars.discourse-cdn.com/v4/letter/t/6bbea6/32.png) [@taki-eddine](https://openziti.discourse.group/u/taki-eddine)\
**Post date:** [March 25, 2024, 1:37pm UTC](https://openziti.discourse.group/t/api-zrok-returns-error-500/2343/1 "2024-03-25T13:37:30Z")

</div>

Hello, I'm getting error 500 when executing any `zrok` command.

```auto
2024-03-25 14:34:50 [0.497] INFO main.(*enableCommand).run: contacting the zrok service...
2024-03-25 14:35:13 [23.496] ERROR main.(*enableCommand).run: the zrok service returned an error: [POST /enable][500] enableInternalServerError 
2024-03-25 14:35:14 there was a problem enabling your environment!
2024-03-25 14:35:14 
2024-03-25 14:35:14 you are trying to use the zrok service at: https://api.zrok.io
2024-03-25 14:35:14 
2024-03-25 14:35:14 you can change your zrok service endpoint using this command:
2024-03-25 14:35:14 
2024-03-25 14:35:14 $ zrok config set apiEndpoint <newEndpoint>
2024-03-25 14:35:14 
2024-03-25 14:35:14 (where newEndpoint is something like: https://some.zrok.io)
2024-03-25 14:35:14 

```

```auto
2024-03-25 15:05:52 [ERROR]: unable to create share (unable to create share: [POST /share][500] shareInternalServerError)

```

---

<div class="post-metadata">

**Author:** ![TheLumberjack](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/thelumberjack/32/113_2.png) [@TheLumberjack](https://openziti.discourse.group/u/TheLumberjack)\
**Post date:** [March 25, 2024, 3:02pm UTC](https://openziti.discourse.group/t/api-zrok-returns-error-500/2343/2 "2024-03-25T15:02:22Z")

</div>

Hi @taki-eddine,

Yes, zrok had an incident at this time. You can keep up with and review past incidents at [https://status.zrok.io/](https://status.zrok.io/) With each incident we make zrok and OpenZiti stronger. Thanks for your patience!

---

<div class="post-metadata">

**Author:** ![taki-eddine](https://avatars.discourse-cdn.com/v4/letter/t/6bbea6/32.png) [@taki-eddine](https://openziti.discourse.group/u/taki-eddine)\
**Post date:** [March 25, 2024, 3:30pm UTC](https://openziti.discourse.group/t/api-zrok-returns-error-500/2343/3 "2024-03-25T15:30:41Z")

</div>

@TheLumberjack  
Thank you for your response, I checked the status page and I saw that the incident has been fixed, but still the problem persists:

```auto
2024-03-25 16:24:54 INFO: reading enable parameters from environment variables
2024-03-25 16:24:54 zrok configuration updated
2024-03-25 16:24:54 INFO: running: zrok enable ...
2024-03-25 16:25:06 there was a problem enabling your environment!
2024-03-25 16:25:06 
2024-03-25 16:25:06 you are trying to use the zrok service at: https://api.zrok.io
2024-03-25 16:25:06 
2024-03-25 16:25:06 you can change your zrok service endpoint using this command:
2024-03-25 16:25:06 
2024-03-25 16:25:06 $ zrok config set apiEndpoint <newEndpoint>
2024-03-25 16:25:06 
2024-03-25 16:25:06 (where newEndpoint is something like: https://some.zrok.io)
2024-03-25 16:25:06 
2024-03-25 16:24:54 [0.499] INFO main.(*enableCommand).run: contacting the zrok service...
2024-03-25 16:25:05 [11.006] ERROR main.(*enableCommand).run: the zrok service returned an error: [POST /enable][500] enableInternalServerError 

```

---

<div class="post-metadata">

**Author:** ![michael.quigley](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/michael.quigley/32/1123_2.png) [@michael.quigley](https://openziti.discourse.group/u/michael.quigley)\
**Post date:** [March 25, 2024, 3:34pm UTC](https://openziti.discourse.group/t/api-zrok-returns-error-500/2343/4 "2024-03-25T15:34:27Z")

</div>

There might still be issues underway. We're monitoring and will update the status page appropriately.

There is an improvement in the works that should eliminate the issue we're seeing. That _should_ get rolled out this week.