# Native search function fails with 403 error

**URL:** <https://forum.ghost.org/t/native-search-function-fails-with-403-error/37071>\
**Category:** Developer help\
**Created:** [March 15, 2023, 6:28am UTC](https://forum.ghost.org/t/native-search-function-fails-with-403-error/37071 "2023-03-15T06:28:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![razvanilin](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/razvanilin/32/12024_2.png) [@razvanilin](https://forum.ghost.org/u/razvanilin)\
**Post date:** [March 15, 2023, 6:28am UTC](https://forum.ghost.org/t/native-search-function-fails-with-403-error/37071/1 "2023-03-15T06:28:29Z")

</div>

Hey everyone,

I just upgraded my theme and site to the latest version (5.38.0) and tried to use the native search function, but it didn’t work.

- How was Ghost installed and configured?

Ghost was installed and updated using the CLI tool

- What Node version, database, OS & browser are you using?

Node: v14.20.1  
OS: Ubuntu 22.04  
Latest chrome

- What errors or information do you see in the console?

```auto
403 error

content-api.js:199 Uncaught (in promise) NoPermissionError: Authorization failed
    at content-api.js:199:37

```

- What steps could someone else take to reproduce the issue you’re having?

Open [Chartbrew blog - Visualizing data in one place](https://chartbrew.com/blog/) click on the main search box and the error appears in the console. Nothing happens when typing something in the search box.

Did anyone encounter this before?

---

<div class="post-metadata">

**Author:** ![razvanilin](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/razvanilin/32/12024_2.png) [@razvanilin](https://forum.ghost.org/u/razvanilin)\
**Post date:** [March 16, 2023, 4:57am UTC](https://forum.ghost.org/t/native-search-function-fails-with-403-error/37071/2 "2023-03-16T04:57:06Z")

</div>

After a long while trying to find the issue, the problem was that I am using Cloudflare workers to make the blog work on a subdirectory. It seems that the API integrations can only be called from the original URL.

I changed my worker’s code to revert the call from my subdirectory to the original subdomain URL where ghost is running from. All good now 👍
