Issues with SMTP configuration (mail not sending)

[LeoRitterVR]

Hello,

I am opening this post because I am encountering a problem when deploying this solution in a Kubernetes environment.

I based my approach on the tutorial described in this link to perform the operation: https://hubs.mozilla.com/labs/community-edition-case-study-quick-start-on-gcp-w-aws-services/

I am facing an issue when my deployment is finished and I try to connect as an administrator to the hub. Everything appears to be functional visually (no specific errors in the console), however, it seems that the email for connection request is not being sent.

General information:

• I am using Digital Ocean as my Kubernetes provider.
• I am using Mailgun as an SMTP service (tests also conducted with Amazon SES).

Upon inspecting the logs of the Reticulum pod, I found this during the connection attempt:

Here is also the configuration of my render_hcce.sh file used during deployment:

I have tried several SMTP services like Mailgun and Amazon SES, and have tested the configurations in another application, so it is unlikely that the SMTP service is at fault here. I also tried to open my 587 port (the one the SMTP service is using), but that didn't changed anything.

Any help regarding a possible mishandling would be greatly appreciated.

[Doginal]

Try running kubectl get secret configs -n hcce that will show you if the values got applied correctly. exec into the ret pod and try echoing out the vars maybe they didn't get set correctly on kubectl apply 🤷‍♂️

[LeoRitterVR]

Try running kubectl get secret configs -n hcce that will show you if the values got applied correctly. exec into the ret pod and try echoing out the vars maybe they didn't get set correctly on kubectl apply 🤷‍♂️

Unless I'm mistaken, it's not possible to run the command "kubectl get secret configs -n hcce" in the pod's environment because kubectl is not installed there. In any case, that's my situation.

Should I manually install it to be able to perform the execution?

[Doginal]

run it from where you installed the platform! That will show you if the configs exist then check kubectl describe secret configs -n hcce which will show you if each key/value has data. Then in the pod, echo out the env var you want to see. There is no need to install kubectl in the pods.

[Arko7777]

run it from where you installed the platform! That will show you if the configs exist then check kubectl describe secret configs -n hcce which will show you if each key/value has data. Then in the pod, echo out the env var you want to see. There is no need to install kubectl in the pods.

facing same issue, checked all the value + data and echoed all out. smh still not sending the mail. Any idea what the issue may be?

[Arko7777]

run it from where you installed the platform! That will show you if the configs exist then check kubectl describe secret configs -n hcce which will show you if each key/value has data. Then in the pod, echo out the env var you want to see. There is no need to install kubectl in the pods.

facing same issue, checked all the value + data and echoed all out. smh still not sending the mail. Any idea what the issue may be?

Thanks to the great support of @Doginal I have fixed the issue and now everything is running on my GCP connected to SES.

Here some info for everybody facing the same issue:

• if you use smtp.gmail.com you may run into some cred issues because of 2fa
• if you use SES or other mail providers, make sure you use port 587. 25 is over http and will not make it run over https
• the moment you change your creds inside the render_hcce.sh and deploy MAKE SURE to delete your recticulum pod, cause it is not updating automatically.

Following steps solved my issue:

1) change Port from 25 to 587 2) bash render_hcce.sh && kubectl apply -f hcce.yaml 3) kubectl get pods -n hcce 4) kubectl delete pod [YOUR_RETICULUM] -n hcce 5) DONE :white_check_mark:

[mikemorran]

Great job @Doginal and @Arko7777