-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slow log out. #9179
Comments
I'm also observing this in NextCloud 13.0.7. Any hints what might be causing this? |
@gohrner |
I have a similar problem on nextcloud 14.0.3, and actually a even worse issue. |
I upgraded to NextCloud 14.03, same issue. Will check into the log-rotate setting above mentioned by @nextcloud-bot. The second click behavior mentioned still persists as well. Same applies to Nextcloud 14.04. This is after following steps in https://docs.nextcloud.com/server/14/admin_manual/issues/general_troubleshooting.html#service-discovery. |
In 14.04 this issue was solved to me :) |
For me the logout takes 15s (owncloud takes < 1s).
|
Logout takes really long some times (latest stable 15.x). In chromium, if I do 'empty cache and hard reload', logouts becomes fast again. |
Same issue and no solution found :-( |
Same issue in 15. I saw it in 14 too. Clicking the logout again after a few seconds wakes it up for me. |
Please open again, the problem persists. Nexcloud 15.0.6 Steps to reproduce:
Results (sign out duration, deterministic / reproducible):
|
Can you reproduce this with https://demo.nextcloud.com? |
Thanks for your quick response. Yes, I can reproduce the behaviour with the demo instance -- 9.92 s with Chrome and 368 ms with Safari. Here the header details of Chrome's logout request, if you have the change to see something in the logs of the demo instance: Request URL: https://demo.nextcloud.com/aeb9ouc9/logout?requesttoken=WRHtv%2BSN6UKbAyDm9VByvhAlsnZbkcgvCvgPw1d4l24%3D%3AFSOc67PVpBvDO2eLkB8l%2BlZMggQc3bpaPIhrpiIS8lg%3D |
The issue definitely isn't fixed, I observe it on both of my NextCloud instances, one using LDAP and the other not using LDAP. The problem persists since 13, is still present in 15.0.5 and simply hasn't been dealt with so far... |
Not sure why but logout with chrome is (much) slower than firefox. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
For those who can live with it and need a fast logout, just remove the cache clear from the |
I guess it's valid to have some config property to manage this behaviour. Feel free to take the above patch as start and submit a pull requests. Don't forget to update the tests: https://github.com/nextcloud/server/blob/master/core/Controller/LoginController.php |
+1 |
Please use GitHub Reactions for "+1" or "Same here". I've hidden most of the +1 posts to make reading easier ;)
The patch adds a way to disable the Clear-Site-Data header. You still need to modify your
With Clear-Site-Data header logout is much slower in chrome and browsers using the chrome engine. This needs to be fixed by chrome. The issue (slow logout if clear-site-data header is present) should to be fixed by chromium. There are multiple ways for you to get rid of this problem:
Thanks to all of you for helping with this issue 👍 |
This comment has been minimized.
This comment has been minimized.
I proposed a patch to disable the |
https://bugs.chromium.org/p/chromium/issues/detail?id=762417 here is a bug report for this issue. Can someone of you test it with a newer (>= 77) chrome version and confirm that the issue is fixed? |
I tested with the stable version (78) and it still happens. ~30sec to logout on a decent computer. |
With a fresh Nextcloud installation, the issue seems to be fixed \o/ (Build 78.0.3904.87, macOS 10.15.1). However, the logout is slow when testing with my old installation (both 16.0.5, same config.php/webserver/database). |
I tested on https://try.nextcloud.com/ so it cannot be fresher. However I am under Win 10 (but the exact same Chrome version). |
Nextcloud 18 will not send the clear site data header for chrome* browsers. * actually every browser that user agents matches |
I know this is closed, but the issue is still present in NextCloud 18.0.3 |
Hi. As mentioned, it's Chrome-related |
Broken again on NC27. |
Steps to reproduce
Expected behaviour
Log out should be as fast as log in. There should not be a delay to get out of the system.
Actual behaviour
I have two instances of Nextcloud (one mine, one is a friends). Both are V 13.1. Either may take anywhere from 5 to 30 seconds to achieve log out.
Server configuration
Operating system:
Ubuntu
Web server:
Apache2
Database:
MySQL
PHP version:
7.2
Nextcloud version: (see Nextcloud admin page)
13.1
Updated from an older Nextcloud/ownCloud or fresh install:
One of each
Where did you install Nextcloud from:
Web
Signing status:
Signing status
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Enabled:
Nextcloud configuration:
Config report
With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your Nextcloud installation folder
Without access to your command line download the data/owncloud.db to your local
computer or access your SQL server remotely and run the select query:
SELECT * FROM
oc_appconfig
WHEREappid
= 'user_ldap';Eventually replace sensitive data as the name/IP-address of your LDAP server or groups.
Nextcloud log (data/nextcloud.log)
Nextcloud log
{"reqId":"JTdr8OQ7ACQEgPi71sJ0","level":3,"time":"2018-04-13T17:23:54+00:00","remoteAddr":"71.48.121.114","user":"wjw","app":"PHP","method":"GET","url":"\/nextcloud\/index.php\/settings\/admin","message":"Cannot modify header information - headers already sent by (output started at \/var\/www\/nextcloud\/apps\/passman\/personal.php:1) at \/var\/www\/nextcloud\/lib\/private\/AppFramework\/Http\/Output.php#69","userAgent":"Mozilla\/5.0 (X11; Linux x86_64) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/65.0.3325.181 Safari\/537.36","version":"13.0.1.1"}Insert your Nextcloud log here
Browser log
Browser log
N/A
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
JQMIGRATE: Migrate is installed, version 1.4.0
12:32:08.990 DevTools failed to parse SourceMap: https://bobbi1.is-an-artist.net/nextcloud/core/vendor/purify.min.js.map
12:32:09.381 inject.js:324 Found 1 logins for this site
12:32:09.443 inject.js:324 Found 1 logins for this site
The text was updated successfully, but these errors were encountered: