PubSub endpoint not receiving payload data

[Alvie]

Hi

I am trying to implement the PubSub system and currently am just testing it out to see how it works.

I have created the fusio file in /etc/cron.d/ and created an event via the fusio app available in the marketplace.

I created the subscriptions to these events via the API:

{
	"event": "my_event",
	"endpoint": "https://webhook.site/02f0758f-3231-48d6-8441-3679657e4163"
}

They are successfully created, so I despatch an event when http://localhost/events receives a GET request. I tested this by making a call to the /events route, and it seems that the event is triggered as the table shows {"foo":"bar"} in the payload.

I then noticed the /etc/cron.d/fusio file was unpopulated so I tried again with giving www-data:www-data ownership of that file, and created event2, and redeployed but the cron file is still empty and whilst the event is triggered, the endpoints do not receive the payload data. Am I doing something incorrectly?

[chriskapp]

Hi, ok thanks for the info, so if you create an cronjob entry at the backend, does this trigger a write to the cronfile? Or could you also take a look at the fusio_cronjob table to see which entries are available. In general Fusio should write those entries to the cron file.

[Alvie]

Thanks for the response :) After making a cronjob entry with backend app, it does populate the /etc/cron.d/fusio file:

# Generated by Fusio on 2021-09-16 08:35:47
# Do not edit this file manually since Fusio will overwrite those
# entries on generation.

*/5 * * * * /usr/bin/php /home/path/to/fusio/bin/fusio cronjob 4
0 0 * * * /usr/bin/php /home/path/to/fusio/bin/fusio cronjob 3
* * * * * /usr/bin/php /home/path/to/fusio/bin/fusio cronjob 2
* * * * * /usr/bin/php /home/path/to/fusio/bin/fusio cronjob 1

Here are the contents of the table, though I'm unsure if the event dispatch is the same one as created earlier

[chriskapp]

Ok great :) ... and your endpoints are then also triggered as expected?

[Alvie]

Ok great :) ... and your endpoints are then also triggered as expected?

Hi Chris, thanks for the reply. Unfortunately the webhook.site I used to test with didn't get the callback. I'll try another endpoint tomorrow to see if I can get this to work.

The payload does appear in the events triggered table though, I'll try to use wireshark or something similar to see if anything is sent.

[Alvie]

Hi @chriskapp I have tried it again but the endpoints aren't triggered. The row does exist in the table as mentioned previously:

I tried using wireshark but couldn't find any relevant packets, or anything to the ip addresses of the endpoints, though it is possible that I used it incorrectly.