Bekijk de mislukte taken in Sidekiq. (MailGun) die er niet in slagen e-mails te verzenden

[Aaron_Walsh]

Evening all,

I haven’t really been using my forum, either as an end user or an admin, but I noticed it was a bit quiet. All of a sudden, when looking at the admin panel, I have 42 email jobs, and reading using Gemini, it is related to the provider (Mailgun) not being synced with the provider (DigitalOcean console) through the app.yml. I haven’t changed anything and can’t find anything on this forum about whether we needed to change anything on our side.

Username and now password are correct; other than that, there isn’t much else with the SMTP I can change. The port is also correct, and when I say “now” password, I’ve also changed this.

None of these have been changed since 2022, so what could it be?

[Moin]

Which port do you currently use?

@pfaffman

The issue with port 587 being blocked is a digital ocean issue. I’ve had several clients who just stopped being able to send mail because digital ocean started blocking the port without warning. It’s a trivial fix to switch to port 2525, though.

[Aaron_Walsh]

Hallo,

Oorspronkelijk heb ik deze poort, 2525, ook getest, op aanbeveling van ./discourse-doctor om de e-mailkant te testen.

[pfaffman (Jay Pfaffman)]

Was het altijd 2525, of heb je het net veranderd?

Als je het hebt veranderd, heb je de container dan vernietigd en opnieuw gestart (of een rebuild gedaan)?

Als je naar /admin/email/server-settings gaat, kun je dan een testbericht sturen?

[Aaron_Walsh]

No, always been 587 until about 2 hours ago and been this since 2022.

Once I change them in the container I’ve been rebuilding.

@pfaffman

/admin/email/server-settings

In here it comes up as Error “ERROR - execution expired”

[pfaffman (Jay Pfaffman)]

@Aaron_Walsh

In here it comes up as Error “ERROR - execution expired”

That sounds like it’s still getting blocked. Are you sure that you changed it to 2525? And when you rebuilt it built and started a new container?

[Aaron_Walsh]

@pfaffman

That sounds like it’s still getting blocked. Are you sure that you changed it to 2525? And when you rebuilt it built and started a new container?

So I’ve done this:

cd /var/discourse
./launcher destroy app
./launcher start app

And now it works. I do apologize. I see the original topic was back in 2017 and lasted this long, which is good going. Hopefully, this will fix it going forward.