[Worker] Worker 0 is ready!
Worker mails started
[Job] Received Job (66198f51670c90.43559084).
[Job] (66198f51670c90.43559084) failed to run.
[Job] (66198f51670c90.43559084) Error sending mail: SMTP Error: Could not authenticate.
Fatal error: Uncaught Exception: Failed to create connection: SQLSTATE[HY000] [1045] Access denied for user ''@'172.21.0.6' (using password: NO) in /usr/src/code/vendor/utopia-php/pools/src/Pools/Pool.php:193
Stack trace:
#0 /usr/src/code/app/worker.php(48): Utopia\Pools\Pool->pop()
#1 /usr/src/code/vendor/utopia-php/queue/src/Queue/Server.php(99): {closure}(Object(Utopia\Cache\Cache), Object(Utopia\Registry\Registry))
#2 /usr/src/code/vendor/utopia-php/queue/src/Queue/Server.php(119): Utopia\Queue\Server->getResource('dbForConsole')
#3 /usr/src/code/vendor/utopia-php/queue/src/Queue/Server.php(99): Utopia\Queue\Server->getResources(Array)
#4 /usr/src/code/vendor/utopia-php/queue/src/Queue/Server.php(388): Utopia\Queue\Server->getResource('project')
#5 /usr/src/code/vendor/utopia-php/queue/src/Queue/Server.php(295): Utopia\Queue\Server->getArguments(Object(Utopia\Hook))
#6 [internal function]: Utopia\Queue\Server->Utopia\Queue\{closure}('0')
#7 /usr/src/code/vendor/utopia-php/queue/src/Queue/Adapter/Swoole.php(37): call_user_func(Object(Closure), '0')
#8 [internal function]: Utopia\Queue\Adapter\Swoole->Utopia\Queue\Adapter\{closure}(Object(Swoole\Process\Pool), '0')
}
thrown in /usr/src/code/vendor/utopia-php/pools/src/Pools/Pool.php on line 193
just trying to send an email, 1.5.3
@VincentGe I need help from you guys here
@Steven Ideas?
mailgun is not receiving it and I've confirmed ENV vars are fine
It's gotta be an auth problem. Double triple check all the environment variables mentioned in our docs
okay apparently it's just mailgun with a disallowed IP, for future reference
but that error is weird
why did it say no username is not allowed as an SQL error?
probably just a bug I presume
Isn’t this a known bug in 1.5.3? Missing envvars on some containers?
No apparently it just was mailgun and a weird error
Cause the error went away 🤷♂️
Are you sure it’s actually gone away? The emails may be sending, but that error might still be there? Does the mail worker container actually have the SQL envvars?
Well if it didn’t it wouldn’t have sent the email regardless of the SQL haha
Restart the container and you might see the error again 😜
hahaha I am thinking maybe it has something to do with Messaging functionality but not using it to send a team invite or something
Dunno
hello. i got the same issue and i cant figure out what the problem is. can someone help
Recommended threads
- I recently switched to TablesDb. When li...
olddb.list_documents( queries =[ Query.order_desc("timestamp"), Query.equal("isPosted",[False]) ] ) Above works fine and reruns documents But below don't return...
- Database error validating 'min' and 'max...
I keep seeing an error when I try to add a column to a database table within the AppWrite cloud UI. I also see this error when trying to create or update a reco...
- Fine grained permissions for webRTC hand...
Hi, I am building a WebRTC P2P app for a university project and have hit a security limitation regarding permissions for anonymous users. The Architecture: We ...