# After v.33.0.3 upgrade: Apache reports "autoindex:error"; "File sequence directory exists but is not writable"

**URL:** <https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920>\
**Category:** ℹ️ Support\
**Tags:** nc33, apache\
**Created:** [May 27, 2026, 11:13pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920 "2026-05-27T23:13:51Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![4slam](https://help.nextcloud.com/user_avatar/help.nextcloud.com/4slam/32/39662_2.png) [@4slam](https://help.nextcloud.com/u/4slam)\
**Post date:** [May 27, 2026, 11:13pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/1 "2026-05-27T23:13:51Z")

</div>

> **Support intro**
>
> ## Sorry to hear you’re facing problems. 🙁
> 
> _The community help forum ([help.nextcloud.com](http://help.nextcloud.com)) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are **volunteering their time to help you.** _
> 
> **If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via [portal.nextcloud.com](http://portal.nextcloud.com) where Nextcloud engineers can help ensure your business keeps running smoothly.**
> 
> ## Getting help
> 
> In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
> 
> **Before clicking submit** : Please check if your query is already addressed via the following resources:
> 
> - [Official documentation](https://docs.nextcloud.com) (searchable and regularly updated)
> - [How to topics and FAQs](https://help.nextcloud.com/c/how-to-faqs/9)
> - [Forum search](https://help.nextcloud.com/search)
> 
> (Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. ❤

## The Basics

- Nextcloud Server version _(e.g., 29.x.x)_:
  - `33.0.3`

- Operating system and version _(e.g., Ubuntu 24.04)_:
  - FreeBSD 14.4

- Web server and version _(e.g, Apache 2.4.25)_:
  - Apache 2.4

- Reverse proxy and version \_(e.g. nginx 1.27.2)
  - `NA`

- PHP version _(e.g, 8.3)_:
  - `8.3`

- Is this the first time you’ve seen this error? (Yes / No):
  - `Yes`

- When did this problem seem to first start?
  - `When attempting to access the admin console immediately after successfully upgrading to v. 33.0.3`

- Installation method _(e.g. AlO, NCP, Bare Metal/Archive, etc.)_
  - `Command line`

- Are you using CloudfIare, mod\_security, or similar? _(Yes / No)_
  - `No`

### Summary of the issue you are facing:

“Internal Server Error” upon attempting to access the admin console after successfully upgrading to v. 33.0.3. Apache HTTP Server reports “autoindex:error”.

Error in `nextcloud.log`: “File sequence directory exists but is not writable.”

### Steps to replicate it (hint: details matter!):

1. Upgrade to Nextcloud 33.0.3 using CLI.

2. Upgrade command reports “Update successful”.

3. Turn off maintenance mode.

4. In a browser go to the URL of the installation (e.g., [domain.com/nextcloud](http://domain.com/nextcloud)).

5. The site reports an Internal Server Error.

### Log entries

#### Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the _Copy raw_ option from _Administration settings-\>Logging_ screen or from your `nextcloud.log` located in your data directory). Feel free to use a pastebin/gist service if necessary.

> _Entries from nextcloud.log with timestamps that coincided with the HTTP request that resulted in the error:_
> 
> [https://bin.disroot.org/?3c8006506acd572c#GJz6VjAMAhPCGr2Y72aNrYV2zPxobUiEw3t8a4TdHiKw](https://bin.disroot.org/?5e2bc79eadcbbb41#76ScS49LEGUEHrbeMkCJAYKSskDLdEgePfn2dM2f7G7h)

```auto
{"Exception":"Exception","Message":"File sequence directory exists but is not writable","Code":0,"Trace":[{"file":"/path/to/nextcloud/lib/private/Snowflake/FileSequence.php","line":32,"function":"ensureWorkdirExists","class":"OC\\Snowflake\\FileSequence","type":"->","args":[]}

```

#### Web Browser

If the problem is related to the Web interface, open your browser inspector _Console_ and _Network_ tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

> NA

```auto
PASTE

```

#### Web server / Reverse Proxy

The output of your Apache/nginx/system log in `/var/log/ ____ `:

> _Apache error log—the HTTP request that resulted in the error was made immediately after rotating the log:_
> 
> ```auto
> [Wed May 27 20:00:11.329633 2026] [autoindex:error] [pid 89502:tid 42608754556944] [client 209.6.113.125:0] AH01276: Cannot serve directory /path/to/nextcloud: No matching DirectoryIndex (none) found, and server-generated directory index forbidden by Options directive
> 
> ```

### Configuration

#### Nextcloud

The output of `occ config:list system` or similar is best, but, if not possible, the contents of your `config.php` file from `/path/to/nextcloud` is fine (make sure to remove any identifiable information!):

> _config.php:_
> 
> ```auto
> <?php
> $CONFIG = array (
> 'instanceid' => 'SCRUBBED',
> 'passwordsalt' => 'SCRUBBED',
> 'secret' => 'SCRUBBED',
> 'appstoreenabled' => false,
> 'config_is_read_only' => true,
> 'trusted_domains' =>
> array (
> 0 => 'domain.com',
> ),
> 'trusted_proxies' =>
> array (
> 0 => '192.168.0.0/16',
> ),
> 'datadirectory' => '/path/to/data',
> 'tempdirectory' => '/tmp/nextcloudtemp',
> 'log_type' => 'file',
> 'logfile' => '/path/to/data/nextcloud.log',
> 'logfilemode' => 432,
> 'loglevel' => 2,
> 'log.condition' =>
> array (
> 'apps' =>
> array (
> 0 => 'admin_audit',
> ),
> ),
> 'log_rotate_size' => 10485760,
> 'debug' => false,
> 'dbtype' => 'mysql',
> 'version' => '33.0.3.2',
> 'overwrite.cli.url' => 'https://domain.com/nextcloud',
> 'htaccess.RewriteBase' => '/nextcloud',
> 'dbname' => 'mydb',
> 'dbhost' => 'mydbhost',
> 'dbport' => 'mydbport',
> 'dbtableprefix' => 'oc_',
> 'mysql.utf8mb4' => true,
> 'dbuser' => 'mydbuser',
> 'dbpassword' => 'mydbpassword',
> 'installed' => true,
> 'mail_smtpmode' => 'sendmail',
> 'mail_sendmailmode' => 'smtp',
> 'mail_smtpdebug' => false,
> 'mail_smtpauthtype' => 'LOGIN',
> 'mail_smtphost' => '127.0.0.1',
> 'mail_smtpport' => '25',
> 'mail_smtptimeout' => 10,
> 'trashbin_retention_obligation' => 'auto, 30',
> 'twofactor_enforced' => 'true',
> 'twofactor_enforced_groups' =>
> array (
> 0 => 'group0',
> 1 => 'group1',
> ),
> 'twofactor_enforced_excluded_groups' =>
> array (
> ),
> 'maintenance' => false,
> 'has_rebuilt_cache' => true,
> 'theme' => '',
> 'mail_from_address' => 'adminuser',
> 'mail_domain' => 'domain.com',
> );
> 
> ```

#### Apps

The output of `occ app:list` (if possible).

> `Enabled: `  
> `- activity: 6.0.0`  
> `- admin_audit: 1.23.0`  
> `- app_api: 33.0.0`  
> `- bookmarks: 16.1.4`  
> `- bruteforcesettings: 6.0.0`  
> `- calendar: 6.4.2`  
> `- circles: 33.0.0`  
> `- cloud_federation_api: 1.17.0`  
> `- comments: 1.23.0`  
> `- contacts: 8.5.1`  
> `- contactsinteraction: 1.14.1`  
> `- dashboard: 7.13.0`  
> `- dav: 1.36.0`  
> `- federatedfilesharing: 1.23.0`  
> `- federation: 1.23.0`  
> `- files: 2.5.0`  
> `- files_downloadlimit: 5.1.0`  
> `- files_pdfviewer: 6.0.0`  
> `- files_reminders: 1.6.0`  
> `- files_sharing: 1.25.2`  
> `- files_trashbin: 1.23.0`  
> `- files_versions: 1.26.0`  
> `- firstrunwizard: 6.0.0`  
> `- logreader: 6.0.0`  
> `- lookup_server_connector: 1.21.0`  
> `- news: 28.4.1`  
> `- nextcloud_announcements: 5.0.0`  
> `- notes: 5.0.0`  
> `- notifications: 6.0.0`  
> `- oauth2: 1.21.0`  
> `- password_policy: 5.0.0`  
> `- photos: 6.0.0`  
> `- privacy: 5.0.0`  
> `- profile: 1.2.0`  
> `- provisioning_api: 1.23.0`  
> `- qownnotesapi: 26.2.2`  
> `- recommendations: 6.0.0`  
> `- related_resources: 4.0.0`  
> `- serverinfo: 5.0.0`  
> `- settings: 1.16.0`  
> `- sharebymail: 1.23.0`  
> `- support: 5.0.0`  
> `- survey_client: 5.0.0`  
> `- suspicious_login: 11.0.0`  
> `- systemtags: 1.23.0`  
> `- tasks: 0.17.1`  
> `- text: 7.0.1`  
> `- theming: 2.8.0`  
> `- twofactor_backupcodes: 1.22.0`  
> `- twofactor_totp: 15.0.0`  
> `- updatenotification: 1.23.0`  
> `- user_status: 1.13.0`  
> `- viewer: 6.0.0`  
> `- weather_status: 1.13.0`  
> `- webhook_listeners: 1.5.0`  
> `- workflowengine: 2.15.0`  
> `Disabled: `  
> `- encryption: 2.21.0`  
> `- files_external: 1.25.1`  
> `- testing: 1.23.0`  
> `- twofactor_nextcloud_notification: 7.0.0 (installed 2.3.0)`  
> ` - user_ldap: 1.24.0`

### Tips for increasing the likelihood of a response

- Use the `preformatted text` formatting option in the editor for all log entries and configuration output.
- If screenshots are useful, feel free to include them.
  - If possible, also include key error output in text form so it can be searched for.

- Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

---

<div class="post-metadata">

**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtr](https://help.nextcloud.com/u/jtr)\
**Post date:** [May 29, 2026, 4:27pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/2 "2026-05-29T16:27:48Z")

</div>

> [@4slam](#):
>
> ```auto
> [Wed May 27 20:00:11.329633 2026] [autoindex:error] [pid 89502:tid 42608754556944] [client 209.6.113.125:0] AH01276: Cannot serve directory /path/to/nextcloud: No matching DirectoryIndex (none) found, and server-generated directory index forbidden by Options directive
> 
> ```

Are you certain upgrading to v33.0.3 is the only change? No PHP, OS, or web server/Apache changes/upgrades?

It’s expected that auto-indexing won’t work; but that’s because Nextcloud’s entrypoint should be loaded.

The most suspicious part of your output is this:

`No matching DirectoryIndex (none) found`

That suggests the `DirectoryIndex` value isn’t getting populated. Nextcloud comes with an `.htaccess` for Apache. It’s possible to prevent it from being used in your web server configuration, but that wouldn’t be triggered by just upgrading Nextcloud itself.

---

<div class="post-metadata">

**Author:** ![4slam](https://help.nextcloud.com/user_avatar/help.nextcloud.com/4slam/32/39662_2.png) [@4slam](https://help.nextcloud.com/u/4slam)\
**Post date:** [May 29, 2026, 8:04pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/3 "2026-05-29T20:04:12Z")

</div>

> [@jtr](#):
>
> Are you certain upgrading to v33.0.3 is the only change? No PHP, OS, or web server/Apache changes/upgrades?

None of that has changed since I upgraded to v.32.0.9, all was well after that upgrade. I upgraded to v.33.0.3 about a week later and ran into this issue immediately.

I cannot directly edit Apache config files except for the .htaccess files under the web root. My custom directives in those files:

> **[Disroot Bin - Encrypted pastebin by PrivateBin](https://bin.disroot.org/?0bf91c85788a4668#BoGfMkYRFSDxkTdW2Y9zsJmdja1JcvUrCGKwG2SKNHSD)**
>
> Visit this link to see the note. Giving the URL to anyone allows them to access the note, too.

---

<div class="post-metadata">

**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtr](https://help.nextcloud.com/u/jtr)\
**Post date:** [May 29, 2026, 8:29pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/4 "2026-05-29T20:29:44Z")

</div>

Based on your earlier Nextcloud log this part:

> `File sequence directory exists but is not writable`

Sounds like an issue with your Snowflake IDs in v33.

Do you have multiple installations? Or maybe somehow ran the Updater as a different user than your web/PHP user?

> <https://github.com/nextcloud/server/issues/58416>
>
> \### ⚠️ This issue respects the following points: ⚠️
> 
> \- \[x\] This is a \*\*bug\*\*, no…t a question or a configuration/webserver/proxy issue.
> \- \[x\] This issue is \*\*not\*\* already reported on \[Github\](https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3Abug) OR \[Nextcloud Community Forum\](https://help.nextcloud.com/) \_(I've searched it)\_.
> \- \[x\] Nextcloud Server \*\*is\*\* up to date. See \[Maintenance and Release Schedule\](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) for supported versions.
> \- \[x\] I agree to follow Nextcloud's \[Code of Conduct\](https://nextcloud.com/contribute/code-of-conduct/).
> 
> \### Bug description
> 
> When trying to update NC to 33.0.0 via updater.phar a issue arises with shared temp-directories on servers running multiple installations with different uid/gid as the directory /tmp/sfi\_file\_sequence/ (that already was created by a different installation) is not writable.
> 
> This seems to be related to the commit 65c9e346da0610476ad2d599a24536fed41c6f1f as this is now checking for file permissions.
> 
> Manually setting a tempdirectory in config.php to eg $datadirectory/temp fixes the issue.
> 
> \`\`\`
> An unhandled exception has been thrown:
> Exception: File sequence directory exists but is not writable in /home/REDACTED/lib/private/Snowflake/FileSequence.php:37
> Stack trace:
> \#0 /home/REDACTED/lib/private/Snowflake/FileSequence.php(31): OC\\Snowflake\\FileSequence-\>ensureWorkdirExists()
> \#1 \[internal function\]: OC\\Snowflake\\FileSequence-\>\_\_construct()
> \#2 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(74): ReflectionClass-\>newInstanceArgs()
> \#3 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(131): OC\\AppFramework\\Utility\\SimpleContainer-\>buildClass()
> \#4 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(157): OC\\AppFramework\\Utility\\SimpleContainer-\>resolve()
> \#5 /home/REDACTED/lib/private/ServerContainer.php(155): OC\\AppFramework\\Utility\\SimpleContainer-\>query()
> \#6 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(46): OC\\ServerContainer-\>query()
> \#7 /home/REDACTED/lib/private/Server.php(1277): OC\\AppFramework\\Utility\\SimpleContainer-\>get()
> \#8 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(186): OC\\Server-\>OC\\{closure}()
> \#9 /home/REDACTED/3rdparty/pimple/pimple/src/Pimple/Container.php(118): OC\\AppFramework\\Utility\\SimpleContainer-\>OC\\AppFramework\\Utility\\{closure}()
> \#10 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(149): Pimple\\Container-\>offsetGet()
> \#11 /home/REDACTED/lib/private/ServerContainer.php(155): OC\\AppFramework\\Utility\\SimpleContainer-\>query()
> \#12 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(95): OC\\ServerContainer-\>query()
> \#13 \[internal function\]: OC\\AppFramework\\Utility\\SimpleContainer-\>OC\\AppFramework\\Utility\\{closure}()
> \#14 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(82): array\_map()
> \#15 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(74): OC\\AppFramework\\Utility\\SimpleContainer-\>buildClassConstructorParameters()
> \#16 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(131): OC\\AppFramework\\Utility\\SimpleContainer-\>buildClass()
> \#17 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(157): OC\\AppFramework\\Utility\\SimpleContainer-\>resolve()
> \#18 /home/REDACTED/lib/private/ServerContainer.php(155): OC\\AppFramework\\Utility\\SimpleContainer-\>query()
> \#19 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(46): OC\\ServerContainer-\>query()
> \#20 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(208): OC\\AppFramework\\Utility\\SimpleContainer-\>get()
> \#21 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(186): OC\\AppFramework\\Utility\\SimpleContainer-\>OC\\AppFramework\\Utility\\{closure}()
> \#22 /home/REDACTED/3rdparty/pimple/pimple/src/Pimple/Container.php(118): OC\\AppFramework\\Utility\\SimpleContainer-\>OC\\AppFramework\\Utility\\{closure}()
> \#23 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(149): Pimple\\Container-\>offsetGet()
> \#24 /home/REDACTED/lib/private/ServerContainer.php(155): OC\\AppFramework\\Utility\\SimpleContainer-\>query()
> \#25 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(95): OC\\ServerContainer-\>query()
> \#26 \[internal function\]: OC\\AppFramework\\Utility\\SimpleContainer-\>OC\\AppFramework\\Utility\\{closure}()
> \#27 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(82): array\_map()
> \#28 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(74): OC\\AppFramework\\Utility\\SimpleContainer-\>buildClassConstructorParameters()
> \#29 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(131): OC\\AppFramework\\Utility\\SimpleContainer-\>buildClass()
> \#30 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(157): OC\\AppFramework\\Utility\\SimpleContainer-\>resolve()
> \#31 /home/REDACTED/lib/private/ServerContainer.php(155): OC\\AppFramework\\Utility\\SimpleContainer-\>query()
> \#32 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(46): OC\\ServerContainer-\>query()
> \#33 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(208): OC\\AppFramework\\Utility\\SimpleContainer-\>get()
> \#34 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(186): OC\\AppFramework\\Utility\\SimpleContainer-\>OC\\AppFramework\\Utility\\{closure}()
> \#35 /home/REDACTED/3rdparty/pimple/pimple/src/Pimple/Container.php(118): OC\\AppFramework\\Utility\\SimpleContainer-\>OC\\AppFramework\\Utility\\{closure}()
> \#36 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(149): Pimple\\Container-\>offsetGet()
> \#37 /home/REDACTED/lib/private/ServerContainer.php(155): OC\\AppFramework\\Utility\\SimpleContainer-\>query()
> \#38 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(95): OC\\ServerContainer-\>query()
> \#39 \[internal function\]: OC\\AppFramework\\Utility\\SimpleContainer-\>OC\\AppFramework\\Utility\\{closure}()
> \#40 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(82): array\_map()
> \#41 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(74): OC\\AppFramework\\Utility\\SimpleContainer-\>buildClassConstructorParameters()
> \#42 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(131): OC\\AppFramework\\Utility\\SimpleContainer-\>buildClass()
> \#43 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(157): OC\\AppFramework\\Utility\\SimpleContainer-\>resolve()
> \#44 /home/REDACTED/lib/private/ServerContainer.php(155): OC\\AppFramework\\Utility\\SimpleContainer-\>query()
> \#45 /home/REDACTED/lib/private/AppFramework/Utility/SimpleContainer.php(46): OC\\ServerContainer-\>query()
> \#46 /home/REDACTED/lib/public/Server.php(37): OC\\AppFramework\\Utility\\SimpleContainer-\>get()
> \#47 /home/REDACTED/core/register\_command.php(142): OCP\\Server::get()
> \#48 /home/REDACTED/lib/private/Console/Application.php(83): require\_once('...')
> \#49 /home/REDACTED/console.php(86): OC\\Console\\Application-\>loadCommands()
> \#50 /home/REDACTED/occ(33): require\_once('...')
> \#51 {main}
> 
> \`\`\`
> 
> \### Steps to reproduce
> 
> Try to update existing installation of NC \<33 on a server with shared temp-Directory (and unset tempdirectory in config.php) via updater.phar
> 
> \### Expected behavior
> 
> Use unique tempnam instead of fixed directory name or private temp-directory within datadirectory as default
> 
> \### Nextcloud Server version
> 
> 33
> 
> \### Operating system
> 
> RHEL/CentOS
> 
> \### PHP engine version
> 
> PHP 8.3
> 
> \### Web server
> 
> Apache (supported)
> 
> \### Database engine version
> 
> MariaDB
> 
> \### Is this bug present after an update or on a fresh install?
> 
> Upgraded to a MAJOR version (ex. 31 to 32)
> 
> \### Are you using the Nextcloud Server Encryption module?
> 
> Encryption is Disabled
> 
> \### What user-backends are you using?
> 
> \- \[x\] Default user-backend \_(database)\_
> \- \[\] LDAP/ Active Directory
> \- \[\] SSO - SAML
> \- \[\] Other
> 
> \### Configuration report
> 
> \`\`\`json
> {
> "system": {
> "instanceid": "\*\*\*REMOVED SENSITIVE VALUE\*\*\*",
> "passwordsalt": "\*\*\*REMOVED SENSITIVE VALUE\*\*\*",
> "secret": "\*\*\*REMOVED SENSITIVE VALUE\*\*\*",
> "trusted\_domains": \[
> "REDACTED"
> \],
> "datadirectory": "\*\*\*REMOVED SENSITIVE VALUE\*\*\*",
> "dbtype": "mysql",
> "version": "32.0.6.1",
> "overwrite.cli.url": "https:\\/\\/REDACTED",
> "dbname": "\*\*\*REMOVED SENSITIVE VALUE\*\*\*",
> "dbhost": "\*\*\*REMOVED SENSITIVE VALUE\*\*\*",
> "dbport": "",
> "dbtableprefix": "oc\_",
> "mysql.utf8mb4": true,
> "dbuser": "\*\*\*REMOVED SENSITIVE VALUE\*\*\*",
> "dbpassword": "\*\*\*REMOVED SENSITIVE VALUE\*\*\*",
> "installed": true,
> "maintenance": true,
> "loglevel": 2
> }
> }
> \`\`\`
> 
> \### List of activated Apps
> 
> \`\`\`shell
> Enabled:
> - activity: 5.0.0
> - app\_api: 32.0.0
> - bruteforcesettings: 5.0.0
> - calendar: 6.2.0
> - circles: 32.0.0
> - cloud\_federation\_api: 1.16.0
> - comments: 1.22.0
> - contacts: 8.3.2
> - contactsinteraction: 1.13.1
> - dashboard: 7.12.0
> - dav: 1.34.2
> - federatedfilesharing: 1.22.0
> - federation: 1.22.0
> - files: 2.4.0
> - files\_downloadlimit: 5.0.0-dev.0
> - files\_pdfviewer: 5.0.0
> - files\_reminders: 1.5.0
> - files\_sharing: 1.24.1
> - files\_trashbin: 1.22.0
> - files\_versions: 1.25.0
> - firstrunwizard: 5.0.0
> - logreader: 5.0.0
> - lookup\_server\_connector: 1.20.0
> - mail: 5.7.0
> - nextcloud\_announcements: 4.0.0
> - notes: 4.13.0
> - notifications: 5.0.0
> - oauth2: 1.20.0
> - password\_policy: 4.0.0
> - photos: 5.0.0
> - privacy: 4.0.0
> - profile: 1.1.0
> - provisioning\_api: 1.22.0
> - recommendations: 5.0.0
> - related\_resources: 3.0.0
> - serverinfo: 4.0.0
> - settings: 1.15.1
> - sharebymail: 1.22.0
> - support: 4.0.0
> - survey\_client: 4.0.0
> - suspicious\_login: 10.0.0
> - systemtags: 1.22.0
> - text: 6.0.1
> - theming: 2.7.0
> - twofactor\_backupcodes: 1.21.0
> - twofactor\_totp: 14.0.0
> - updatenotification: 1.22.0
> - user\_status: 1.12.0
> - viewer: 5.0.0
> - weather\_status: 1.12.0
> - webhook\_listeners: 1.3.0
> - workflowengine: 2.14.0
> Disabled:
> - admin\_audit: 1.23.0
> - deck: 1.16.3 (installed 1.16.3)
> - encryption: 2.21.0
> - files\_external: 1.25.1
> - forms: 5.2.4 (installed 5.2.4)
> - tasks: 0.17.1 (installed 0.17.1)
> - twofactor\_nextcloud\_notification: 7.0.0
> - user\_ldap: 1.24.0
> \`\`\`
> 
> \### Nextcloud Signing status
> 
> \`\`\`shell
> 
> \`\`\`
> 
> \### Nextcloud Logs
> 
> \`\`\`json
> 
> \`\`\`
> 
> \### Additional info
> 
> \_No response\_

---

<div class="post-metadata">

**Author:** ![4slam](https://help.nextcloud.com/user_avatar/help.nextcloud.com/4slam/32/39662_2.png) [@4slam](https://help.nextcloud.com/u/4slam)\
**Post date:** [May 29, 2026, 9:29pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/5 "2026-05-29T21:29:25Z")

</div>

> [@jtr](#):
>
> Sounds like an issue with your Snowflake IDs in v33.

I suspected that.

I did encounter that bug during the upgrade. Following the solution in [this comment](https://github.com/nextcloud/server/issues/58416#issuecomment-4325228789), I gave _g+w_ permission to the `/tmp/nextcloudtemp/sfi_file_sequence_<instance>` directory (which was empty). I reran the upgrade after that and it reported success.

About my installation (I only have one):

- I always upgrade using the CLI (the `occ` command) through SSH. I can only run it as the SSH user, I cannot switch to the web user.
- My installation directories/files are owned by \<ssh\_user\>:\<web\_group\>; directory perms 750, file perms 640.
- I usually keep my `config` directory and `config.php` read-only for group (with the corresponding config setting set to `true`). ~~However, they are currently _g+w_, following the suggestion in the [aforementioned comment](https://github.com/nextcloud/server/issues/58416#issuecomment-4325228789).~~ `cron.php` has been running without errors.

Is there anything else I need to do to work around the issue with Snowflake IDs?

---

<div class="post-metadata">

**Author:** ![4slam](https://help.nextcloud.com/user_avatar/help.nextcloud.com/4slam/32/39662_2.png) [@4slam](https://help.nextcloud.com/u/4slam)\
**Post date:** [June 10, 2026, 7:28pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/6 "2026-06-10T19:28:41Z")

</div>

I was able to update to v.33.0.5, but the error persists. The [issue with the Snowflake IDs](https://github.com/nextcloud/server/issues/58416) is expected to be fixed in v.34 according to the [pull request for the bug fix](https://github.com/nextcloud/server/pull/58516).

Meanwhile, the web console and syncs (calendar, bookmarks, etc.) are broken, and I’m not sure if they will be fixed by the fix for the Snowflake IDs.

😢

---

<div class="post-metadata">

**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/5_5575768a8748004e209b776fc1b2916d.png) [@jtr](https://help.nextcloud.com/u/jtr)\
**Post date:** [June 10, 2026, 8:39pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/7 "2026-06-10T20:39:09Z")

</div>

> [@4slam](#):
>
> I was able to update to v.33.0.5, but the error persists. The [issue with the Snowflake IDs](https://github.com/nextcloud/server/issues/58416) is expected to be fixed in v.34 according to the [pull request for the bug fix](https://github.com/nextcloud/server/pull/58516).

That fix was backported already months ago and was in v33.0.1.

---

<div class="post-metadata">

**Author:** ![4slam](https://help.nextcloud.com/user_avatar/help.nextcloud.com/4slam/32/39662_2.png) [@4slam](https://help.nextcloud.com/u/4slam)\
**Post date:** [June 11, 2026, 5:18pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/8 "2026-06-11T17:18:48Z")

</div>

> [@jtr](#):
>
> That fix was backported already months ago and was in v33.0.1.

Thanks. In that case, I’ll report this as a new issue.

---

<div class="post-metadata">

**Author:** ![4slam](https://help.nextcloud.com/user_avatar/help.nextcloud.com/4slam/32/39662_2.png) [@4slam](https://help.nextcloud.com/u/4slam)\
**Post date:** [June 29, 2026, 7:53pm UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/9 "2026-06-29T19:53:06Z")

</div>

This issue persists after upgrading to v.34.0.1.  
😟

---

<div class="post-metadata">

**Author:** ![4slam](https://help.nextcloud.com/user_avatar/help.nextcloud.com/4slam/32/39662_2.png) [@4slam](https://help.nextcloud.com/u/4slam)\
**Post date:** [July 8, 2026, 12:22am UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/10 "2026-07-08T00:22:28Z")

</div>

The `/tmp/nextcloud/sfi_file_sequence_<instance>` directory and its contents need to be writable by the web server, as I said in [this comment](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/5). While I did make them writeable, I left the ownership of the `*.lock` files in `/tmp/nextcloud/sfi_file_sequence_<instance>` unchanged. I only checked this upon reading [this reply](https://github.com/nextcloud/server/issues/58416#issuecomment-4836360740) to my post under the related issue at GitHub. With those files now owned by \<ssh\_user\>:\<webserver\_group\> and _g+rw_ perms (770 for directory, 660 for files), the web console is working again.

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [July 16, 2026, 12:23am UTC](https://help.nextcloud.com/t/after-v-33-0-3-upgrade-apache-reports-autoindex-error-file-sequence-directory-exists-but-is-not-writable/244920/11 "2026-07-16T00:23:14Z")

</div>

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.