topic Re: Getting error while configuring Qlik Alerting email setting in Reporting Service & Alerting

Getting error while configuring Qlik Alerting email setting

sumitk — Wed, 29 Jan 2025 15:57:23 GMT

Hi All,

We installed Qlik Alerting on separate server. We installed Node JS and MongoDB as suggested in Qlik help. After that we installed Qlik Alerting, the connection with Qliksense server becomes successful, but when we are trying to configure Email it is giving error.

Please check error in attached screenshot and help.

Thanks in advance.

Re: Getting error while configuring Qlik Alerting email setting

Anil_Babu_Samineni — Tue, 06 Feb 2024 19:06:43 GMT

@sumitk Hope your email server SMTP gateway added Qlik alerting IP in the whitelist of their network? Do you have any logs on this?

Re: Getting error while configuring Qlik Alerting email setting

Chetan_MN — Wed, 07 Feb 2024 06:48:26 GMT

Hi @sumitk This looks to be a configuration issue on the SMTP end, please have a check with your SMTP administrator.

Re: Getting error while configuring Qlik Alerting email setting

sumitk — Wed, 07 Feb 2024 08:41:38 GMT

Hi,

We already checked with Qlik Support over the call IP is whitelisted and we are able to reach mail server from Alerting server. But still issue persists.

Re: Getting error while configuring Qlik Alerting email setting

sumitk — Wed, 07 Feb 2024 08:41:49 GMT

Hi,

We already checked with Qlik Support over the call IP is whitelisted and we are able to reach mail server from Alerting server. But still issue persists.

Re: Getting error while configuring Qlik Alerting email setting

Anil_Babu_Samineni — Thu, 15 Feb 2024 08:52:51 GMT

@sumitk Do you have any alerting logs that we can see?

Re: Getting error while configuring Qlik Alerting email setting

Chetan_MN — Wed, 21 Feb 2024 08:40:41 GMT

Hi @sumitk Did opening port 587 solve the issue?

Re: Getting error while configuring Qlik Alerting email setting

sumitk — Wed, 28 Feb 2024 08:16:31 GMT

we asked customer to create a new mail id and to open port 25, after doing this issue was resolved.

Thank you all for your support.