Login fails "You took too long to login, please try again now"

Server
9

Using https instead of http resolved the same problem for me. It definitely the apache issue.

1 Like
10

I always get this error when trying to login using http: instead of https: .

11

Same here, this always happens if I don’t use HTTPS

12

Interesting. I would look for an open issue about that on GitHub in ownCloud repository.

13

I also see this message occasionally, although I always use HTTPS.

14

Seems there are various reasons for this to happen and quite some threads already exists about the same message:

With the following two a reinstall of the packages “worked”:

With this an update of PHP worked:

This seems to be unanswered but i just want to add a reference to it anyway:

15

FIXED !

I set CHMOD 777 to /var/lib/php/session and worked
Also, i didn`t had that folder, so i created it.
After that, clear cookies and works !

2 Likes
16

i get the error if i install the oauth2 app, when i uninstalled it it disappeared

17

What version of the app are you installing?

18

the one in the market store 0.23

19

Can you try the previous version?

20

will look for it and try

21

I had this problem when the certificate did not exactly match the hostname in the address bar. Try to add the hostname to your local hosts file.

Some browsers (e.g. Chrome) recently changed their behavior regarding subdomains. This could lead to the error message too.

22

Hi,
The issue comes when you don’t have space in your server to storing the data and to logged in your account.
Check your Hard Drive space in server.

1 Like
23

Great! Thanks!!! Finally I am in!

24

In my case, it was only happening in HTTP (HTTPS was ok), but I was needing HTTP for local use (without my domain https name). My config.php was like this:
‘trusted_domains’ =>
array (
0 => ‘192.168.1.170:8000’,
1 => ‘192.168.1.170:8443’,
2 => ‘mydomain.com:443’

And I solved it by removing repeated domain (with different port):
‘trusted_domains’ =>
array (
0 => ‘192.168.1.170’,
1 => ‘mydomain.com’

In fact, it seems that putting more than one domain with different port causes unexpected troubles, so it’s better to authorize the full domain without ports.

2 Likes
25

Hey,

thanks for posting this additional information / workaround.

The configuration setting is called “trusted_domains” and to my knowledge a port isn’t part of a domain so it might be expected that you don’t need to add a port there.

26

Adding in a small note, this could also happen if you’re out of disk space

27

Hi there,

|version|10.2.1.4|
|versionstring|10.2.1|

I received this ‘error’ today after having upgraded OC yesterday to latest version. I am running on VPS with Apache 2.4.x and php 7.2. In my case it was the cookie setting in Apache(!) which was causing this behaviour. My OC install is accessed using HTTP and I had just edited my Apache global config to always set secure cookies. And boom I couldn’t log into my OC with this message of taking too long. When I removed the ‘secure’ option in my Apache cookie setting it worked again.

Something for devs to have a look at :slight_smile:

Hope it helps others!

Regards,
Eric

1 Like
28

Hey,

nice that you have found this mis-configuration in your webserver.

From what i know the “secure” cookie disallows the transmission of this cookie over insecure HTTP connections. I’m not sure if a developer of ownCloud can do much about this. :slightly_frowning_face:

But maybe you could still notify them at https://github.com/owncloud/core/issues to see what they think about this?