I run 2 Discourse instances: a standard one (Docker) a dev one, behind a nginx proxy I’ve set up the same webhook on both instances. It works well from the standard instance, but not from the dev instance: the Ping button never gets a response and stays gray, although the corresponding POST event seems to appear in the nginx log (EDIT: this log entry is about the click event localhost->Discourse, not the outgoing webhook ping message). I see no error in the Discourse server console or nginx logs. What should I check?

You might need to set a pointer in /etc/hosts to 127.0.0.1 (or your public IP, depending on where your nginx is listening) for your dev host.

Thanks @hellekin. My nginx routes requests from www.myhostname.org to 127.0.0.1:3000. So I’ve tried to add 127.0.0.1 www.myhostname.org to my host file, but it hasn’t solved the problem…

I don’t see anything pertaining to the webhook call neither in nginx nor Discourse logs. However, I do see the webhook call in Sidekiq “Enqueued” list. The entry stays there forever. Any idea why Sidekiq never processes the job? P.S.: because I could curl to my webhook service from the Discourse server, I believe nginx is not involved in the issue. I’m going to change the topic’s title to reflect that.

Using Firefox or Chromium, do you have network logs? I’m sorry I can’t help you much, as I didn’t look into web hooks so far.

It’s solved now. The problem was about Sidekiq not processing jobs. I did a lot of things (updating Discourse, flushing redis, restarting Sidekiq, changing database.yml then restoring it, rebooting the server) and now it works. Thanks again @hellekin!

It was too good to be true. Here is what I do on my dev instance: Create a webhook Use the Ping button: it works (I can trace it all the way up to my webhook service) Create a post: this adds 4 jobs in Sidekiq (2 x “event_name”=>“user_updated” and 2 x “event_name”=>“post_created”). But those jobs stays in the Busy list and aren’t processed. If I keep triggering events, they add up to the busy list. Somewhere along the way, even Ping events get stuck. At that point, I need to flush Redis and restart Sidekiq if I want to go back to point 2. If I do the same on my Docker instance, it works like a charm. I also want to mention that, in my admin Dashboard (on the dev instance), I have the following warning: “A check for updates has not been performed. Ensure sidekiq is running.”

Stuck jobs in development mode are a known problem with Sidekiq and Rails 5.1 It’s probably because of missing dependencies. See the following post for more information on that. [image] When should Discourse upgrade to Rails 5? Development Rails 5.1 is merged into Discourse. One notable change which was a source of pain in development for me is that Sidekiq supports live reloading with Rails 5 but dependencies in each file has to be required properly. Otherwise, the job will be stucked in the Sidekiq queue. I’ve fixed most that I can find but if you run into any other job, feel free to let me know. Feel free to send a pull request if you find missing dependencies in sidekiq jobs. Unfortunately the ProcessPost job can’t be fixed that way. We are aware of the problem… As a workaround you can change config.eager_load to true in development.rb

Thanks a lot @gerhard, setting config.eager_load to true seemed to solve the issue. EDIT: I could work for 2 hours without any problem, then the issue came back…

Webhooks/Sidekiq issue on dev instance

Development

jack2 October 1, 2017, 3:12pm 2

My nginx is set up according to @riking’s excellent post.

Topic		Replies	Views
Sidekiq is unexpectedly paused Development	15	1508	February 21, 2019
"Ensure sidekiq is running." when it is definitely running Self-hosting	18	8229	October 2, 2015
My Discourse Jobs are stuck in queue. Not able to find solution Product Support	5	219	October 15, 2025
Sidekiq has a lot of errors and queued jobs Product Support	18	1583	March 1, 2024
"Sidekiq is not running" Self-hosting	6	3202	February 7, 2016

Webhooks/Sidekiq issue on dev instance

Related topics