You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you were performing an action on the app from the webadmin or the CLI (install, update, backup, restore, change_url...), you are on the right place!
Otherwise, the issue may be due to the app itself. Refer to its documentation or repository for help.
When in doubt, post here and we will figure it out together.
Delete the italic comments as you write over them below, and remove this guide.
Describe the bug
When I try to save mail attachments with "Save to Files" from Mail app, nothing happens
Context
Hardware: AMD Ryzen 3 with 32 GB of RAM
YunoHost version: 11.2.11.3
I have access to my server: through ssh
Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: I installed sslh to share port 443 betweeen https and openvpn, changed the port in conf.d/nginx.domain.conf to 444
Using, or trying to install package version/branch:
If upgrading, current package version: 28.0.5~ynh1
Steps to reproduce
Install and open Mail app
Register imap account (Gmail) with app password
filnd the mail with attachments
try to save the attachment as Save to Files
Expected behavior
Dialog opens and I save the files to some folder on the Nextcloud server
Logs
Nothing concerning the mail app shows in the logs. This dialog appears, e.g., in files app when I try to move or copy files to another location
The text was updated successfully, but these errors were encountered:
How to post a meaningful bug report
Describe the bug
When I try to save mail attachments with "Save to Files" from Mail app, nothing happens
Context
Steps to reproduce
Expected behavior
Dialog opens and I save the files to some folder on the Nextcloud server
Logs
Nothing concerning the mail app shows in the logs. This dialog appears, e.g., in files app when I try to move or copy files to another location
The text was updated successfully, but these errors were encountered: