1

I am facing an problem, Gcp PubSub not pushing message to my registered endpoint. Let me narrate in details the steps I have executed.

Note,

  1. I am not using app engine
  2. I am deploying my simple spring boot app on PCF (Pivotal Cloud Foundry...PaaS) hosted on GCP (IaaS)

Steps:

  1. 1st I have created an service account with required permission to access GCP PubSub
  2. Next am using this service account to create/subscribe/register my endpoint to the topic
  3. Next, as expected I have registered & verified my domain ownership & added my push endpoint path say https://example.com with GCP
  4. Deployed my app in Pcf

Test Executed:

  1. I am able to successfully create & subscribe the topic
  2. Successfully registered my push end point like https://example.com/myPushEp with the newly created topic
  3. Successfully able to post message to the topic.

As my push ep is registered with gcp pubsub topic so asa the message is posted it must be pushed into registered endpoint, but unfortunately it not pushing any message to the registered endpoint. I am completely clueless what is the mistake.

Can any one guide me where I am doing the mistakes. Its an simple spring boot rest application, do I am making any mistake in coding or any configuration.

Donald Duck
  • 8,409
  • 22
  • 75
  • 99
Indranil Bera
  • 11
  • 3

4 Answers4

1

I recommend you looking in Cloud Monitoring, you can use the push metrics, which start with the name "Push Request", to figure out if your messages are being pushed to your endpoint and if your endpoint is returning errors to Pub/Sub.

David Torres
  • 11
  • 1
  • please can you send a link? or explain exactly where to find it? i'm having hard time finding out why the posts dont arrive. – Mike Jul 22 '23 at 19:26
0

I faced the same problem and the funny turnout was that it was my server's fail2ban who banned google ip addresses.

yaugenka
  • 2,602
  • 2
  • 22
  • 41
0

One reason might be that the SSL Certificate of your push endpoint might be expired. It took me half a day to figure it out. Pubsub requires a working SSL certificate.

You can look up the type of errors in Google's stack monitoring. If it is a pubsub_interal_push error then most likely it is a certificate issue.

Usually, Google doesn't accept URLs without HTTPS but in my case - I had an HTTP URL. The certificate had an issue.

mohammed_ayaz
  • 620
  • 11
  • 16
0

also faced this (burned 4 hours on it) it was something broken in the firebase subdomain Redirecting to the actual function.. just gave it the orignal URL of the functions and it just worked... nothing in the google logs not even a line..

Mike
  • 741
  • 13
  • 40