# Cannot login in https://manage.ntppool.org/

**URL:** <https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903>\
**Category:** Pool Development\
**Created:** [July 2, 2025, 8:54pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903 "2025-07-02T20:54:39Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![KsmoinO](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KsmoinO](https://community.ntppool.org/u/KsmoinO)\
**Post date:** [July 2, 2025, 8:54pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/1 "2025-07-02T20:54:39Z")

</div>

Hello

Today I cannot login in [manage.ntppool.org](http://manage.ntppool.org) with email.

After login I’m always redirected to `https://manage.ntppool.org/manage?`

But I’m able to connect here with the same account on the same login page.

I tried on Librewolf (Firefox) and Chromium with the same result

Regards

---

<div class="post-metadata">

**Author:** ![connatic](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/connatic/32/19_2.png) [@connatic](https://community.ntppool.org/u/connatic)\
**Post date:** [July 3, 2025, 5:01am UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/2 "2025-07-03T05:01:42Z")

</div>

I get to the offer to add a passkey. Turning that down takes me to another login page.

---

<div class="post-metadata">

**Author:** ![ronv42](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ronv42/32/1466_2.png) [@ronv42](https://community.ntppool.org/u/ronv42)\
**Post date:** [July 3, 2025, 1:20pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/3 "2025-07-03T13:20:34Z")

</div>

I am receiving this:

# 503 Service Unavailable

No server is available to handle this request.

---

<div class="post-metadata">

**Author:** ![KsmoinO](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KsmoinO](https://community.ntppool.org/u/KsmoinO)\
**Post date:** [July 3, 2025, 1:23pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/4 "2025-07-03T13:23:10Z")

</div>

I’m currently receiving this message too and the same at [www.ntppool.org](http://www.ntppool.org)

---

<div class="post-metadata">

**Author:** ![marco.davids](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/marco.davids/32/767_2.png) [@marco.davids](https://community.ntppool.org/u/marco.davids)\
**Post date:** [July 3, 2025, 2:19pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/5 "2025-07-03T14:19:08Z")

</div>

Here is some info:

> **[Database outage](https://status.ntppool.org/incidents/rs48y2p1xjrv)**
>
> NTP Pool System Status's Status Page - Database outage.

---

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [July 3, 2025, 3:15pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/6 "2025-07-03T15:15:19Z")

</div>

I hope this gets fixed soon. An old value for the netspeed setting by far exceeds the line bitrate to one of my instances, making it inaccessible and disrupting other services, and at this rate blasting through this month’s traffic quota in days (though I am fully sure it will not come to the latter)… 🤨 🙂

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [July 3, 2025, 11:22pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/7 "2025-07-03T23:22:15Z")

</div>

I moved the production database to a new version of MySQL earlier in the week (using the same instance the beta system has been using since sometime last year). There were some minor hiccups in the process, but I left it in what I thought was a stable happy place.

Early early this morning California time the database cluster went into read-only mode. I couldn’t get it back in sync when I woke up and saw it. I decided the best cause of action was to clear the cluster and restore the most recent backup (from a few hours prior).

I deleted the cluster and pointed to the backup, but the (open source) tool to restore the backup had a bug that made the restore fail and it took me a little while to learn enough about it to add debugging, deploy a custom build and then fix the bug. Ooof.

It was down for almost 6 hours by the time it was up and working again.

It was a major database upgrade now completed though, so hopefully there won’t be something like it until maybe converting to Postgres at some point in the future.

---

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [July 4, 2025, 5:07am UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/8 "2025-07-04T05:07:09Z")

</div>

Sorry to hear about all the issues you faced, many thanks for your hard work to overcome them and get the system back up!

---

<div class="post-metadata">

**Author:** ![KsmoinO](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KsmoinO](https://community.ntppool.org/u/KsmoinO)\
**Post date:** [July 4, 2025, 7:58am UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/9 "2025-07-04T07:58:12Z")

</div>

Thanks for the main services.

Howover, I’m still unable to connect using my email/password on `manage.ntppool.org`.

I rejected passkey too

---

<div class="post-metadata">

**Author:** ![Kets\_One](https://avatars.discourse-cdn.com/v4/letter/k/46a35a/32.png) [@Kets\_One](https://community.ntppool.org/u/Kets_One)\
**Post date:** [July 4, 2025, 8:53am UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/10 "2025-07-04T08:53:12Z")

</div>

same here. no access to manage page

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [July 4, 2025, 9:25am UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/11 "2025-07-04T09:25:34Z")

</div>

@KsmoinO & @Kets_One — can you direct message me the traceid from the http headers or the top of the html page? It’s hard to catch the failed login, but a request close in time will help me find the login in the logs.

---

<div class="post-metadata">

**Author:** ![KsmoinO](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KsmoinO](https://community.ntppool.org/u/KsmoinO)\
**Post date:** [July 4, 2025, 9:56am UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/12 "2025-07-04T09:56:32Z")

</div>

I have just sent you a request-id header (I did not find traceid ☹ )

---

<div class="post-metadata">

**Author:** ![KsmoinO](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KsmoinO](https://community.ntppool.org/u/KsmoinO)\
**Post date:** [July 4, 2025, 6:58pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/13 "2025-07-04T18:58:45Z")

</div>

Was it what you needed?

---

<div class="post-metadata">

**Author:** ![avij](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/avij/32/197_2.png) [@avij](https://community.ntppool.org/u/avij)\
**Post date:** [July 5, 2025, 6:19am UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/14 "2025-07-05T06:19:55Z")

</div>

Hi @ask, looks like the 503’s for the websites are back.

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [July 5, 2025, 8:41am UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/15 "2025-07-05T08:41:14Z")

</div>

yeah, I’m learning way more about MySQL group replication than I ever intended to know!

I’d upgraded the development and beta database to MySQL 8.0 (from 5.7) late last year and moved the production database last weekend to have it updated before deploying the new code, and it’s … not a good time.

I got it back in sync now. If it fails again I’ll redo the setup with just a single database node to have a simple setup.

Part of all the monitoring work has been to get setup to not have all the monitoring data flow through the database to make it simpler to move to postgres. I might move the postgres migration up the todo list and just deal with the `log_scores` table as it is (it’s down to just one day of data, all the graphs operate on clickhouse so the database table is just there as a staging area for the various archives of the data and for the “selector” to do queries to determine the best monitors for a server).

---

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [July 5, 2025, 9:25am UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/16 "2025-07-05T09:25:54Z")

</div>

Sorry to hear about the continued issues with the database, thanks for getting the system back up again once more, keeping fingers crossed that it remains stable now 🤞

In the unlikely case that you might not be aware yet:

Attempting to validate servers in the production system continues to return “503 Service Unavailable” for me for the call to [https://validate6.ntppool.dev/p/](https://validate6.ntppool.dev/p/) and its IPv4 equivalent.

---

<div class="post-metadata">

**Author:** ![Kets\_One1](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/kets_one1/32/1700_2.png) [@Kets\_One1](https://community.ntppool.org/u/Kets_One1)\
**Post date:** [July 5, 2025, 12:13pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/17 "2025-07-05T12:13:10Z")

</div>

I’m sorry to report that i still cannot get back into [pool.ntp.org: the internet cluster of ntp servers](http://manage.ntppool.org/manage).  
When i fill credentials i dont get forwarded to status page, but just back to login page.  
No errors, but it also doesn’t ask for MFA …

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [July 5, 2025, 12:46pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/18 "2025-07-05T12:46:16Z")

</div>

@Kets_One1 still now? If so can you send me traceid from a request close to this one?

---

<div class="post-metadata">

**Author:** ![KsmoinO](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@KsmoinO](https://community.ntppool.org/u/KsmoinO)\
**Post date:** [July 5, 2025, 1:17pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/19 "2025-07-05T13:17:25Z")

</div>

I’m still unable to connect using my email/password on `manage.ntppool.org` too.

I have just PM you a new request-id

In other hand, those credentials works on [community.ntppool.org](http://community.ntppool.org) and [web.beta.grundclock.com](http://web.beta.grundclock.com)

---

<div class="post-metadata">

**Author:** ![mail](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/mail/32/1631_2.png) [@mail](https://community.ntppool.org/u/mail)\
**Post date:** [July 5, 2025, 3:49pm UTC](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903/20 "2025-07-05T15:49:33Z")

</div>

New user, just signed up. I can’t log in with Brave. Same loop as described above. Looks like this has been an issue for a few days so I’ll try again next week.

[Next page](https://community.ntppool.org/t/cannot-login-in-https-manage-ntppool-org/3903.md?page=2)
