8000 Experiencing 504 timeout with no way to access to freescout · Issue #174 · tiredofit/docker-freescout · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Experiencing 504 timeout with no way to access to freescout #174

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

Open
altdsoy opened this issue Apr 27, 2024 · 2 comments
Open

Experiencing 504 timeout with no way to access to freescout #174

altdsoy opened this issue Apr 27, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@altdsoy
Copy link
altdsoy commented Apr 27, 2024

Summary

We have a docker instance of Freescout that was running just fine and now all of a sudden we are getting 504 Timeout errors.
Restarting the docker compose stack do not solve the issue.

The logs in the container side does not show anything useful:

Container log:
2024-04-26.20:06:22 [NOTICE] ** [container-init] Detected Container that has been restarted - Cleaning '/tmp/.container' files
2024-04-26.20:06:23 [NOTICE] ** [monitoring] Container configured for monitoring with 'zabbix modern'
2024-04-26.20:06:23 [NOTICE] ** [scheduling] Container configured for scheduled tasks with 'cron'
2024-04-26.20:06:23 [NOTICE] ** [messaging] Container configured to route mail via SMTP to 'postfix-relay'
2024-04-26.20:06:26 [INFO] ** [freescout] Auto Configuring based on Environment Variables
2024-04-26.20:06:28 [WARN] ** [freescout] Installing Modules into container
2024-04-26.20:06:28 [WARN] ** [freescout] Running any Database Migrations
2024-04-26.20:06:30 [INFO] ** [freescout] Initialization Complete. Please visit https://my.freescout.com and login with your credentials..
2024-04-26.20:06:30 [STARTING] ** [nginx] [1] Starting nginx 1.25.4
2024-04-26.20:06:30 [STARTING] ** [php-fpm] [1] Starting php-fpm 8.2.17
2024-04-26.20:06:30 [STARTING] ** [monitoring] [1] Starting Zabbix Agent (modern) 6.4.13
2024-04-26.20:06:31 [STARTING] ** [scheduling] [1] Starting cron

And unfortunately it's the same on Freescout side. Her are the only non empty logs I have:

logs/freescout/fetch-emails.log:
[2024-04-26 20:07:02] Fetching UNREAD emails for the last 3 days.
[2024-04-26 20:07:02] Mailbox: Customer Service
[2024-04-26 20:07:02] Folder: Customer Service
[2024-04-26 20:07:02] Fetched: 0
[2024-04-26 20:07:02] Mailbox: Support
[2024-04-26 20:07:03] Folder: Support
[2024-04-26 20:07:03] Fetched: 0
[2024-04-26 20:07:03] Mailbox: Comment
[2024-04-26 20:07:03] Folder: Comment
[2024-04-26 20:07:04] Fetched: 0
[2024-04-26 20:07:04] Fetching finished
logs/php-fpm/access.log:
[26-Apr-2024 20:06:17] NOTICE: Terminating ...
[26-Apr-2024 20:06:17] NOTICE: exiting, bye-bye!
[26-Apr-2024 20:06:30] NOTICE: fpm is running, pid 1447
[26-Apr-2024 20:06:30] NOTICE: ready to handle connections
### Steps to reproduce

It happened all of a sudden.

Earlier today it was just working fine.

Environment

I have the server behind Traefik.

And tried restarting Traefik as well.

No errors in Traefik.

  • Image version / tag: Latest (at the time of running on April 4th - not sure of the actual version as it's not running)
  • Host OS: Debian
Here is my entire `docker-compose.yml`:
version: '2'

services:
  freescout-app:
    image: tiredofit/freescout
    container_name: freescout-app
    links:
    - freescout-db
    volumes:
    ### If you want to perform customizations to the source and have access to it, then uncomment this line - This includes modules
    # - ./data:/www/html
    ### Or, if you just want to use Stock Freescout and hold onto persistent files like cache and session use this, one or the other.
    - /root/freescout/data:/data
    ### If you want to just keep the original source and add additional modules uncomment this line
    # - /root/freescout/modules:/www/html/Modules
    - /root/freescout/logs/:/www/logs
    environment:
    - CONTAINER_NAME=freescout-app
    - DB_HOST=freescout-db
    - DB_NAME=freescout
    - DB_USER=freescout
    - DB_PASS=abc
    - SITE_URL=https://my.freescout.com
    - ADMIN_EMAIL=admin@my.freescout.com
    - ADMIN_PASS=xyz
    - ENABLE_SSL_PROXY=FALSE
    - DISPLAY_ERRORS=FALSE
    - TIMEZONE=America/Los_Angeles
    restart: always
    networks:
      - freescout
      - traefik
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.freescout.rule=Host(`my.freescout.com`)"
      - "traefik.http.routers.freescout.entrypoints=https"
      - "traefik.http.routers.freescout.tls=true"
      - "traefik.http.routers.freescout.tls.certresolver=traefik_resolver"

  freescout-db:
    image: tiredofit/mariadb
    container_name: freescout-db
    volumes:
      - /root/freescout/db:/var/lib/mysql
    environment:
      - ROOT_PASS=jkl
      - DB_NAME=freescout
      - DB_USER=freescout
      - DB_PASS=abc
      - CONTAINER_NAME=freescout-db
    restart: always
    networks:
      - freescout

  freescout-db-backup:
    container_name: freescout-db-backup
    image: tiredofit/db-backup
    links:
     - freescout-db
    volumes:
      - /root/freescout/dbbackup:/backup
    environment:
      - CONTAINER_NAME=freescout-db-backup
      - DB_HOST=freescout-db
      - DB_TYPE=mariadb
      - DB_NAME=freescout
      - DB_USER=freescout
      - DB_PASS=abc
      - DB01_BACKUP_INTERVAL=1440
      - DB01_BACKUP_BEGIN=0000
      - DB_CLEANUP_TIME=8640
      - COMPRESSION=BZ
      - MD5=TRUE
    restart: always
    networks:
      - freescout

networks:
  freescout:
  traefik:
    external: true

Possible fixes

I have no clue.

What can I look inside the container besides the log files that's also mostly empty?

I remember having something equivalent a few weeks back but it was an issue on my docker compose configuration as I did somehow enabled all of the volumes. Now I only have 2.

It's really annoying to not have any clue about what's going on.
Any help is much appreciated as I'm getting tired of IT as well :)

@altdsoy altdsoy added the bug Something isn't working label Apr 27, 2024
@WesternSmokehousePartners

Have you tried changing version:latest to the previous version to see if an update may have caused the issue? We had a problem with the latest version and had to roll back. We changed our image to tiredofit/freescout:php8.1-1.17.68 to fix the issue.

@jhgeluk
Copy link
jhgeluk commented Mar 7, 2025

Also experiencing this issue..

Nothing in the nginx, laravel and mail logs. Also nothing in my traefik logs.

Do you remember what the issue was @altdsoy ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants
0