Skip to content

Login Error #433

Closed
Closed

Description

@Aybee2k

Actual behaviour

When logging in via the Android app, the error always appears: The server takes too long for a response

Steps to reproduce

We can not say half a day we could use the app and then Suddenly the error.

Environment data

Android version: 6.0.1

Device model: Moto G4+

Stock or customized system: Stock
Nextcloud app version: 1.4.0
Nextcloud server version: 10.0.1 (stable)

Activity

  1. tulamidan commented on Jan 8, 2017

    @tulamidan

    Same here. Android 7.1 Nextcloud 10.0.1, App 1.4.0
    After trying to change the password I am stuck here.
    The same actually happens with the OCloud app.

  2. Aybee2k commented on Jan 8, 2017

    @Aybee2k
    Author

    After we have cleared the cache of the APP and the mobile phone has re-started it worked with us.

  3. tulamidan commented on Jan 8, 2017

    @tulamidan

    I wish it was so easy. Als my desktops can't connect any more. Only the webUI works fine

  4. tobiasKaminsky commented on Feb 10, 2017

    @tobiasKaminsky
    Member

    @tulamidan if it also does not work with a desktop client, then it seems more related to the server.

  5. madmas commented on Apr 26, 2017

    @madmas

    Hi, I have the same issue after changing the password on the server.
    It seems like the app has difficulties to invalidate the session and just re-request the password. (Same thing seems to be the case for the desktop sync app : -( ).
    Will try to remove the account and restart the phone.

  6. JSoko commented on Apr 27, 2017

    @JSoko
    Member

    @madmas Please first have a look in your bruteforce table and delete relateing entries:
    You can handle the bruteforcetable with phpmyadmin or in the terminal:

    DON'T FORGET TO MAKE A DATABASE BACKUP!

    mysql
    USE nextcloud;
    SHOW tables;
    SELECT * FROM oc_bruteforce_attempts;
    

    Lists the bruteforce entries
    For removing rows:

    DELETE FROM oc_bruteforce_attempts WHERE IP="nnn.nnn.nnn.nnn.";
    SELECT * FROM oc_bruteforce_attempts;
    exit
    
    
  7. madmas commented on May 2, 2017

    @madmas

    @JSoko Thanks a lot for the hint, wasn't aware of that mechanism! #893 would definitely be an improvement!

  8. tobiasKaminsky commented on Jun 26, 2017

    @tobiasKaminsky
    Member

    In the latest dev version there is already #1099 which will make the login work again.
    Please test it and if it is not working, re-open issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions