search

polhenarejos / acme_email

ACME Email Client for EmailReply-00 Challenge
https://acme.castle.cloud
GNU General Public License v3.0
59 stars 9 forks source link

ClientError: Response 500 #41

Open d0x7 opened 3 months ago

d0x7 commented 3 months ago

I was trying to request a new certificate, which didn't work using imap/smtp. Nothing happened, no output whatsoever (besides the "you're requesting a cert [...]" header), and then after around 5 minutes, I got a An unexpected error occurred: ConnectionResetError: [Errno 54] Connection reset by peer.

Then I thought I would try the interactive mode, which just game me An unexpected error occurred: acme.errors.ClientError: <Response [500]> instantly.

Are there any known issues or what am I doing wrong? I cloned the repo, installed it as per README and then basically used the example command (obviously with my own imap/domains). I had a typo in the password which also instantly tripped an wrong password error, but after correcting, the above happened, so nothing for around 5 mins, then the first error.

Have a good day :)

polhenarejos commented 3 months ago

Try again. I’ve restarted the backend.

d0x7 commented 3 months ago

Nope, it's unfortunately giving the same 500 instantly again.

polhenarejos commented 3 months ago

Please provide the full log stack.

d0x7 commented 3 months ago

I've sent you an email to xxxxx because I don't wanna post it publicly due to privacy reasons.

polhenarejos commented 3 months ago

Does #40 solve it?

d0x7 commented 3 months ago

I tried that, but that was actually not the issue. I narrowed it down a bit more. The issue is with requesting multiple emails in one go from multiple different domains. -e test1@example.com -e test2@example.com works just fine, but -e test1@example.com -e test2@gmail.com causes it to return the 500. The usage type doesn't matter, with multiple emails on the same domain it works with all four types, but fails when using two different domains with even just the digitalSignature type.

polhenarejos commented 3 months ago

A bug in the backend. Can you try again?