Can't log in to Pikapod hosted Ghost, accidentally created second domain?

Using Ghost
1

Hello,

Just signed up for ghost today and I’m having trouble after I think I accidentally created a second account or domain and now I can’t log into my Pikapods hosted Ghost blog.

First I created an account on Ghost, under the free trial period. Then I signed up for Pikapods to host a Ghost blog. That led me to another Ghost sign up where I assumed I would be logging into my Ghost account, but instead it created a different site.

I decided to cancel the trial and close the first blog, but now I can’t log in to the Pikapods host Ghost website. Instead, on the Ghost log in page I just get the error “Failed to send email. Please check your site configuration and try again.” I’m not sure what configuration it is I need to change (and if it’s a Ghost configuration I don’t know how to log in and change it!)

I’ve contacted support but trying to figure out if there’s anything I can do in the mean time.

2

Hey @cashley ! So, as of a couple weeks ago, Ghost sends a device verification email for new admin logins. I’m guessing that’s the problem here – you got logged out, and now can’t get logged back in.

So, two options:

  1. Configure transactional email. This is done in config.production.json, or in the case of Pikapods, by setting your environment variables (it’s an option in the pikapods control panel). If you plan to have members (required for sending a newsletter, comments, content gating, etc), you need to do this anyway.

  2. Disable device verification. In your environment variables, set security__staffDeviceVerification to false. (That’s a new option and right at the top of the env vars. I suspect you’re not the only Pikapods user to hit this issue recently!)

3

Hi @Cathy_Sarisky ! Do you know is it possible to configure transactional email if I already use Mailgun for both. My config.production.json is now

"mail": {
    "transport": "SMTP",
    "options": {
      "service": "Mailgun",
      "host": "smtp.eu.mailgun.org",
      "port": 465,
      "secure": true,
      "auth": {
        "user": "имя@домен.com",
        "pass": "пароль который появляется в окне на пару секунд"
      }
    }
  },
4

Your config file shows that you have transactional email configured – but that error message says there’s a problem with it.

I’d try recreating the password in Mailgun, if you haven’t already, in case it isn’t what you think. Also confirm that your account is eu, not us, as the host is different.

Your next step would be to check your Ghost logs (via pikapods dashboard) and your Mailgun logs, to see if you can find the problem.

5

No I mean, for now my config and mailgun working good. I am asking just in case in the future if something happened with mailgun account. How can I configure config.production.json if already use mailgun.
As I understood no way use 2 smtp servers? For example 1 custom for transaction and second one for bulk mail (it will be mailgun according to documentation)…

P.S. maybe this question better for separate topic…