bugs

Anyone else getting this message when trying to send an email verification?

"There was an error with your request."

It only seems to be on this bot :S.

Can you try again on this bot and see if it's a persistent issue? I checked the logs from around when you were trying to do this and saw an error:

[23-Dec-2019 08:58:51] PHP Fatal error: Uncaught exception 'Swift_TransportException' with message 'Connection could not be established with host smtp.gmail.com [Connection timed out #110]' in /home/mazur/bots4.net/trunk/lib/swiftmailer/classes/Swift/Transport/StreamBuffer.php:273

It's evidently happened a handful of times over years, but mostly this month (and yesterday/today, specifically):

$ grep -H 'Connection could not be established with host smtp.gmail.com' log/php/* | cut -d ':' -f 1 | cut -d '/' -f 3 | cut -d '.' -f 1 | sort | uniq -c
1 20110904
1 20131112
1 20140916
8 20191214
1 20191223
2 20191224

It might have been a transient issue. Were you registering a bunch of bots at once? Maybe the game hit some sort of quota/rate-limiting issue. If it keeps happening, I can look into adding some sort of throttling mechanism to avoid the problem.

I was registering 4 bots at the time, 3 were succesful this one wasn't.

I just tried again and got the same message.

Hmm strange, I don't the error from above in the logs this time.

To make sure I understand, the issue is happening when you're requesting that an email with a verification code be sent to you, not when clicking on a verification code in your email, right?

For next steps, I guess try again in a few days. If the problem is still happening, I'll look into this more closely, will maybe add some more logging, etc.

Yeah, when i try to get the email sent to me with the link i get that error message and dont get the email.

Same thing is happening on this bot.

-Zach

This seems to have cleared up by itself.

I noticed from your dates that on one day in December the error occurred 8 times, not sure if others are still affected?

Alright thanks for the update, I'm going to treat this as a one-off issue unless there are others having problems. It's possible there was a transient issue either with my server or with Google's that the game could detect and handle better, but given that this code hasn't been touched in nearly a decade and that things are working for the majority of people AFAICT, I'm inclined to just leave it alone for now.