Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. FreeScout
  3. Failed to open stream: Permission denied

Failed to open stream: Permission denied

Scheduled Pinned Locked Moved FreeScout
17 Posts 2 Posters 99 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • sebastienserreS Offline
    sebastienserreS Offline
    sebastienserre
    wrote last edited by
    #2

    https://forum.cloudron.io/topic/14610/not-receiving-tickets-in-freescout-helpdesk-cloudron-419-errors-on-polycast-receive/5?_=1768070658349

    Rebooting mail service and then Freescout app is solving the issue.
    I will monitor to see if it's definitively fixed.

    He/Him - Native language: French

    1 Reply Last reply
    2
    • sebastienserreS Offline
      sebastienserreS Offline
      sebastienserre
      wrote last edited by
      #3

      The error just came back....

      He/Him - Native language: French

      1 Reply Last reply
      1
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote last edited by
        #4

        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?

        1 Reply Last reply
        1
        • sebastienserreS Offline
          sebastienserreS Offline
          sebastienserre
          wrote last edited by
          #5

          Hello @nebulon
          I've a cron here:
          cloudron app cron

          Here the list of Freescout module:
          freescout module list

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

          He/Him - Native language: French

          1 Reply Last reply
          1
          • nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote last edited by
            #6

            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.

            1 Reply Last reply
            0
            • sebastienserreS Offline
              sebastienserreS Offline
              sebastienserre
              wrote last edited by
              #7

              I've removed and will monitor few days .
              Thanks

              He/Him - Native language: French

              1 Reply Last reply
              1
              • sebastienserreS Offline
                sebastienserreS Offline
                sebastienserre
                wrote last edited by
                #8

                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

                He/Him - Native language: French

                1 Reply Last reply
                0
                • nebulonN Offline
                  nebulonN Offline
                  nebulon
                  Staff
                  wrote last edited by
                  #9

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

                  1 Reply Last reply
                  0
                  • sebastienserreS Offline
                    sebastienserreS Offline
                    sebastienserre
                    wrote last edited by
                    #10

                    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 😞

                    He/Him - Native language: French

                    1 Reply Last reply
                    0
                    • nebulonN Offline
                      nebulonN Offline
                      nebulon
                      Staff
                      wrote last edited by
                      #11

                      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.

                      1 Reply Last reply
                      0
                      • sebastienserreS Offline
                        sebastienserreS Offline
                        sebastienserre
                        wrote last edited by
                        #12

                        yes but without the external cron no emails are fetch.

                        He/Him - Native language: French

                        1 Reply Last reply
                        0
                        • nebulonN Offline
                          nebulonN Offline
                          nebulon
                          Staff
                          wrote last edited by
                          #13

                          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)

                          1 Reply Last reply
                          1
                          • sebastienserreS Offline
                            sebastienserreS Offline
                            sebastienserre
                            wrote last edited by sebastienserre
                            #14

                            I think the CRON are OK.
                            I do not understand why, but it seems that emails on this mailboxe are marked as read. I can't find how because I've checked the settings and there are no rules to mark a mail as read.
                            I've stopped SOGo and installed Roundcube, the same
                            The address is not setup in Thunderbird but I've tried by closing it, and the email is also marked as read...
                            is there logs I can check to know who and when a mail is marked as read ?

                            This is how if 1 cron task (marking as read) works but then an error arises.
                            here's an alert received by Freescout:

                            [2026-01-13 07:52:06] Erreur lors de la récupération de l'e-mail {"error":"Error: connection failed - stream_socket_client(): Unable to connect to ssl:\/\/mail.txxx.com:993 (Connection refused); File: \/app\/code\/overrides\/webklex\/php-imap\/src\/Connection\/Protocols\/ImapProtocol.php (95)","mailbox":"Support Thxxxo"}
                            ``

                            He/Him - Native language: French

                            1 Reply Last reply
                            0
                            • nebulonN Offline
                              nebulonN Offline
                              nebulon
                              Staff
                              wrote last edited by
                              #15

                              Ok so the cron from the package, fetching new mails works and no more permissions errors? Just to have that out of the way.

                              Is ther maybe some sieve script for that mailbox which could interact with mail like marking them as read?

                              1 Reply Last reply
                              0
                              • sebastienserreS Offline
                                sebastienserreS Offline
                                sebastienserre
                                wrote last edited by
                                #16

                                Yes the original permissions error is gone.
                                I really do not remember to have added any script but my brain is going these days....
                                where should these scripts could be readable?
                                I will check if something is wrong there.

                                He/Him - Native language: French

                                1 Reply Last reply
                                0
                                • nebulonN Offline
                                  nebulonN Offline
                                  nebulon
                                  Staff
                                  wrote last edited by
                                  #17

                                  So you can find the sieve scripts for each mailbox at /home/yellowtent/boxdata/mail/<mailbox>/sieve via SSH. Maybe check if you have any for that mailbox, just so we can rule that out.

                                  1 Reply Last reply
                                  0
                                  Reply
                                  • Reply as topic
                                  Log in to reply
                                  • Oldest to Newest
                                  • Newest to Oldest
                                  • Most Votes


                                  • Login

                                  • Don't have an account? Register

                                  • Login or register to search.
                                  • First post
                                    Last post
                                  0
                                  • Categories
                                  • Recent
                                  • Tags
                                  • Popular
                                  • Bookmarks
                                  • Search