The circumstances are similar: we manually added this member in the backend a few months ago, the theme is a customized version of Casper, and we recently added Portal. We haven’t made any edits to the signup file, however, and we’re currently on 3.40.5. The email address giving the error is a me.com one.
I was able to use the link generated by “Impersonate” to bypass the error, which allowed them to temporarily log in, but they are still not able to sign in via their email address.
My latest test was to delete their account in the backend and try creating a new one from the Portal signup form. That gives a different error: “Failed to sign up, please try again.” Since I also have a me.com email address, I tested my own: same error.
Hey @brooklet , thanks for attaching the error log, I can see the requests failing for me.com addresses on https://blog.brainandbrain.co/ - though I am unable to reproduce the same thing on my blog for me.com address. Can you please post extended error log for around this particular error as that might help with more insight on the problem here in debugging this ?
Thanks for the stack-trace @brooklet . This error seems unrelated to the email issue though and something with error logging in Ghost-CLI, but it does seem like there is an issue with me.com addresses from the multiple reports. Will investigate it further, and leave an update once I have more details on it, or reach back if I need more info.
Though the problem wasn’t on Mailgun’s end, I did find the solution in the thread linked to in my previous post: editing my config.production.json file. I’d installed with DigitalOcean and wasn’t aware of this file, so it wasn’t set up with my Mailgun credentials.