# API is throwing 404 errors

**URL:** <https://meta.discourse.org/t/api-is-throwing-404-errors/335647>\
**Category:** Product Support\
**Created:** [November 11, 2024, 7:17pm UTC](https://meta.discourse.org/t/api-is-throwing-404-errors/335647 "2024-11-11T19:17:33Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![lmno](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lmno/32/463544_2.png) [@lmno](https://meta.discourse.org/u/lmno)\
**Post date:** [November 11, 2024, 8:06pm UTC](https://meta.discourse.org/t/api-is-throwing-404-errors/335647/3 "2024-11-11T20:06:59Z")

</div>

> [@supermathie](#):
>
> - validate the API key  
> does Discourse show a valid user authentication (`x-discourse-username`) when making a simple GET with that key?
> - validate the user ID  
> it _really_ exists, right? it’ll 404 if it doesn’t
> - are you behind Cloudflare?  
> it can mess with parameters

1. **API Key Validation**  
The API key was confirmed to be valid using the following command:

2. **User Existence Confirmation**  
The test user (ID: 15) was verified to exist, as demonstrated by querying the user’s data using `/admin/users/15/suspend.json`.:

 ![image](https://global.discourse-cdn.com/meta/original/4X/a/8/c/a8c481fcd8b1e5986528266b1a5a35e25fde0054.png)

1. **Network Configuration**  
The site is not utilizing Cloudflare. Instead, it operates behind an NGINX reverse proxy. The application listens on port `8080` internally, with NGINX handling SSL termination on port `443` for external access. The `app.yml` configuration does not bind directly to port `443`, as SSL and certificate management are handled by NGINX to ensure secure connectivity and availability.

---

_[View the full topic](https://meta.discourse.org/t/api-is-throwing-404-errors/335647)._