# 403 Error 7 request per second

**URL:** <https://openziti.discourse.group/t/403-error-7-request-per-second/3446>\
**Category:** zrok\
**Created:** [November 19, 2024, 5:17pm UTC](https://openziti.discourse.group/t/403-error-7-request-per-second/3446 "2024-11-19T17:17:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jveliz-08](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/jveliz-08/32/2755_2.png) [@jveliz-08](https://openziti.discourse.group/u/jveliz-08)\
**Post date:** [November 19, 2024, 5:17pm UTC](https://openziti.discourse.group/t/403-error-7-request-per-second/3446/1 "2024-11-19T17:17:46Z")

</div>

Hi Everyone! im running a little app with a self-hosted instance of zrok, (i am using a reserved share).  
but every once in a while y get the 403 error and it blocks me for a couple of minutes.  
is there a way to override this config?  
i will appreciate any advice.  
Edit:  
i'm Aware that if i exceeed the 7 requests per second limit for over 5 minutes i will get this error, i was wondering if there's a way to bypass that.

---

<div class="post-metadata">

**Author:** ![mguthrie88](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/mguthrie88/32/151_2.png) [@mguthrie88](https://openziti.discourse.group/u/mguthrie88)\
**Post date:** [November 19, 2024, 6:11pm UTC](https://openziti.discourse.group/t/403-error-7-request-per-second/3446/2 "2024-11-19T18:11:37Z")

</div>

Hi @jveliz-08 - there isn't a way to bypass that with a public share, however a private share does not go through the public frontend and is not subject to rate limiting.

---

<div class="post-metadata">

**Author:** ![jveliz-08](https://yyz2.discourse-cdn.com/free1/user_avatar/openziti.discourse.group/jveliz-08/32/2755_2.png) [@jveliz-08](https://openziti.discourse.group/u/jveliz-08)\
**Post date:** [November 20, 2024, 12:14pm UTC](https://openziti.discourse.group/t/403-error-7-request-per-second/3446/3 "2024-11-20T12:14:38Z")

</div>

oh that's interesting, thank you so much for the response!
