Wekan - nach Reboot kein Login mehr möglich

Apps & App Center
1

Hallo Leute,

UCS 4.4.1 Errata 241. Benutze hier seit einigen Tagen sehr erfolgreich Wekan. Seit einem Reboot, der VM (keine Änderung), funktioniert der Login nicht mehr. User die eingeloggt sind, können damit noch arbeiten, alle anderen kommen nicht mehr drann. Es kommt auch keine Fehlermeldung beim Login am Webinterface von Wekan. Lediglich ein Timeout von ca. 10 Sekunden. In der Apacheerror und Accesslog kommt überhaupt gar keine Meldung.

Mein Benutzer (admin) ist auch noch eingeloggt. Die Einstellungen scheinen zu passen. Auch sieht man die gesamte Userliste in den Einstellungen. Kann mir bitte jemand helfen. Setzt nämlich schon sämtliche Arbeitspläne auf Wekan.

  • Selbsttest aller UCS ok
  • User von Wekan entfernt und neu hinzugefügt, keine Änderung

Vielen Dank und glg
boospy

2

Hello,

I translate it to be able to involve the Wekan maintainer.

UCS 4.4.1 Errata 241. I’ve been using Wekan very successfully for a few days now. Since a reboot, the VM (no change), the login doesn’t work anymore. Users who are logged in, can still work with it, all others can’t get through. There is also no error message when logging in at the web interface of Wekan. Only a timeout of about 10 seconds. In the Apacheerror and Accesslog there is no message at all.

My user (admin) is still logged in. The settings seem to fit. You can also see the whole user list in the settings. Can someone please help me? It already sets all work plans to Wekan.

  • Self-test of all UCS ok
  • User removed from Wekan and added new, no change

Best regards
Nico

1 Like
3

It could be Wekan brute force login prevention, that notices wrong passwords.

You can look are some accounts locked out:

sudo su
docker exec -it wekan-db bash
mongo
use wekan
db.AccountsLockout.Connections.find();

If there is any, you can delete them with:

db.AccountsLockout.Connections.deleteMany({});

Then exit from MongoDB CLI and Docker container:

exit
exit
4

Probably I should add most Wekan settings to Univention web UI, like this lockout:

5

You will see here when this is sometime solved:

6

There was a lock:
{ "_id" : "ovxucoTsGSqSGiios", "clientAddress" : "172.16.0.1", "services" : { "accounts-lockout" : { "lastFailedAttempt" : 1566996732090, "firstFailedAttempt" : 1566996732086 } } }
But don’ t know what this really means. Maybe this ID “ovxucoTsGSqSGiios” is an username. No this part is clean. I’ve restarted the dockerCT’s. But login still not working.

Is there a way to the the right logs, were i can see why users can’t login?

7

New cognition. I think the issue is depending on changing the main mailadress in UCS from the users. I think the user is then not right registered in wekan. If i would change the existing mailadress in wekan for that users, the system says, address already exist. But this is wrong.

8

Wekan will no longer upload any attachment - After upgrade to UCS Version

4.4-1 errata305 (Blumenthal)

UMC Version

11.0.4-36A~4.4.0.201909050927 – no longer upload any attachments, images or pdfs. No longer usable as a result

9

Works here fine on UCS 4.4.2 with Wekan 3.42.0.