-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker container has problems sending emails after signup #627
Comments
From slack https://pecanproject.slack.com/archives/C8QSKFDG8/p1546336813005300?thread_ts=1546309635.005100&cid=C8QSKFDG8 : it is configured to send email using localhost. See https://guides.rubyonrails.org/action_mailer_basics.html#action-mailer-configuration-for-gmail how to change it (see in same page for all variables you can set) Probably enough to just set
|
@robkooper I just got another report about it happening on bety6.ncsa.illinois.edu / terraref.ncsa.illinois.edu/bety is this something that can be set, at least as a default, in the docker container or a configuration yml file? |
bety6 does not run docker, so this is something else. When did this happen? |
It happened last week. Also the accounts were created but no email was sent out. |
Do you have an approximate date/time so I can look at the log files. |
According to Slack ~ Tues Dec 3 around or before 8:37 AM AZ time. users.created_at on bety6 times are 2019-12-10 15:04:11, 2019-12-03 15:31:41, 2019-12-03 15:31:41 |
There is an error reported to the user of the web site after signing up for an account when running the docker image. The account gets created however. This indicates that the problem arises from attempting to send email. The error reported to the user is
We're sorry, but something went wrong. We've been notified about this issue and we'll take a look at it shortly.
The exception message (which I can't find right now) indicates that the problem occurs when trying to bind to port 25.The text was updated successfully, but these errors were encountered: