SMTP on wasp build connecting on localhost instead of my SMTP provider
So basically, I have my SMTP configured to be on SMTP2go, with the hosting and password as env variables, also in main.wasp it is set to SMTP. When I try on dev mode (with wasp start) it connects to the SMTP host and sends the email correctly, but when I build all the stuff and deploy both backend and frontend, when it comes to sending a mail, it shows this:
POST /auth/email/signup 200 44.671 ms - 16Failed to send email Error: connect ECONNREFUSED 127.0.0.1:587 at __node_internal_captureLargerStackTrace (node:internal/errors:496:5) at __node_internal_exceptionWithHostPort (node:internal/errors:671:12) at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) { errno: -111, code: 'ESOCKET', syscall: 'connect', address: '127.0.0.1', port: 587, command: 'CONN'}
POST /auth/email/signup 200 44.671 ms - 16Failed to send email Error: connect ECONNREFUSED 127.0.0.1:587 at __node_internal_captureLargerStackTrace (node:internal/errors:496:5) at __node_internal_exceptionWithHostPort (node:internal/errors:671:12) at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) { errno: -111, code: 'ESOCKET', syscall: 'connect', address: '127.0.0.1', port: 587, command: 'CONN'}
Is this connecting to my own address on port 587? will opening this port help with smth or is it other problem?
Recent Announcements
Continue the conversation
Join the Discord to ask follow-up questions and connect with the community
W
Wasp
Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.