claabs / epicgames-freegames-node

Automatically login and find available free games the Epic Games Store. Sends you a prepopulated checkout link so you can complete the checkout after logging in. Supports multiple accounts, login sessions, and scheduled runs.
https://hub.docker.com/r/charlocharlie/epicgames-freegames
MIT License
1.38k stars 93 forks source link

Error sending email. Please check your configuration #88

Closed nitanmarcel closed 3 years ago

nitanmarcel commented 3 years ago

Hi! I can't get SMTP to work on my machine (Windows 10 + Docker)

Here's a full log of what`s going on

Incoming env vars:

RUN_ON_STARTUP: true

CRON_SCHEDULE:

RUN_ONCE:

No JSON file found

Setting config variables

Run on startup: true

Run once: false

> epicgames-freegames-node@3.0.0 start /usr/app

> node dist/src/index.js

[2021-02-24 07:28:12.069 -0600] INFO (26 on 84cf8e21a17a): Checking free games for nitan.marcel@gmail.com

[2021-02-24 07:28:20.575 -0600] ERROR (26 on 84cf8e21a17a): Error sending email. Please check your configuration

user: "nitan.marcel@gmail.com"

emailConfig: {

"smtpHost": "smtp.gmail.com",

"smtpPort": 587,

"emailSenderAddress": "nitan.marcel@gmail.com",

"emailSenderName": "Marcel Alexandru",

"emailRecipientAddress": "nitan.marcel@gmail.com",

"secure": true,

"auth": {

"user": "nitan.marcel@gmail.com",

"pass": "*****"

}

}

[2021-02-24 07:28:20.578 -0600] ERROR (26 on 84cf8e21a17a): 139719869136200:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

Error: 139719869136200:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

[2021-02-24 07:28:20.583 -0600] ERROR (26 on 84cf8e21a17a): 139719869136200:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

Error: 139719869136200:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

Setting timezone: America/Chicago

Setting cron schedule as 0 12 * * *
claabs commented 3 years ago

Duplicate of #34

nitanmarcel commented 3 years ago

Duplicate of #34

`It doesn't work. I saw the issue and I've set secure to false but I got the same error~

Or nvm, I see it,s still set to secure in docker

nitanmarcel commented 3 years ago

@claabs I'm running it with this command again but it's still says it's secure in the json:

docker run -d -e TZ=America/Chicago -e EMAIL=nitan.marcel@gmail.com -e PASSWORD=***-e TOP=******-e RUN_ON_STARTUP=true -e SMTP_HOST=smtp.gmail.com -e SMTP_PORT=587 -e SMTP_HOST=smtp.gmail.com -e EMAIL_SENDER_ADDRESS=nitan.marcel@gmail.com -e EMAIL_SENDER_NAME="Marcel Alexandru" -e EMAIL_RECIPIENT_ADDRESS=nitan.marcel@gmail.com -e SMTP_SECURE=false -e SMTP_USERNAME=nitan.marcel@gmail.com -e SMTP_PASSWORD=***-v /my/host/dir/:/usr/app/config:rw -p 3001:3000 charlocharlie/epicgames-freegames:latest

I'm not used to docker so maybe I forgot something.

emailConfig: {

"smtpHost": "smtp.gmail.com",

"smtpPort": 587,

"emailSenderAddress": "nitan.marcel@gmail.com",

"emailSenderName": "Marcel Alexandru",

"emailRecipientAddress": "nitan.marcel@gmail.com",

"secure": true,

"auth": {

"user": "nitan.marcel@gmail.com",

"pass": "***"

}

}
claabs commented 3 years ago

Looks like I got tricked by the JS Boolean() function. Try pulling the image once the build is finished on Docker Hub.

nitanmarcel commented 3 years ago

@claabs

Thanks is working. ~but I got another problem: I can't access localhost from my computer. Every time I try to enter the link I get Unable to connect message~ But the address sent by the email is wrong. The port it's 3001 not 3000 as the email says

Also you might add a small detail in the readme to tell users to make sure they allow less secure apps to log to google:

https://support.google.com/accounts/answer/6010255

nitanmarcel commented 3 years ago

I fixed the problem above but there's no capcha visible:

image

claabs commented 3 years ago

Please file a new issue following the bug report (captcha UI) template. That will help me diagnose your use case and the problem you're having.