scubamuc

@manticode, okay, so I'll reopen here and see what the devs say :+1:

@nextcloud-snap/developers > Actually I believe it is a snap issue. The config line in question should be parameterized in a way that it can be adjusted using Snap commands. wdyt

@manticode see [PHP configuration options](https://github.com/nextcloud-snap/nextcloud-snap/wiki/Configure-config.php) you could try something like ``` sudo nextcloud.occ config:system:set upload_tmp_dir --value=${SNAP_COMMON}/nextcloud/tmp ``` but I've not tried this... be sure to backup you config!

@manticode as far as I know changes to `/snap/nextcloud/current/config/php/php-fpm.d/www.conf ` are not possible unless you build your own snap. but lets wait for @kyrofa on this...

@JOpsDev welcome and thanks for your request so i've just recently tested a PR #2919 and could not reproduce your issue. i'm guessing this request should be placed upstream?

@JOpsDev thanks for your reply. The Nextcloud snap team packages a finished stable upstream Nextcloud, adds some snap magic, tests and releases that snap package. Since none of the Nextcloud...

@nextcloud-snap/developers do you have any ideas?

@JOpsDev thanks for trying to get to the bottom of this... but this is certainly not a snap issue. the collabora team would definitely appreciate your efforts. please consider posting...

The Nextcloud snap team tests and documents recommended default apps. Our documentation for [CODE & Nextcloud Office configuration](https://github.com/nextcloud-snap/nextcloud-snap/wiki/Configure-CODE-and-Nextcloud-office-for-Nextcloud-snap) is also part of the default fresh install snap testing. These tests...

@juliushaertl >The trace seems to come from the built-in CODE server autoconfiguration which I could imagine causing some concurrency issues thanks for the heads up... looking forward to 30 and...