I recently restarted my nextcloud AIO containers and now I can’t log in.
I use a password manager, so I’m pretty sure the password is correct. I’ve restarted the containers again and examined the logs. I didn’t see anything in the logs worth mentioning.
There were no changes made since the last time this worked, except for restarting the host and then the containers.
How should I start?
Mike.
Is just the initial attempt failing but it works on the next attempt?
A few hours after I posted this, I was able to get logged in on my android using Firefox. However, my Linux workstation is still having problems.
I can get logged in, but the calendar isn’t working. I’m getting a box at the top right of the screen indicating that it can’t load the page. I get the calendar grid, but none of my calendars are loading.
I’ll try to attach a screen shot.
Mike.
Please check your browser inspect, under the Network tab to see what transaction is failing.
Do you have a reverse proxy in front of AIO?
So, a few hours after posting the reply, above, it started working on my phone, then I tested on my workstation w/ Chrome and it worked. Finally, it began to work on my workstation w/ Firefox. But this was almost 12 hours after the containers were restarted, and I didn’t do ANYTHING to try to fix this other than post here…
So, going forward, if I have problems with NC, I’m going to treat it as a moody teenage girl and give it some alone time to work things out! LOL.
Thanks for your time.
Mike.
Glad you got it working, but that’s not normal. 
Are you by chance using a reverse proxy in front of AIO? Such as NPM?
Yes, in fact, I am running NC behind an NPM proxy. Is there something(s) I need to know about running in this configuration?
I do suspect that this configuration is causing issues with the activity links not working…
I appreciate your time.
Mike.
Me ocurre lo mismo. Aunque en mi caso, lo tengo instalado directamente en una maquina debian11.
Tenia versión 29.0.1.1, actualicé aplicaciones keeweb (tenía version 0.6.18) y music (tenía version1.11.0). También me estaba dando error de que cron, no se ejecutaba desde hace varios meses. Tras solucionar lo de cron, y ejecutarlo, es cuando comenzó a fallar.
No me dejaba iniciar sesión. En los dispositivos en los que ya tenía iniciada sesión, sigue funcionado, pero es imposible iniciar una nueva.
Cargue un backup que tenía del día anterior a cuando me ocurrió esto y comprobé que seguía fallando.
Como en uno de los dispositivos tenía iniciada sesión como administrador actualice a versión 29.0.7.1 y sigue dando el mismo fallo.
¿Alguien sabe que puede estar ocurriendo?
The same thing happens to me. Although in my case, I have it installed directly on a debian11 machine.
I had version 29.0.1.1, I updated the keeweb applications (it had version 0.6.18) and music (it had version 1.11.0). I was also getting an error that cron had not been running for several months. After fixing the cron issue and running it, that’s when it started to fail.
It wouldn’t let me log in. On the devices where I was already logged in, it still works, but it’s impossible to start a new one.
I loaded a backup I had from the day before this happened to me and found that it was still failing.
Since I was logged in as administrator on one of the devices, I updated to version 29.0.7.1 and it still gives the same error.
Does anyone know what could be happening?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
