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? [A dark-themed software interface displays installation details, a positive update status with a smiley face, advisory messages regarding failed email jobs, and a refresh option with a recent check timestamp. (Captioned by AI)]

[imagen] 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?

Which port do you currently use? [imagen]Proposed changes to discourse-setup because Digital Ocean blocks outbound smtp 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.

Hi, Originally, I tested this port, 2525, as well, from the recommendation of ./discourse-doctor to test the mailing side.

Was it always 2525, or did you just change it? If you changed it, did you destroy and start the container (or do a rebuild)? If you go to /admin/email/server-settings can you send a test message?

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. [imagen] pfaffman: /admin/email/server-settings In here it comes up as Error “ERROR - execution expired”

[imagen] 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.

Ver los trabajos fallidos en Sidekiq. (MailGun) fallando al enviar correos electrónicos

Soporte del producto

Moin 8 Julio, 2025 15:27 2

¿Qué puerto utilizas actualmente?

Tema		Respuestas	Vistas
ERROR - execution expired Product Support	5	364	29 Marzo 2025
DigitalOcean blocking SMTP and forcing SendGrid usage Product Support email	11	4147	17 Abril 2025
Digital Ocean blocking Port 587 Product Support	1	706	31 Marzo 2025
Emails are no longer being sent to users Product Support email	5	243	7 Agosto 2025
Any alternative way to connect to email service then SMTP (on Digital Ocean) Product Support email	6	553	18 Abril 2025

Ver los trabajos fallidos en Sidekiq. (MailGun) fallando al enviar correos electrónicos

Temas relacionados