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. Not Receiving Tickets in FreeScout Helpdesk (Cloudron) – 419 Errors on /polycast/receive

Not Receiving Tickets in FreeScout Helpdesk (Cloudron) – 419 Errors on /polycast/receive

Scheduled Pinned Locked Moved FreeScout
4 Posts 2 Posters 38 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.
  • F Offline
    F Offline
    Felipe.rubilar
    wrote last edited by
    #1

    Hello everyone,

    We are running FreeScout on Cloudron, and for about the last 2 hours, our organization has not been receiving any new tickets in our FreeScout helpdesk. Upon checking the system logs, I noticed repeated errors like the following:

    POST /polycast/receive HTTP/1.1" 419 21 ...
    App details:

    FreeScout version: 1.8.197
    Cloudron App ID: 99b9ef3d-b524-4349-b7ab-823205ca5f58
    Cloudron package version: net.freescout.cloudronapp@1.15.21
    Installed at: 26/08/2020
    Last updated: 11:58
    From what I understand, HTTP 419 errors in Laravel (which FreeScout is based on) are usually related to session or CSRF token issues. However, we have not made any changes to the internal app configuration or the .env file—we only manage the app through the Cloudron dashboard.

    So far, I have tried:

    Restarting the app from the Cloudron dashboard.
    Verifying the incoming mail (IMAP/POP3) configuration in FreeScout.
    Testing from different browsers and incognito mode.
    Confirming that the server time is correct.
    Despite these steps, the issue persists and no new tickets are being received by the helpdesk.

    Has anyone experienced this issue or knows how to resolve it?
    Is there any internal configuration that needs to be changed, or is this a known bug with FreeScout on Cloudron?

    Here is a relevant log snippet:

    POST /polycast/receive HTTP/1.1" 419 21 "https://mesa.solutoria.help/"
    Any help or guidance would be greatly appreciated!

    Best regards,
    Felipe Rubilar

    1 Reply Last reply
    1
    • jamesJ Offline
      jamesJ Offline
      james
      Staff
      wrote last edited by
      #2

      Hello @Felipe.rubilar
      Have you tried clearing the application cache itself?
      Open the web terminal of your freescout app and run the following command:

      sudo -E -u www-data php artisan freescout:clear-cache
      
      1 Reply Last reply
      0
      • F Offline
        F Offline
        Felipe.rubilar
        wrote last edited by Felipe.rubilar
        #3

        I’ve just cleared the cache, sent a test ticket, and the tickets started coming in again. Two of them were test tickets I sent myself and one is from operations. Thank you for your help — I hope this has resolved the issue at its root. If anything else comes up, I’ll report back in this same thread.

        Thanks.

        1 Reply Last reply
        2
        • F Offline
          F Offline
          Felipe.rubilar
          wrote last edited by
          #4

          Hi again,

          Unfortunately, our FreeScout helpdesk has stopped receiving tickets once more.

          When I first ran the cache clear command:

          sudo -E -u www-data php artisan freescout:clear-cache

          it worked correctly for about 1–2 hours — tickets started coming in again during that period. However, after that time window, new incoming tickets stopped being created again.

          To temporarily restore service, I had to restart the entire Cloudron server, and after that, tickets began arriving again. Even so, the behavior is still intermittent and not stable.

          I also noticed a Cloudron notification that might be relevant:

          Server is running out of disk space
          One or more file systems are running low on space. Please increase the disk size at the earliest.

          /dev/nvme0n1p1 (ext4) mounted at / is at 91% capacity.
          Used: 350.66GB
          Available: 37.02GB
          Size: 387.69GB

          I’m not sure if this disk space issue could be causing FreeScout to stop processing incoming emails/tickets, but I wanted to mention it in case it’s related to the 419 errors or to the mail processing queue.

          Do you think low disk space on the server could be affecting FreeScout’s ability to handle incoming mail, or is there anything else I should check (logs, queues, cron, etc.) on the Freescout/Cloudron side?

          Thanks again for your support — I’ll share any new findings here in the same thread.

          1 Reply Last reply
          1
          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