Page MenuHomePhabricator
Paste P12543

push notification - FCM endpoint post - 500 error
ActivePublic

Authored by Jgiannelos on Wed, Sep 9, 12:06 PM.
$ echo "{\"deviceTokens\":[\"__REPLACE_ME__\"],\"messageType\":\"checkEchoV1\",\"topic\":\"string\",\"dryRun\":false}" | http --verify no POST https://staging.svc.eqiad.wmnet:4104/v1/message/fcm
HTTP/1.1 500 Internal Server Error
access-control-allow-headers: accept, x-requested-with, content-type
access-control-allow-origin: *
access-control-expose-headers: etag
content-length: 438
content-security-policy: default-src 'self'; object-src 'none'; media-src *; img-src *; style-src *; frame-ancestors 'self'
content-type: application/json; charset=utf-8
date: Wed, 09 Sep 2020 12:03:01 GMT
server: main-tls
vary: Accept-Encoding
x-content-security-policy: default-src 'self'; object-src 'none'; media-src *; img-src *; style-src *; frame-ancestors 'self'
x-content-type-options: nosniff
x-envoy-upstream-service-time: 5182
x-frame-options: SAMEORIGIN
x-webkit-csp: default-src 'self'; object-src 'none'; media-src *; img-src *; style-src *; frame-ancestors 'self'
x-xss-protection: 1; mode=block
{
"detail": {
"code": "app/invalid-credential",
"message": "Credential implementation provided to initializeApp() via the \"credential\" property failed to fetch a valid Google OAuth2 access token with the following error: \"Error fetching access token: Error while making request: connect ETIMEDOUT 172.217.164.141:443.\"."
},
"method": "POST",
"status": 500,
"title": "Failed to send message to FCM",
"type": "fcm_send_failed",
"uri": "/v1/message/fcm"
}