API is throwing 404 errors

[lmno (Ross M.)]

@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:

   curl -X GET "https://redactedurl.com/admin/users/list/active.json" -H "Api-Key: LIVEPRODKEYHERE" -H "Api-Username: system"
   

   The response (with sensitive data redacted for confidentiality) is as follows:

   [
     {
       "id": 1,
       "username": "User1",
       "name": "Redacted",
       "avatar_template": "/user_avatar/yourforum.com/user1/{size}/avatar.png",
       "active": true,
       "admin": true,
       "moderator": true,
       "trust_level": 4,
       "title": "Recognized Member",
       "days_visited": 6,
       "post_count": 3
     },
     {
       "id": 19,
       "username": "User2",
       "name": "Redacted",
       "avatar_template": "/letter_avatar_proxy/v4/letter/j/{size}.png",
       "active": true,
       "admin": false,
       "moderator": false,
       "trust_level": 1,
       "title": "Member (Unverified)"
     },
     {
       "id": 3,
       "username": "User3",
       "name": "Redacted",
       "avatar_template": "/user_avatar/yourforum.com/user3/{size}/avatar.png",
       "active": true,
       "admin": true,
       "moderator": true,
       "trust_level": 4,
       "title": "Community Founder"
     },
     {
       "id": -1,
       "username": "system",
       "name": "system",
       "avatar_template": "/user_avatar/yourforum.com/system/{size}/avatar.png",
       "active": true,
       "admin": true,
       "moderator": true,
       "trust_level": 4,
       "title": "Bot"
     }
   ]
   

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.:

   {
     "id": 15,
     "username": "User15",
     "active": true,
     "admin": false,
     "moderator": false,
     "trust_level": 0,
     "days_visited": 1,
     "post_count": 0,
     "can_send_activation_email": true,
     "can_activate": false,
     "can_deactivate": true,
     "can_grant_admin": true,
     "can_grant_moderation": true,
     "can_impersonate": true,
     "groups": [
       {
         "name": "trust_level_0",
         "bio_excerpt": "New members with limited abilities"
       }
     ]
   }
   

3. 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.