No directory and file access any more in Nexcloud website when enabling ebook app: Epub Viewer: solved

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

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 :heart:

Nextcloud version Nextcloud Hub 5 (27.0.2)
Operating system and version Linux 5.10.0-25-amd64 x86_64 on younohost

PHP

Version: 8.1.23

The issue you are facing:

Is this the first time you’ve seen this error?Y

Steps to replicate it:

Facing the problem that i cannot access Folders or files via file tab in the browser.
Files are accessible for instance in dash I can see and open a new file (note) but in File tab I cannot access the Notes folder. If I click around in Files Tab somehow i see some folders but cannot access them, sometimes I can go down one folder hierarchy but than it stops .
I am not sure if it hast to do with the upgrade to 27.0.2. or turn on the server encryption.
I upgraded first and than switched the server encryption on, but found out not until done both in browser → files that there is a problem.
so I can access files from other apps it seems just a problem within rights in File tab.

The output of your Nextcloud log in Admin > Logging:
the only repeating log in Logging is:
Error no app in context OCP\AutoloadNotAllowedException: Autoload path not allowed: /var/www/nextcloud/apps/epubviewer/lib/config.php

/var/www/nextcloud/lib/autoloader.php - line 166:

OC\Autoloader->isValidPath()

/var/www/nextcloud/apps/epubviewer/lib/Hooks.php - line 41:

OC\Autoloader->load()

/var/www/nextcloud/lib/private/legacy/OC_Hook.php - line 105:

OCA\Epubviewer\Hooks::announce_settings()

/var/www/nextcloud/lib/private/Template/JSConfigHelper.php - line 302:

OC_Hook::emit()

/var/www/nextcloud/core/Controller/OCJSController.php - line 86:

OC\Template\JSConfigHelper->getConfig()

/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 230:

OC\Core\Controller\OCJSController->getConfig()

/var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 137:

OC\AppFramework\Http\Dispatcher->executeController()

/var/www/nextcloud/lib/private/AppFramework/App.php - line 183:

OC\AppFramework\Http\Dispatcher->dispatch()

/var/www/nextcloud/lib/private/Route/Router.php - line 315:

OC\AppFramework\App::main()

/var/www/nextcloud/lib/base.php - line 1071:

OC\Route\Router->match()

/var/www/nextcloud/index.php - line 36:

OC::handleRequest()

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

PASTE HERE

The output of your Apache/nginx/system log in /var/log/____:
Which exactly do you need:
insgesamt 44500
drwxr-xr-x 18 root root 4096 3. Sep 00:00 .
drwxr-xr-x 13 root root 4096 29. Jan 2023 …
-rw-r–r-- 1 root root 4528 3. Sep 17:52 alternatives.log
-rw-r–r-- 1 root root 16432 31. Aug 20:37 alternatives.log.1
-rw-r–r-- 1 root root 467 20. Jun 18:28 alternatives.log.2.gz
-rw-r–r-- 1 root root 169 30. Mai 17:36 alternatives.log.3.gz
-rw-r–r-- 1 root root 733 26. Mai 15:10 alternatives.log.4.gz
-rw-r–r-- 1 root root 981 22. Feb 2023 alternatives.log.5.gz
-rw-r–r-- 1 root root 3678 29. Jan 2023 alternatives.log.6.gz
drwxr-xr-x 2 root root 4096 2. Sep 18:35 apt
-rw-r----- 1 root adm 791335 4. Sep 13:10 auth.log
-rw-r----- 1 root adm 5175697 3. Sep 00:00 auth.log.1
-rw-r----- 1 root adm 482634 27. Aug 00:00 auth.log.2.gz
-rw-r----- 1 root adm 351763 20. Aug 00:00 auth.log.3.gz
-rw-r----- 1 root adm 369938 13. Aug 00:00 auth.log.4.gz
-rw-rw---- 1 root utmp 1883136 4. Sep 12:05 btmp
-rw-rw---- 1 root utmp 21638400 31. Aug 23:58 btmp.1
-rw-r----- 1 root adm 75262 4. Sep 13:09 daemon.log
-rw-r----- 1 root adm 428243 3. Sep 00:00 daemon.log.1
-rw-r----- 1 root adm 9718 27. Aug 00:00 daemon.log.2.gz
-rw-r----- 1 root adm 8317 20. Aug 00:00 daemon.log.3.gz
-rw-r----- 1 root adm 8962 13. Aug 00:00 daemon.log.4.gz
-rw-r----- 1 root adm 166160 4. Sep 13:10 debug
-rw-r----- 1 root adm 586178 2. Sep 23:30 debug.1
-rw-r----- 1 root adm 12610 26. Aug 23:42 debug.2.gz
-rw-r----- 1 root adm 11425 19. Aug 23:45 debug.3.gz
-rw-r----- 1 root adm 11511 12. Aug 22:55 debug.4.gz
-rw-r–r-- 1 root root 43716 2. Sep 18:41 dpkg.log
-rw-r–r-- 1 root root 141201 31. Aug 20:50 dpkg.log.1
-rw-r–r-- 1 root root 3138 17. Jun 12:18 dpkg.log.2.gz
-rw-r–r-- 1 root root 7341 26. Mai 12:38 dpkg.log.3.gz
-rw-r–r-- 1 root root 6158 22. Feb 2023 dpkg.log.4.gz
-rw-r–r-- 1 root root 50910 29. Jan 2023 dpkg.log.5.gz
-rw-r----- 1 root adm 325045 4. Sep 12:32 fail2ban.log
-rw-r----- 1 root adm 2166556 2. Sep 23:54 fail2ban.log.1
-rw-r----- 1 root adm 236423 26. Aug 23:59 fail2ban.log.2.gz
-rw-r----- 1 root adm 171632 19. Aug 22:25 fail2ban.log.3.gz
-rw-r----- 1 root adm 160804 13. Aug 00:00 fail2ban.log.4.gz
-rw-r–r-- 1 root root 32000 31. Aug 11:54 faillog
-rw-r–r-- 1 root root 3106 31. Aug 11:55 fontconfig.log
drwxr-xr-x 3 root root 4096 29. Jan 2023 installer
drwxr-sr-x+ 3 root systemd-journal 4096 29. Jan 2023 journal
-rw-r----- 1 root adm 90829 3. Sep 19:43 kern.log
-rw-r----- 1 root adm 179862 2. Sep 22:00 kern.log.1
-rw-r----- 1 root adm 17639 31. Aug 23:42 kern.log.2.gz
-rw-r----- 1 root adm 34070 22. Jun 17:41 kern.log.3.gz
-rw-r----- 1 root adm 33908 19. Jun 10:35 kern.log.4.gz
-rw-rw-r-- 1 root utmp 294336 4. Sep 12:32 lastlog
-rw-r----- 1 root adm 0 6. Aug 00:00 mail.err
-rw-r----- 1 root adm 2982 1. Aug 19:19 mail.err.1
-rw-r----- 1 root adm 887 29. Jul 19:07 mail.err.2.gz
-rw-r----- 1 root adm 840 22. Jul 19:06 mail.err.3.gz
-rw-r----- 1 root adm 831 15. Jul 07:04 mail.err.4.gz
-rw-r----- 1 root adm 123025 4. Sep 12:50 mail.info
-rw-r----- 1 root adm 1419514 2. Sep 23:30 mail.info.1
-rw-r----- 1 root adm 70830 26. Aug 23:59 mail.info.2.gz
-rw-r----- 1 root adm 143532 19. Aug 23:45 mail.info.3.gz
-rw-r----- 1 root adm 133437 13. Aug 00:00 mail.info.4.gz
-rw-r----- 1 root adm 123025 4. Sep 12:50 mail.log
-rw-r----- 1 root adm 1419514 2. Sep 23:30 mail.log.1
-rw-r----- 1 root adm 70830 26. Aug 23:59 mail.log.2.gz
-rw-r----- 1 root adm 143532 19. Aug 23:45 mail.log.3.gz
-rw-r----- 1 root adm 133437 13. Aug 00:00 mail.log.4.gz
-rw-r----- 1 root adm 3763 4. Sep 12:34 mail.warn
-rw-r----- 1 root adm 17743 2. Sep 20:50 mail.warn.1
-rw-r----- 1 root adm 1988 26. Aug 20:54 mail.warn.2.gz
-rw-r----- 1 root adm 16284 19. Aug 23:33 mail.warn.3.gz
-rw-r----- 1 root adm 7244 12. Aug 23:38 mail.warn.4.gz
-rw-r----- 1 root adm 85310 3. Sep 19:43 messages
-rw-r----- 1 root adm 262533 2. Sep 22:00 messages.1
-rw-r----- 1 root adm 148 20. Aug 00:10 messages.2.gz
-rw-r----- 1 root adm 147 13. Aug 00:10 messages.3.gz
-rw-r----- 1 root adm 147 6. Aug 00:10 messages.4.gz
drwxr-x— 2 metronome adm 4096 4. Sep 00:00 metronome
drwxr-s— 2 mysql adm 4096 29. Jan 2023 mysql
drwxr-xr-x 2 root root 4096 22. Feb 2023 nextcloud
drwxr-xr-x+ 2 root adm 12288 4. Sep 00:00 nginx
drwxr-xr-x 2 ntp ntp 4096 23. Sep 2020 ntpstats
-rw------- 1 root root 637 4. Sep 07:12 php7.4-fpm.log
-rw------- 1 root root 4235 2. Sep 19:11 php7.4-fpm.log.1
-rw------- 1 root root 235 1. Jul 19:02 php7.4-fpm.log.10.gz
-rw------- 1 root root 359 24. Jun 19:03 php7.4-fpm.log.11.gz
-rw------- 1 root root 433 19. Jun 10:35 php7.4-fpm.log.12.gz
-rw------- 1 root root 243 26. Aug 19:02 php7.4-fpm.log.2.gz
-rw------- 1 root root 239 19. Aug 19:12 php7.4-fpm.log.3.gz
-rw------- 1 root root 244 12. Aug 19:03 php7.4-fpm.log.4.gz
-rw------- 1 root root 248 5. Aug 19:07 php7.4-fpm.log.5.gz
-rw------- 1 root root 236 29. Jul 19:07 php7.4-fpm.log.6.gz
-rw------- 1 root root 243 22. Jul 19:06 php7.4-fpm.log.7.gz
-rw------- 1 root root 242 15. Jul 19:12 php7.4-fpm.log.8.gz
-rw------- 1 root root 240 8. Jul 19:04 php7.4-fpm.log.9.gz
-rw------- 1 root root 2320 31. Aug 11:51 php8.0-fpm.log
-rw------- 1 root root 1456 26. Aug 19:02 php8.0-fpm.log.1
-rw------- 1 root root 357 24. Jun 19:03 php8.0-fpm.log.10.gz
-rw------- 1 root root 429 19. Jun 10:35 php8.0-fpm.log.11.gz
-rw------- 1 root root 246 10. Jun 19:12 php8.0-fpm.log.12.gz
-rw------- 1 root root 239 19. Aug 19:12 php8.0-fpm.log.2.gz
-rw------- 1 root root 244 12. Aug 19:03 php8.0-fpm.log.3.gz
-rw------- 1 root root 246 5. Aug 19:07 php8.0-fpm.log.4.gz
-rw------- 1 root root 240 29. Jul 19:07 php8.0-fpm.log.5.gz
-rw------- 1 root root 245 22. Jul 19:06 php8.0-fpm.log.6.gz
-rw------- 1 root root 238 15. Jul 19:12 php8.0-fpm.log.7.gz
-rw------- 1 root root 241 8. Jul 19:04 php8.0-fpm.log.8.gz
-rw------- 1 root root 235 1. Jul 19:02 php8.0-fpm.log.9.gz
-rw------- 1 root root 7965 4. Sep 10:54 php8.1-fpm.log
-rw------- 1 root root 16778 2. Sep 19:11 php8.1-fpm.log.1
-rw------- 1 root root 1043 1. Jul 19:02 php8.1-fpm.log.10.gz
-rw------- 1 root root 782 24. Jun 19:03 php8.1-fpm.log.11.gz
-rw------- 1 root root 628 19. Jun 10:35 php8.1-fpm.log.12.gz
-rw------- 1 root root 1673 26. Aug 19:57 php8.1-fpm.log.2.gz
-rw------- 1 root root 1849 19. Aug 19:12 php8.1-fpm.log.3.gz
-rw------- 1 root root 1327 12. Aug 19:03 php8.1-fpm.log.4.gz
-rw------- 1 root root 1310 5. Aug 19:07 php8.1-fpm.log.5.gz
-rw------- 1 root root 1284 29. Jul 19:07 php8.1-fpm.log.6.gz
-rw------- 1 root root 917 22. Jul 19:06 php8.1-fpm.log.7.gz
-rw------- 1 root root 1085 15. Jul 19:12 php8.1-fpm.log.8.gz
-rw------- 1 root root 1429 8. Jul 19:04 php8.1-fpm.log.9.gz
-rw------- 1 root root 637 4. Sep 07:12 php8.2-fpm.log
-rw------- 1 root root 3681 2. Sep 19:11 php8.2-fpm.log.1
drwx------ 2 root root 4096 29. Jan 2023 private
drwxr-s— 2 redis adm 4096 3. Sep 00:00 redis
drwxr-x— 2 _rspamd _rspamd 4096 4. Sep 00:00 rspamd
drwxr-xr-x 4 root root 4096 29. Jan 2023 runit
drwxr-x— 2 root adm 4096 9. Aug 2022 samba
lrwxrwxrwx 1 root root 26 29. Jan 2023 seafile → /opt/yunohost/seafile/logs
-rw-r----- 1 root adm 590336 4. Sep 13:10 syslog
-rw-r----- 1 root adm 3236078 3. Sep 00:00 syslog.1
-rw-r----- 1 root adm 147778 27. Aug 00:00 syslog.2.gz
-rw-r----- 1 root adm 226547 20. Aug 00:00 syslog.3.gz
-rw-r----- 1 root adm 216292 13. Aug 00:00 syslog.4.gz
drwxr-x— 2 root adm 4096 4. Sep 00:00 unattended-upgrades
-rw-r----- 1 root adm 150332 4. Sep 12:50 user.log
-rw-r----- 1 root adm 407487 2. Sep 23:30 user.log.1
-rw-r----- 1 root adm 9840 26. Aug 23:35 user.log.2.gz
-rw-r----- 1 root adm 9918 19. Aug 23:45 user.log.3.gz
-rw-r----- 1 root adm 9832 12. Aug 22:55 user.log.4.gz
drwxr-xr-x 2 vaultwarden vaultwarden 4096 29. Jan 2023 vaultwarden
-rw-rw-r-- 1 root utmp 65664 4. Sep 12:32 wtmp
drwxr-x— 3 root root 4096 3. Sep 00:00 yunohost

PASTE HERE

PASTE HERE


![image|690x320](upload://xBwltOMWRr8z351ZFULGXiICIBp.png)
can not even access on cli nextcloud and change user 
(to say here I am new to Nextcloud and linux and have to learn a lot)

PASTE HERE

I have a similar problem. I did a fresh install for a test nextcloud, Server fresh installed with Ubuntu 22.04. First everything was like expected (It’s not my first nextcloud instance, but the first running on own hardware). But after doing the recommended server tweaks (SSL, Memcache etc…) the Cloud ended up the way that the filkes app is completly empty, just the sidebar is visible. Clikcing on recent files and then back to main view brings the folders and files up, I can open the files, but not the folders.

After two days trial an error deleted the nextcloud folder and made a new install, with checking all needed preinstall things again. Worked also well until I activeted memcache, but that ssemed to be a redis problem (couldn’t create files or folders); so I took redis out and stuck with apcu only, filkes worked then. I kept rying around, installed apps, and after some time (20 minutes or so) I was checking the main settings and got new errors (caldav, carddav). I wanted to correkt that, but the entries in htaccess were there, Nevertheless I added the entries for webfinger and nodeinfo.

Restarted the server, and the files problem was there again. I already disabled most additional apps, but without success.

So I have no idea how to solve this or if it’s a problem especially with NC 27.0.2…

Edit: I don’t use encryption, so encryption won’t be the problem to my mind…

Additional to the problem, not being able to access folders or files from the File Tab
Today I found out that I cannot send e-mails any more
During setup before the update I was able to send a testmail, now the send button is greyed out
even when all credentials are in !

Hm, Mail works for me.

Interesting the first level is accessible I can open the pdf on the first level
but everything else in Browerser Files is locked:

Yes, my problem too. Do yoz see the files and folders when you open the files app or do you need to change the view first (like me) to see at least something? My first level folder seems to be empty, files and folders only spear if I click on recent files (what gas also no result), but clicking back on all files at least shows them then.

exactly the same behavior here,
If I select group folder first they show up
and afterwards then ticking on all files I get the result above not being able to go on level down.

The good question is why can I open the PDF and view so it seems the rights to view are set correct ON THE FIRST LEVEL of the Files Folder in WEBBROWSER!



If I select the notes folder RMT and select properties even that does not give any information the property window that appears on the right side is completely empty
So this means everything in the filesystem and even in the encryption on server side that is enabled , there is no problem otherwise the file wouldn’t be in the client decrypted and editable.

Just created a note and I can edit and write and it is saved.
If I go to my windows client directory I find in the notes directory the new sub category I created as a sub folder and can see edit and view the note!!

So to narrow down :slight_smile: I don’t believe any more that this is a problem with the server encryption.

Something has been messed up the the file rights in the www-data folder !!!

And es I already said send and receive used to work and has stopped as well.

So what is wrong with the update!

Please help somebody My family cannot access files any more!!

I found the solution, at least for me. Do you have the eBooks app installed? Disabeling that solved the problem. Maybe there ate other apps too, I’m not right through testing all Apps I want. But as I have these problems on a freshly installed server with a freshly installed Nextcloud and ran into the same problem ever and ever again I did another try and installed NC without Apps in setup process. I then installed only Apps from the recommend tab, and the problem was there again. So I disabled all apps and started a step by step process - enabling an app and look if files work, if yes enable the next one.

So as disabling apps doesn’t affect stored data simply deactivate/disable all apps and turn them active again with checking the behaviour of the files app after ever activation.

But as said above, if you have the eBook app active start with disabling these.

WTF!!
Cryx you are genius!
Thank you so much you saved my day!!!

Yes I could remember that I some-when clicked and installed it

So for every other user whom this screws up his nerves:
I disabled the frickin ebook app


and voila
I can access my files in nextcloud Webbrowser Files again

Thanks so much
Is there a process to log this as a bug, I am not familiar with!?
And I will change the topic line to this!

but ,
still I cannot send any e-mails any more

Send button stays always grey
even after disabling epub viewer

The epub viewer app got an update today. Our prevoius problem seems to be solved with that version, I can access all my files. But I also updated Nextcloud itself to 27.1 in the meantime.

Thanks I will test it as soon as possible,

Sorry to ask, but do you ever have experienced that first created user can send in the mail system of Nextcloud but later created ones (after an update!?) cannot!
Any idea?

Appreciate your knowledge

Mail app or from Admin settings?

Inside nextcloud:
From mail app of each user
older user can send and receive mails, (created in yunohost admin console) , activated and used inside NC some time ago,

newly created (or jjust activated inside NC ) don’t

new user created in yunohost and activated in NC (so credentials inside auto creation process for mail run through and accepted everything fine) but,
cannot send or receive mails
The last test was to activate the first user (admin) in NC Mail, because never used and
“he also cannot send and receive mails.”
Conclusion somewhere in between and update may be has gone something wrong within Nextcloud and the mail accounts now created or activated are not able to send or receive mails.

the other option do you mean this:

never touched it, but as you say now gonna try…

In the picture are the main settings for your instance to send mails for password resets, email 2FA, Email notifications. These can be done here or direct in config.php.

I never really used the mail client or setting up auot-mail-accounts, so I can’t help with that right now, sorry.

no problem, thank you for your time to answer