Too many failed login attempts. Please try again later!

[Rob_in]

My Android phone auto-updated the Loxone app this morning. No changes to the Miniserver of course.

While the app on my phone works, when trying to login via Web of the App on my PC I see "Too many failed login attempts. Please try again later!"

What is super weird/annoying is that even when I fire up Loxone Config and try to connect as admin (not the same user that is configured on my phone) I see the same message!

Anyone else noticed this?

TIA,

Robin

[Simon Still]

I've had this issue quite a bit.  Rebooting the min server seems to solve it. 

[Rob_in]

Thanks for the reply. Rebooted this morning and seems OK now.

But yes, this is a pretty annoying and potentially dangerous bug.

Robin

[Simon Still]

"potentially dangerous"?

[Rob_in]

On Monday, 20 October 2025 at 17:15:47 UTC+2 Simon Still wrote:

"potentially dangerous"?

Maybe I should have said, "very serious"?

I'd call loosing admin access to the Miniserver from the App, web and Loxone Config pretty catastrophic.

[Simon Still]

I've been able to fix it by rebooting the mini server from the iPhone app - so don't need physical access to the mini server to regain admin access via config/computer.  You've said the app on your phone works. 

I mean, this is clearly a bug but theres a simple workaround once you know what's going on. 

[Rob_in]

This problem happened again this morning.

Can't login from the Loxone app on my laptop.

Can't login from the web interface using any number of users.

Can't login from Loxone Config using the admin user.

I was able to reboot the Miniserver from Loxone app on my phone though, but that didn't change anything.

What's super weird, is that after the reboot I opened the app to try a it second time and the 'Reboot Miniserver' link (I won't call it a button, because it's just green text - UI fail!) doesn't even work. I press it and absolutely nothing happens!

I physically power cycled the Miniserver and now it's back to normal.

This is a horrible and very serious bug!

Robin

[Rob_in]

... and the problem came back less than an hour later.

[Bartel Eerdekens]

Do you also have other systems connected to your Loxone? 

I had this problem before, and it was caused with my Openhab Loxone binding.

Since then, I split up all my accounts for each system (openhab, loxberry, ...).

I think the login-guard is shared across accounts, which is of course not correct.

But then you know where the problem comes from.

Updating your external systems (openhab e.g. for me resolved the issue) could be a good idea.

Also, when this problem occurred, my miniserver was very unresponsive.

But I found out why: I was getting a mini-DDoS attack on my miniserver, because the HTTPS port, 443, was exposed to my miniserver (V1).

When I removed this forward, because it also has no purpose, the external attack was blocked at the router and the miniserver functioned properly again.

Good luck

[Rob_in]

Yes, I do have an ioBroker instance attached to Loxone, but that hasn't changed and is still connected even when I can't login to the GUI.

The Miniserver is on a VLAN that protects it from outside traffic.

Here's the flow I just saw

- Login from Linux laptop using native app. Works just fine.

- Maybe after a minute app is logged out, can no longer login.

- Reboot Miniserver

- Login from Linux laptop using native app. Works just fine.

- Close Linux app.

- Immediately try login from Linux laptop using native app. This now fails.

- Try to login from Loxone Config. This now fails.

At least a manual reboot now fixes this, but still... so bad.

Robin