Tu as l’extension Group Folder d’activée ?
Yes, we plan to implement that as an automated check.
1 Like
Oui, absolument, elle pose problème ?
Bon c’est un bug qui est relaté ici je pense:
This is what I do regularly, before and after Nextcloud updates.
Bonjour à tous, depuis le passage à NC hier soir v28.0.1, impossible d’uploader un fichier avec le “drag & drop”. Lorsque je glisse dans la fenêtre du dossier destinataire un fichier ‘xyz.pdf’ par exemple, il ne s’upload pas. J’ai une fenêtre “file:///C:/Users/USERNAME/Downloads/xyz.pdf” qui s’ouvre dans mon navigateur.
Même comportement dans Mozilla v115.6 et dans Edge v120.0.2210.133.
Vous avez une idée ?
Merci.
Hi everybody, since migration to NC v28.0.1 on yesterday evening, impossible to upload a file with “drag & drop” function. When I drag a file ‘xyz.pdf’ in the destination directory window, the file does not upload. A “file:///C:/Users/USERNAME/Downloads/xyz.pdf” window opens instead in my explorer.
Same comportment with Mozilla v115.6 and Edge v120.0.2210.133.
An idea ?
Thanks.
1 Like
Same problem here (never tested before).
121.0.1 (64 bits) on Linux Mint
Apparently known issue that will be fixed in 28.0.2
See
2 Likes
After the last update (28.0.2), a new error appears:
Server has no maintenance window start time configured. This means resource intensive daily background jobs will also be executed during your main usage time. We recommend to set it to a time of low usage, so users are less impacted by the load caused from these heavy tasks.
It seems that the problem is fixed by adding this line in config/config.json:
'maintenance_window_start' => 1,
Finally, the error related to an insufficient opcache.interned_strings_buffer value has reappeared 
Do you have the same?
Same here. Fixed in testing.
1 Like
What did you need to change the opcache value to? I’ve gone up to 1028 and it still doesn’t seem to be high enough, unless this message is just the result of a bug.
That line is fine… as long as you don’t mind heavy processes running on your server regularly at 1am UTC (8pm New York time, 5pm LA time). If this isn’t a good time to have heavy use of your server resources, then you might need to change the 1 to whatever UTC time works better for your particular users.
Yes, the same problem.
I don’t know what’s going on with Nextcloud updates, but there are errors.
The second-to-last one and this one.
Hello, me too…
For the fix 'maintenance_window_start' => 1, it works editing the config/config.php. I have try a lot of differents values with opcache in the /etc/php/8.2/fpm/pool.d/nextcloud.conf but it always want more for opcache.interned_strings_buffer… I put it back as origin, perhaps also it may be a false warning ?? not sure but it can be ?? There so many topics with this recurrent issue with opcache…
I think there are tons of problems with NC 28 for now to resolve before it becomes really stable, as we can see on the help.nextcloud.com
1 Like
Perhaps something wrong with the nginx conf ??
nginx -t
nginx: [warn] duplicate extension "js", content type: "text/javascript", previous content type: "application/javascript" in /etc/nginx/conf.d/nextcloud.domain.tld.d/nextcloud.conf:7
nginx: [warn] could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size
For the first advertisement I have commented in nextcloud.conf the lines…
But is a bad idea, don’t do it, I put it back as origin or I have an advertisement on NC
#include mime.types;
#types {
# text/javascript js mjs;
#}
for the second, I don’t understand what’s going on…
grep -r hash_* /etc/nginx/
/etc/nginx/conf.d/ssowat.conf:server_names_hash_bucket_size 128;
/etc/nginx/nginx.conf: types_hash_max_size 2048;
Ceci dit je découvre un réel ralentissement lorsque je me connecte en ssh ou en poussant des petits commits sur Forgejo…
Ok, bad idea about comment the first lines in the nginx nextcloud.conf, so I put it as origin…
Same thing, in my house too, he always wants more for opcache.interned_strings_buffer, I put it back by default.
My /etc/php/8.2/fpm/pool.d/nextcloud.conf has the entry
php_value[opcache.interned_strings_buffer]=32
but my Nextcloud instance showed a warning
The OPcache interned strings buffer is nearly full. To assure that repeating strings can be effectively cached, it is recommended to apply opcache.interned_strings_buffer to your PHP configuration with a value higher than 8.
Setting
opcache.interned_strings_buffer=32
in /etc/php/8.2/fpm/php.ini (it used the default value 8 before) and restarting the php8.2-fpm service removed the warning.
1 Like
yes, me also, this is the default parameter for this file…
I finally let it by default.
cat /etc/php/8.2/fpm/pool.d/nextcloud.conf | grep opcache
; php_value[opcache.enable]=1
; see here: https://docs.nextcloud.com/server/20/admin_manual/installation/server_tuning.html#enable-php-opcache
php_value[opcache.enable_cli]=1
php_value[opcache.interned_strings_buffer]=32
php_value[opcache.max_accelerated_files]=10000
php_value[opcache.memory_consumption]=128
php_value[opcache.save_comments]=1
php_value[opcache.revalidate_freq]=60
I have this command also
php8.2 -i | opcache
/etc/php/8.2/cli/conf.d/10-opcache.ini,
opcache.blacklist_filename => no value => no value
opcache.consistency_checks => 0 => 0
opcache.dups_fix => Off => Off
opcache.enable => On => On
opcache.enable_cli => Off => Off
opcache.enable_file_override => Off => Off
opcache.error_log => no value => no value
opcache.file_cache => no value => no value
opcache.file_cache_consistency_checks => On => On
opcache.file_cache_only => Off => Off
opcache.file_update_protection => 2 => 2
opcache.force_restart_timeout => 180 => 180
opcache.huge_code_pages => Off => Off
opcache.interned_strings_buffer => 8 => 8
opcache.jit => no value => no value
opcache.jit_bisect_limit => 0 => 0
opcache.jit_blacklist_root_trace => 16 => 16
opcache.jit_blacklist_side_trace => 8 => 8
opcache.jit_buffer_size => 0 => 0
opcache.jit_debug => 0 => 0
opcache.jit_hot_func => 127 => 127
opcache.jit_hot_loop => 64 => 64
opcache.jit_hot_return => 8 => 8
opcache.jit_hot_side_exit => 8 => 8
opcache.jit_max_exit_counters => 8192 => 8192
opcache.jit_max_loop_unrolls => 8 => 8
opcache.jit_max_polymorphic_calls => 2 => 2
opcache.jit_max_recursive_calls => 2 => 2
opcache.jit_max_recursive_returns => 2 => 2
opcache.jit_max_root_traces => 1024 => 1024
opcache.jit_max_side_traces => 128 => 128
opcache.jit_prof_threshold => 0.005 => 0.005
opcache.lockfile_path => /tmp => /tmp
opcache.log_verbosity_level => 1 => 1
opcache.max_accelerated_files => 10000 => 10000
opcache.max_file_size => 0 => 0
opcache.max_wasted_percentage => 5 => 5
opcache.memory_consumption => 128 => 128
opcache.opt_debug_level => 0 => 0
opcache.optimization_level => 0x7FFEBFFF => 0x7FFEBFFF
opcache.preferred_memory_model => no value => no value
opcache.preload => no value => no value
opcache.preload_user => no value => no value
opcache.protect_memory => Off => Off
opcache.record_warnings => Off => Off
opcache.restrict_api => no value => no value
opcache.revalidate_freq => 2 => 2
opcache.revalidate_path => Off => Off
opcache.save_comments => On => On
opcache.use_cwd => On => On
opcache.validate_permission => Off => Off
opcache.validate_root => Off => Off
opcache.validate_timestamps => On => On
Is it same for you ?
Yes, it’s the same for me.