Failed to open stream: Permission denied

[nebulon]

So /app/code is read-only in Cloudron, however /app/code/storage is linked into /app/data/, which is read-write. So the correct chown would be against /app/data/storage/ in this case. The startup code of the app does this already, which is why it works after a restart.

Then the question remains, who changes permissions on that cache folder. Do you have some custom cron job or so which may run as root maybe? Which plugins have you installed, which could interfere here?

[sebastienserre]

Hello @nebulon
I've a cron here:

Here the list of Freescout module:

In the Workflows, I only have rule like "if email is XXXX then apply tag XXXX"

[nebulon]

Ah I see, that custom cron is most likely the root case then, since it runs the scheduler as root instead of www-data. Either way the package already comes with this cron job: https://git.cloudron.io/packages/freescout-app/-/blob/master/cron.sh?ref_type=heads

So you should be fine with just removing your custom cron setting there, if I read that correctly, and that hopefully solves the issue.

[sebastienserre]

I've removed and will monitor few days .
Thanks

[sebastienserre]

Removed it and no emails are fetch.
What's strange is I'm checking the emails on the Sogo Webmail (on Cloudron) and the email is mark as read... but not available on Freescout

[nebulon]

Have you restarted the app after removing the cron job, just to make sure the permissions are all set correctly?

[sebastienserre]

The error gone thank you @nebulon

I now have an issue on mails which are not fetched
This is now like if Cron tasks were not correctly done. The email is mark as read but not available in Freescout.

• Setting unread an email
• Visiting the URL https://example.com/system/cron/04c3f0b4a3771c3d76a2fac9a70b71a7 is fetching the unread emails.

and the email is in Freescout but as per Freescout

Cron Commands

Make sure that you have the following line in your crontab:
* * * * * php /app/code/artisan schedule:run >> /dev/null 2>&1
Alternatively cron job can be executed by requesting the following URL every minute (this method is not recommended as some features may not work as expected, use it at your own risk):
https://example.com/system/cron/04c3f0b4a3771c3d76a2fac9a70b71a7 

So I really do not know what I have to do

[nebulon]

Though this is exactly what the cronjob from the package already does. Cloudron runs that every minute. So at max it should take 1 minute for freescout to catch up on the emails.

You can also trigger the cloudron's cron job in the top right menu, if you open a webterminal into the app. Just to see if this fetches the mails correctly.

[sebastienserre]

yes but without the external cron no emails are fetch.

[nebulon]

I feel there is something else happening here, since both are running the same command. Can you run the cron shipped via the package (via the webterminal) and see if it shows any errors? We use freescout for the Cloudron support ticket and no further cron schedule should be required. Do you see any errors at all (besides the permissions issues, which are to be expected if you run some parts as root and they update cache files, which is wrong in the first place)