# Unable to login after an update

**URL:** <https://forum.ghost.org/t/unable-to-login-after-an-update/63950>\
**Category:** Using Ghost\
**Created:** [October 9, 2026, 4:14pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950 "2026-10-09T16:14:20Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![lejeczek](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/lejeczek/32/18989_2.png) [@lejeczek](https://forum.ghost.org/u/lejeczek)\
**Post date:** [October 9, 2026, 4:14pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/1 "2026-10-09T16:14:20Z")

</div>

Hi guys.

I’ve had a perfectly working site and some 4 weeks ago pulled in image update - did not need to login then - now I’m unable to login - just in case pulled in today again.

When container starts it logs:

```auto
[2026-10-09 15:57:03] ERROR Could not get webhook secret for ActivityPub TypeError: fetch failed
[2026-10-09 15:57:03] ERROR No webhook secret found - cannot initialise

```

Then when I try to login:

```auto
2026-10-09 16:04:40] ERROR "POST /ghost/api/admin/session" 500 137ms

Failed to send email. Please check your site configuration and try again.

"Please see https://docs.ghost.org/config/#mail for instructions on configuring email."

Error ID:
    3a7ccc0e-c116-49a8-ad1c-6527915f4f7b

Error Code: 
    ESOCKET

----------------------------------------

EmailError: Failed to send email. Please check your site configuration and try again.
    at Object.sendAuthCodeToUser (/var/lib/ghost/versions/6.69.0/core/server/services/auth/session/session-service.js:471:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
    at async Object.createSession (/var/lib/ghost/versions/6.69.0/core/server/services/auth/session/middleware.js:16:9)

```

And indeed webui login tells me: `Failed to send email. Please check your site configuration and try again. `

But there is more, probably more important bits, when login-landing page gets loaded:

```auto
[2026-10-09 16:06:58] ERROR "GET /ghost/api/admin/users/me/?include=roles" 403 1ms

Authorization failed

"Unable to determine the authenticated user or integration. Check that cookies are being passed through if using session authentication."

Error ID:
    45e898e8-7f8f-489e-ac4c-795c1a750fad

----------------------------------------

NoPermissionError: Authorization failed
    at authorizeAdminApi (/var/lib/ghost/versions/6.69.0/core/server/services/auth/authorize.js:38:9)
    at Layer.handle [as handle_request] (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/express@4.22.3_supports-color@10.2.2/node_modules/express/lib/router/layer.js:95:5)
    at next (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/express@4.22.3_supports-color@10.2.2/node_modules/express/lib/router/route.js:149:13)
    at authenticate (/var/lib/ghost/versions/6.69.0/core/server/services/auth/session/middleware.js:58:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)

[2026-10-09 16:06:58] INFO "GET /ghost/api/admin/site/" 200 1ms
[2026-10-09 16:06:58] ERROR "GET /ghost/api/admin/config/" 403 1ms

Authorization failed

"Unable to determine the authenticated user or integration. Check that cookies are being passed through if using session authentication."

Error ID:
    175f7b29-d1a8-48b2-9db7-01f68555b0c5

----------------------------------------

NoPermissionError: Authorization failed
    at authorizeAdminApi (/var/lib/ghost/versions/6.69.0/core/server/services/auth/authorize.js:38:9)
    at Layer.handle [as handle_request] (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/express@4.22.3_supports-color@10.2.2/node_modules/express/lib/router/layer.js:95:5)
    at next (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/express@4.22.3_supports-color@10.2.2/node_modules/express/lib/router/route.js:149:13)
    at authenticate (/var/lib/ghost/versions/6.69.0/core/server/services/auth/session/middleware.js:58:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)

[2026-10-09 16:06:58] ERROR "GET /ghost/api/admin/users/me/?include=roles" 403 0ms

```

Email config bits I think are pretty clear - besides, all had been working prior to update & config-wise no changes were made, no changes to entire container side of config.

Any & all suggestion on what is not/working & how to try to fix - I’d much appreciate.

many thanks, L

---

<div class="post-metadata">

**Author:** ![lejeczek](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/lejeczek/32/18989_2.png) [@lejeczek](https://forum.ghost.org/u/lejeczek)\
**Post date:** [October 9, 2026, 5:37pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/2 "2026-10-09T17:37:07Z")

</div>

```auto
"staffDeviceVerification": false

```

helps to log in but.. still, not good.

---

<div class="post-metadata">

**Author:** ![jannis](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jannis/32/39718_2.png) [@jannis](https://forum.ghost.org/u/jannis)\
**Post date:** [October 9, 2026, 5:40pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/3 "2026-10-09T17:40:53Z")

</div>

Just looks like you’re missing the email configuration for transactional emails:

> **[​Mail - Configuration - Ghost Developer Docs](https://docs.ghost.org/config#mail)**
>
> For self-hosted Ghost users, a custom configuration file can be used to override Ghost’s default behaviour. This provides you with a range of options to configure your publication to suit your needs.

As noted there, email configuration is required for a production site, for example to send you the staff verification codes.

---

<div class="post-metadata">

**Author:** ![lejeczek](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/lejeczek/32/18989_2.png) [@lejeczek](https://forum.ghost.org/u/lejeczek)\
**Post date:** [October 9, 2026, 5:55pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/5 "2026-10-09T17:55:06Z")

</div>

I don’t think I do - it’s there in `config.production.json` with everything else, which everything else seems to be working a ok.

Like I said - this site of mine had all been working prior to new image I pulled, authorization too, I used to get login confirmation codes via email and… like I said nothing else, config-wise, outside of Ghost (nothing I can think of) has been changed.

From within the container - is there a way, possibly closet way to what Ghost would do, to test email connectivity/functionality?

---

<div class="post-metadata">

**Author:** ![jannis](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jannis/32/39718_2.png) [@jannis](https://forum.ghost.org/u/jannis)\
**Post date:** [October 9, 2026, 5:56pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/6 "2026-10-09T17:56:44Z")

</div>

Can you share your configuration (with secrets redacted)?

Ghost has recently tightened how configurations are typed, so this could be the issue. Different symptom, but sounds kinda similar:

> [@Edit is not redirecting toward backoffice anymore](https://forum.ghost.org/t/edit-is-not-redirecting-toward-backoffice-anymore/63947/):
>
> Version: 6.69.0 Environment: production Database: mysql8 Mail: SMTP Hi Guys, I hope you are well, when i add edit at the end of a post url it was redirecting to backoffice. Now it reddirect to 404 on my website and my clients one. Did i do something wrong? or you guys changed something ? Thanks for letting me know. Best,

---

<div class="post-metadata">

**Author:** ![lejeczek](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/lejeczek/32/18989_2.png) [@lejeczek](https://forum.ghost.org/u/lejeczek)\
**Post date:** [October 9, 2026, 6:44pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/7 "2026-10-09T18:44:24Z")

</div>

```auto
-> $ podman container exec -ti mamba.xyz cat /var/lib/ghost/config.production.json
{
  "url": "https://mamba.xyz",
  "server": {
    "port": 2368,
    "host": "::"
  },
  "database": {
    "client": "mysql",
    "connection": {
      "host": "11.1.0.1",
      "port": 3306,
      "user": "mambaxyzadm",
      "password": "mambaxyz",
      "database": "ghost_mamba_xyz"
    }
  },
  "mail": {
    "transport": "SMTP",
    "from": "postmaster@mamba.xyz",
    "options": {
      "host": "mail.mamba.xyz",
      "port": 465,
      "secure": true,
      "auth": {
        "user": "postmaster@mamba.xyz",
        "pass": "karamba"
      }
    }
  },
  "logging": {
    "transports": [
      "file",
      "stdout"
    ]
  },
  "process": "systemd",
  "paths": {
    "contentPath": "/var/lib/ghost/content"
  },
  "security": {
    "staffDeviceVerification": false
  }
}

```

Ghost is not happy indeed

```auto
[2026-10-09 18:30:57] WARN Ghost was running for 11 minutes
Error: Error parsing your configuration file: [/var/lib/ghost/config.production.json]: Expected ':' after property name in JSON at position 33 (line 2 column 32)
    at File.loadSync (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/nconf@0.13.0/node_modules/nconf/lib/nconf/stores/file.js:170:11)
    at Provider.add (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/nconf@0.13.0/node_modules/nconf/lib/nconf/provider.js:136:23)
    at Provider.file (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/nconf@0.13.0/node_modules/nconf/lib/nconf/provider.js:63:15)
    at loadNconf (/var/lib/ghost/versions/6.69.0/core/shared/config/loader.js:69:11)
    at Object.<anonymous> (/var/lib/ghost/versions/6.69.0/core/shared/config/index.js:3:41)
    at Module._compile (node:internal/modules/cjs/loader:1781:14)
    at Object..js (node:internal/modules/cjs/loader:1913:10)
    at Module.load (node:internal/modules/cjs/loader:1505:32)
    at Function._load (node:internal/modules/cjs/loader:1309:12)
    at wrapModuleLoad (node:internal/modules/cjs/loader:254:19)
Error: Error parsing your configuration file: [/var/lib/ghost/config.production.json]: Expected ':' after property name in JSON at position 33 (line 2 column 32)
    at File.loadSync (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/nconf@0.13.0/node_modules/nconf/lib/nconf/stores/file.js:170:11)
    at Provider.add (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/nconf@0.13.0/node_modules/nconf/lib/nconf/provider.js:136:23)
    at Provider.file (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/nconf@0.13.0/node_modules/nconf/lib/nconf/provider.js:63:15)
    at loadNconf (/var/lib/ghost/versions/6.69.0/core/shared/config/loader.js:69:11)
    at Object.<anonymous> (/var/lib/ghost/versions/6.69.0/core/shared/config/index.js:3:41)
    at Module._compile (node:internal/modules/cjs/loader:1781:14)
    at Object..js (node:internal/modules/cjs/loader:1913:10)
    at Module.load (node:internal/modules/cjs/loader:1505:32)
    at Function._load (node:internal/modules/cjs/loader:1309:12)
    at wrapModuleLoad (node:internal/modules/cjs/loader:254:19)

```

though Ghost starts

---

<div class="post-metadata">

**Author:** ![acburdine](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/acburdine/32/4825_2.png) [@acburdine](https://forum.ghost.org/u/acburdine)\
**Post date:** [October 9, 2026, 6:52pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/8 "2026-10-09T18:52:24Z")

</div>

Unlisted on October 9, 2026, 6:52pm UTC



---

<div class="post-metadata">

**Author:** ![acburdine](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/acburdine/32/4825_2.png) [@acburdine](https://forum.ghost.org/u/acburdine)\
**Post date:** [October 9, 2026, 6:53pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/9 "2026-10-09T18:53:48Z")

</div>

Are those your actual credentials? 😅 It seems like they might not be but I unlisted the post out of an abundance of caution, if they’re fake creds I’ll remove the unlisted designation.

---

<div class="post-metadata">

**Author:** ![acburdine](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/acburdine/32/4825_2.png) [@acburdine](https://forum.ghost.org/u/acburdine)\
**Post date:** [October 9, 2026, 7:02pm UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/10 "2026-10-09T19:02:09Z")

</div>

Looking into it a bit though - the error message you posted originally points to some sort of outbound networking issue. The container not being able to reach the configured hosts (both ActivityPub and mail) would indicate that there’s something misconfigured outside of the container itself related to its networking.

Not sure why Ghost is complaining about config formatting though 🤔

---

<div class="post-metadata">

**Author:** ![lejeczek](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/lejeczek/32/18989_2.png) [@lejeczek](https://forum.ghost.org/u/lejeczek)\
**Post date:** [October 10, 2026, 12:36am UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/11 "2026-10-10T00:36:23Z")

</div>

I wouldn’t say “fake” - this is an actual config with only some bits… obfuscated - common practice I believe (same as or easier than replacing with xzxzxcy..)

---

<div class="post-metadata">

**Author:** ![lejeczek](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/lejeczek/32/18989_2.png) [@lejeczek](https://forum.ghost.org/u/lejeczek)\
**Post date:** [October 10, 2026, 12:42am UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/12 "2026-10-10T00:42:45Z")

</div>

I think that crucial bit - json config errors are gone now (perhaps due to the fact json file resides on networked fs, perhaps there were “issues” or something else, config is the same) - is:

`Unable to determine the authenticated user or integration. Check that cookies are being passed through if using session authentication`

The error which occurs a few times in succession when container is started & when log in/out happens:

```auto
[2026-10-10 00:21:39] INFO "DELETE /ghost/api/admin/session/" 204 8ms
[2026-10-10 00:21:39] INFO "GET /ghost/" 200 3ms
[2026-10-10 00:21:39] ERROR "GET /ghost/api/admin/users/me/?include=roles" 403 3ms

Authorization failed

"Unable to determine the authenticated user or integration. Check that cookies are being passed through if using session authentication."

Error ID:
    63faadb7-09e7-4b8d-87ad-58cee400abd9

----------------------------------------

NoPermissionError: Authorization failed
    at authorizeAdminApi (/var/lib/ghost/versions/6.69.0/core/server/services/auth/authorize.js:38:9)
    at Layer.handle [as handle_request] (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/express@4.22.3_supports-color@10.2.2/node_modules/express/lib/router/layer.js:95:5)
    at next (/var/lib/ghost/versions/6.69.0/node_modules/.pnpm/express@4.22.3_supports-color@10.2.2/node_modules/express/lib/router/route.js:149:13)
    at authenticate (/var/lib/ghost/versions/6.69.0/core/server/services/auth/session/middleware.js:58:7)

[2026-10-10 00:21:39] INFO "GET /ghost/api/admin/site/" 200 0ms
[2026-10-10 00:21:39] ERROR "GET /ghost/api/admin/users/me/?include=roles" 403 3ms

```

---

<div class="post-metadata">

**Author:** ![acburdine](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/acburdine/32/4825_2.png) [@acburdine](https://forum.ghost.org/u/acburdine)\
**Post date:** [October 10, 2026, 1:57am UTC](https://forum.ghost.org/t/unable-to-login-after-an-update/63950/13 "2026-10-10T01:57:20Z")

</div>

Listed on October 10, 2026, 1:57am UTC


