I've been beating my head against this for two days, but I cannot seem to get my Huginn instance to send emails via Mailgun SMTP. Does anyone have any advice?
Whenever I attempt a dry run with my Email Agent, it takes about 30 seconds to process before I get an
execution expired error.
Here is my
.env with my SMTP configuration:
RAILS_ENV=production SMTP_DOMAIN=<my_mailgun_domain_name>.mailgun.org SMTP_USER_NAME=postmaster@<my_mailgun_domain_name>.mailgun.org SMTP_PASSWORD=<my_mailgun_domain_password> SMTP_SERVER=smtp.mailgun.org SMTP_PORT=587 SMTP_AUTHENTICATION=plain SMTP_ENABLE_STARTTLS_AUTO=true EMAIL_FROM_ADDRESS=postmaster@<my_mailgun_domain_name>.mailgun.org
And here's the command I'm using to run Huginn via Docker:
docker run -d -p 80:3000 --restart=always --env-file .env.huginn -v huginn-data:/var/lib/mysql huginn/huginn.
logininstead and see if that works. I'm also working with my server administrators. It may be that there is a restriction in place to prevent outgoing emails. I didn't think that would also apply to external SMTP services like Mailgun, but maybe it does, since I found that I'm not able to send emails via Mailgun's command line method either. Though I can send emails via curl and Mailgun's API.
@comicmuse Seem to have the below issue
Huginn URL on error page after clicking Twitter button
Twitter Developer Callback URLs
[ActiveJob] Enqueued AgentCheckJob (Job ID: c57a873b-dc22-48c0-87ba-69be01a7aa9e) to DelayedJob(default) with arguments: 10
latestdocker image, (but it may be the same)... perhaps there is some way to rebuild the rail database / schemas etc. too?
cd /path/to/huginn rake routes