Hi all, Banging my head against an inexplicable (to me) problem which has arisen when moving off sandbox mailgun SMTP to a new domain. A few hours ago I switched the URL setting in app.yml to the new domain, and install is working fine. Then I moved to email settings and changed necessary settings…

Some questions: Did you complete a ./launcher rebuild app after both app.yml changes? Are you seeing any other issues? Errors in /logs, browser console, etc? Have you verified that your app.yml is valid? http://www.yamllint.com/ Please upload (or copy paste in) your app.yml making sure to remove …

Thanks, Joshua. Here’s a link to the forum: http://caldata.net In answer to your questions: Yes, ./launcher rebuild after all app.yml changes No errors in logs but browser console is reporting “Failed to load resource: the server responded with a status of 502 (Bad Gateway)”. However, this seems…

I’m not seeing anything jump out at me from the app.yml. _Off Topic: when pasting in code, it is helpful to surround it with 3 back ticks. Reference: http://commonmark.org/help/tutorial/07-code.html_ The only thing I haven’t seen before is SEGMENT_IO_KEY. I’m assuming that’s related to this plugi…

Thanks, Joshua. For the code pasting tip, and the response. Yep, that’s a plugin for Segment.io , and the mail settings were working when I was using Mailgun’s sandbox SMTP settings and had that same plugin installed. I can try commenting that out of app.yml and see what happens, but m y guess is th…

@jomaxro FYI, I’m commented out the Segment.io plugin (and all custom plugins) and am still seeing the same error on the email settings page in admin.

I’ve also now tried going back to Mailgun sandbox SMTP settings and creating a Sparkpost account and using those SMTP settings. Still only seeing the “arguments -i” line in the email settings admin page. I’m totally confused. Anyone have any ideas on what else I can try?

The issue is because of this line ## Plugins go here env: SEGMENT_IO_KEY: XXXXXXX You are redefining the “env” key (which is defined earlier) and thus all of the “DISCOURSE_” settings are gone… To fix it, you need to move the “SEGMENT_IO_KEY” under the “#DISCOURSE_CDN_URL” line, like so env: …

@zogstrip Thank you! That did it. I saw the extra “env” statement there, but didn’t stop to think it would redeclare all environment variables. Thanks again, it’s a relief to see my SMTP settings back :slight_smile:

No email settings, only "Arguments -i"

Product Support

jomaxro (Joshua Rosenfeld) Fevereiro 26, 2017, 11:07pm 8

We’ve now surpassed my email knowledge, sorry! Perhaps @zogstrip might have a thought or two, he does a lot of email related development.

Tópico		Respostas	Visualizações
Allow update smtp settings in admin panel Feature email	5	2933	27 de Abril de 2017
Troubleshoot email on a new Discourse install Self-Hosting email , configuring , how-to	36	185405	27 de Abril de 2026
Email doesn't work after fresh install Self-hosting docker , email	11	4448	29 de Janeiro de 2016
Rebuild problem Product Support	11	1870	23 de Abril de 2016
SMTP Settings Missing After Install Self-hosting email	6	327	31 de Janeiro de 2026

No email settings, only "Arguments -i"

Tópicos relacionados