-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
WebDav connection having massive issues with Guzzle after previously have no issues. #12296
Comments
GitMate.io thinks possibly related issues are #3738 (Webdav), #12042 (WebDav issue with One Drive), #11804 (https windows webdav issue ), #8570 (Activation of server side end-to-end encryption creates issue for webdav connection with Cryptomator), and #7964 (Performance issues with WebDav (remote.php)). |
It could be that you are banned by our bruteforce protection. Check the Also the guzzle exception comes from the grdive app not being properly compatible with NC14. Disable it and it should go away. |
@rullzer I don't have gdrive on my server. You can see that from the list of enabled apps in my issue report. I also tried turning off bruteforce protection and that did not fix it. It's fixed now but whatever happened wasn't either of those things. |
Yes you do: files_external_gdrive |
@rullzer Ah dang, whoops. Missed that. Apologies. Also it just did it again. I found a way to fix it though. I just login through an icognito browser and suddenly it works fine? Could that be related to the bruteforce thing? |
SHould be fixed nowadays, the lib received lots of fixes and update |
Steps to reproduce
I set up a folder sync connection for my phone and my nextcloud server using the app FolderSync. It worked fine. Now it is unable to connect, but I am able to reach my nextcloud connection through my browser and desktop client no problems. I am unable to access it through the webdav connection I have on my phone through Solid Explorer or the FolderSync connection. Also I should note that earlier today I did misconfigure my first foldersync and that lead to my IP getting banned by fail2ban but I fixed that and just checked my fail2ban status and it is totally clear.
Expected behaviour
I would expect it to connect no issue.
Actual behaviour
It does not connection
Server configuration detail
Operating system: Linux 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 x86_64
Webserver: nginx/1.14.0 (fpm-fcgi)
Database: mysql 10.1.34
PHP version:
7.2.11-4+ubuntu18.04.1+deb.sury.org+1
Modules loaded: Core, date, libxml, openssl, pcre, zlib, filter, hash, Reflection, SPL, sodium, session, standard, cgi-fcgi, mysqlnd, PDO, xml, apcu, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, iconv, igbinary, imagick, intl, json, exif, mysqli, pdo_mysql, apc, posix, readline, redis, shmop, SimpleXML, smbclient, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xmlreader, xmlwriter, xsl, zip, Phar, libsmbclient, Zend OPcache
Nextcloud version: 14.0.3 - 14.0.3.0
Updated from an older Nextcloud/ownCloud or fresh install:
Where did you install Nextcloud from: official website using Reiner Nippes ansible script
Signing status
Array
(
)
List of activated apps
Configuration (config/config.php)
Are you using external storage, if yes which one: local/smb/sftp/...
Are you using encryption:
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Client configuration
Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0
Operating system: Ubuntu 18.04
Logs
Browser log
Nextcloud log
Browser log
EDIT: I have additional information! It appears to be related to an inability to log in under my normal user name?
When I try to login under my non-admin user through a browser I get blocked! This is the same user being used by the client too. Perhaps the web dav folder sync sent so many requests that it got flagged as spam or ddos or something? I'm going to try and creating a new user with the same privileges and see what that does.
The server was unable to complete your request.
If this happens again, please send the technical details below to the server administrator.
EDIT2: It started working again? I created a new user and then I needed to impersonate my non-admin user to share their folders over with the new fake user and when I did I was like "huh... this is just like logging in. Is impersonating just logging in? Can I now log in?" so I opened an incognito tab in my browser and now I can log in and the folder sync works! WHY????
Here's the latest logs. Maybe they shed light on this:
The text was updated successfully, but these errors were encountered: