> ## Documentation Index
> Fetch the complete documentation index at: https://moengage-doc-2298-s2s-type-case-sensitive.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Are Push Campaigns Resulting in an INVALID_SERVER_CREDS Error?

> Fix the INVALID_SERVER_CREDS error in MoEngage push campaigns by verifying your FCM sender ID, server key, and Private key file configuration.

## Problem

In Push campaigns, under campaign failures breakdown, the following error is displayed:

INVALID\_SERVER\_CREDS

<img src="https://mintcdn.com/moengage-doc-2298-s2s-type-case-sensitive/y8lY5d9Gmh9QL4HC/images/moengage_ea004e.png?fit=max&auto=format&n=y8lY5d9Gmh9QL4HC&q=85&s=5fb31f37e9680ebf248c2ec1ec29a108" alt="" width="506" height="198" data-path="images/moengage_ea004e.png" />

## Solution

* You are receiving the "INVALID\_SERVER\_CREDS" error because the sender ID and server key provided may belong to different GCM or FCM projects.
* To resolve this issue, use the configured sender ID and server key.
* Ensure that you have the accurate FCM keys (or certificate) in your Push settings and include the ServiceKey.json file instead of the google-services.json file (if you have added it).
* Verify the **Private key file (Recommended)** on the MoEngage dashboard.
  * Open the private key JSON file using any text editor.
  * Check that the *project\_id* mentioned in the JSON file matches the Firebase Project ID.
  * If you already have a private key on the Service Accounts page, you need not generate a new one.
    <img src="https://mintcdn.com/moengage-doc-2298-s2s-type-case-sensitive/ci8Djcf_YLqDkdsJ/images/moengage_77d443.png?fit=max&auto=format&n=ci8Djcf_YLqDkdsJ&q=85&s=e5c4a46d36e82504c35d8ece5573186b" width="1600" height="417" data-path="images/moengage_77d443.png" />
    <Info>
      In FCM projects, the sender ID can be found in the google-services.json file.
    </Info>