Skip to content
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

Mail App not working under Nextcloud 17.0.0 #2094

Closed
hillebr opened this issue Oct 10, 2019 · 9 comments
Closed

Mail App not working under Nextcloud 17.0.0 #2094

hillebr opened this issue Oct 10, 2019 · 9 comments

Comments

@hillebr
Copy link

hillebr commented Oct 10, 2019

Expected behavior

Maill app stopped loading Mails on all added accounts after update to Nextcloud 17.0.0
Removing and re-adding the app won't solve the issue
When starting the app, the circle keeps spinning an nothing happens (see attached schreenshot)
2019-10-10 14_56_24-E-Mail - Cloud

and the following error shows up in log:

Exception: The requested uri(/index.php/apps/mail/api/accounts/20/folders/SU5CT1g%3D/messages) cannot be processed by the script '/nextcloud/index.php')

/var/www/html/nextcloud/lib/base.php - line 943:

OC\AppFramework\Http\Request->getRawPathInfo()

/var/www/html/nextcloud/index.php - line 42:

OC::handleRequest()

Actual behavior

...it should just work as under Nexcloud 16.0.5

Mail app

Mail app version: 0.17.0

Mailserver or service: Gmail, web.de, t-online.de & own debian based mailserver

Server configuration

Operating system: Debian 9

Web server: Apache

Database: MariaDB 10.3.18

PHP version: 7.3.10

Nextcloud Version: 17.0.0

Client configuration

Browser: Firefox 69 but independent from browser type

Operating system: Windows 10

@ChristophWurst
Copy link
Member

Please share the line from nextcloud.log that pops up when this error is triggered.

@hillebr
Copy link
Author

hillebr commented Oct 11, 2019

{"reqId":"XaA5X38AAQEAACP0FkUAAAAB","level":3,"time":"2019-10-11T09:12:15+01:00","remoteAddr":"212.211.165.69","user":"rene","app":"index","method":"GET","url":"/index.php/apps/mail/api/accounts/20/folders/SU5CT1g%3D/messages","message":{"Exception":"Exception","Message":"The requested uri(/index.php/apps/mail/api/accounts/20/folders/SU5CT1g%3D/messages) cannot be processed by the script '/nextcloud/index.php')","Code":0,"Trace":[{"file":"/var/www/html/nextcloud/lib/base.php","line":943,"function":"getRawPathInfo","class":"OC\AppFramework\Http\Request","type":"->","args":[]},{"file":"/var/www/html/nextcloud/index.php","line":42,"function":"handleRequest","class":"OC","type":"::","args":[]}],"File":"/var/www/html/nextcloud/lib/private/AppFramework/Http/Request.php","Line":780,"CustomMessage":"--"},"userAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0","version":"17.0.0.9"}

@no-response no-response bot removed the needs info label Oct 11, 2019
@ChristophWurst
Copy link
Member

Related to nextcloud/server#11913 CarnetApp/CarnetNextcloud#14. Do you use that app?

@hillebr
Copy link
Author

hillebr commented Oct 11, 2019

No, I do not use the carnet app and I never did before.

@no-response no-response bot removed the needs info label Oct 11, 2019
@ChristophWurst
Copy link
Member

This is strange. I have never seen an error like this. Could you temporarily disable other 3rdparty apps?

@hillebr
Copy link
Author

hillebr commented Oct 11, 2019

I did but the issue is the same - even after reinstalling the Mail-App.
Maybe I have to reinstall my NC instance.
Could this error be related with a broken webbased update to 17.0.0?
After updating the files the webbased upgrade failed with a white browser tab.
I had to finish it with: sudo -u www-data php updater.phar
After that NC was running again except the Mail app...

@ChristophWurst
Copy link
Member

Any warning on your admin settings overview page? Does the integrity check pass?

@hillebr
Copy link
Author

hillebr commented Oct 11, 2019

...no warnings and yes, the check did pass!

@hillebr
Copy link
Author

hillebr commented Nov 11, 2019

Hi there,
after update to Nextcloud 17.0.1.1 the issue is fixed!

Thanks a lot!

René

@hillebr hillebr closed this as completed Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants