-
Notifications
You must be signed in to change notification settings - Fork 37
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
Regression: Infected Files Now Yield "An unknown error has occurred" Instead of Appropriate Message #119
Comments
One wrinkle in my new setup I did not have with Nextcloud 15.0.2 is that we are now behind the Kubernetes NGinx ingress controller. It may be the case that the ingress controller is not sending along the response body for the 415 response; I am not sure how to get to the bottom of this yet. More coming soon I hope. |
I checked but do not think ingress is to blame here. |
Nextcloud: 16.0.5 |
Same here. nextcloud version 18.0.3 |
Adding my own logs here in hopes this gets fixed. Steps to reproduce
Expected behaviour
Actual behaviour
Server configuration detailOperating system: Linux 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 Webserver: Apache (fpm-fcgi) Database: pgsql PostgreSQL 12.4 (Ubuntu 12.4-0ubuntu0.20.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0, 64-bit PHP version: 7.4.3 Nextcloud version: 19.0.3 - 19.0.3.1 Updated from an older Nextcloud/ownCloud or fresh install: Fresh Install Where did you install Nextcloud from: nextcloud/vm Signing statusArray List of activated apps
Configuration (config/config.php)
Are you using external storage, if yes which one: no Are you using encryption: no Are you using an external user-backend, if yes which one: no Client configurationBrowser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36 Operating system: Windows 10 Pro; Version 2004; Build 19041.338 LogsNextcloud loghttps://loveazure.cloud/s/fEnwFyN7Rb66t9W (needs mirror, I cannot guarantee availability on my own server) Browser logNo relevant logs. Just a bunch of jquery depreciation warnings that are present even in a fresh install |
@EmilyLove26 The choice between 'delete' and 'log only' applies to background scans (cron). For uploads by browser or sync client, there's no such choice. (Or, the docs are wrong) |
The fact is that there are 2 different jobs are implemented and not well documented.
|
Steps to reproduce
Expected behaviour
Actual behaviour
This is a regression from Nextcloud 15.0.2 in which the message appeared correctly.
Server configuration
Operating system: Debian Stretch
Web server: NGinx 1.15.9
Database: MariaDB
PHP version: 7.2.15
Nextcloud version: 15.0.5.3
Updated from an older Nextcloud/ownCloud or fresh install: Fresh install
Where did you install Nextcloud from: Docker image
List of activated apps
Nextcloud apps
Nextcloud configuration
Nextcloud config
Client configuration
Browser: Chrome 72.0.3626.109 (Official Build) (64-bit)
Operating system: Windows 10 17763.316
Logs
Nextcloud log (data/owncloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: