Change SMTP settings and base URL

To change the base URL or SMTP settings of a server, follow these steps:

1. Open the console on the server and run the following command:

elma365ctl reconfigure

2. Select the language.
3. Change the SMTP server connection settings. This connection will be used for sending invites to new users, recovering passwords, and sending notifications about new tasks.
   • SMTP host. Enter the host according to your email server settings. For example, smtp.gmail.com.
   • SMTP port. Enter the connection port according to your email server settings. For example, 465.
   • Encryption method. Select the connection encryption method. For example, TLS.
   • Email address for sending messages. To clear a previously assigned value, enter <empty>.
   • SMTP password. Specify the email server password. To clear a previously assigned value, enter <empty>.
   • From address. This email address will be specified in the “From” field of emails. Example: elma365noreply@company.com.
4. Change the base URL (the local domain name or the server’s IP address). The elma365 service will be available at this URL.
5. This step is optional. It appears only if you specified the domain name at the previous step.
   You can enable HTTPS support to use the SSL certificate. To do that:
   • Specify the domain name as the base URL. If you specified the IP address, HTTPS will not work.
   • You will be prompted to enable HTTPS. Do it.
   • Specify the private key and the SSL certificate for the domain, including not only the domain name but also the certification path. A certificate like this is issued immediately, and its name includes +chain. The key and the certificate have to be stored in your file system.
6. This step is optional. It appears if you specified the domain name at step 4 but didn’t enable HTTPS at step 5. If ELMA365 is installed behind a fully configured proxy with SSL, enable this setting to use it.
7. Enable host aliases. If you specified the domain name during installation, the possibility to establish a connection from the Kubernetes environment for this domain is checked. If it is impossible, you are prompted to enable host aliases to make it work correctly. With some proxy servers, this setting needs to be disabled.

Was this helpful?

Thanks for your feedback!

Please specify why:

Recommendations did not help meArticle is hard to understandDidn`t answer my questionContent does not match the topicOther

How we can improve it?

YesNo

Please specify whyRecommendations did not help meArticle is hard to understandDidn`t answer my questionContent does not match the topicOther

Found a typo? Highlight the text, press ctrl + enter and notify us