Open LoggaRythmus opened 10 months ago
Looks like you are exporting too many volumes. Try exporting only /data and /www/logs..
The error in the first log disappeared but i still cant access the site
`[2023-12-19 11:18:44] production.ERROR: Class "Modules\Checklists\Providers\ChecklistsServiceProvider" not found {"exception":"[object] (Symfony\Component\Debug\Exception\FatalThrowableError(code: 0): Class \"Modules\Checklists\Providers\ChecklistsServiceProvider\" not found at /www/html/overrides/laravel/framework/src/Illuminate/Founda>[stacktrace]
"}`
After Clearing the Cache i had an error:
In ProviderRepository.php line 279:
Class "Modules\Checklists\Providers\ChecklistsServiceProvider" not found
@LoggaRythmus I have the same issue, have you found a solution ?
Hi there.. I just faced the same issue after I tried to update the docker compose stack ( running docker compose pull and then up).. Yet the previous version was 2 weeks old, so I don't think too much change occurred causing incompatibility. Until now I was running using the following volumes:
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
Everything was working fine even between updates (just made a couple). But today I was getting 504 and freescout is not even starting. When looking at the logs it's about missing a module.
If I remove the volumes and only keeps the logs, I'm able to boot freescout again but I lost all my settings.
I still have my data around on the host, how can I fix it?
Update: Somehow the above was working but since I read the problem might be because of having too many volumes, I just commented the modules and just kept the following:
volumes:
- /root/freescout/data:/data
- /root/freescout/logs/:/www/logs
Now I don't see the error message anymore.. But I'm still getting 504 error and I have no logs at all.. Don't know where to look..
Edit: After stopping/recreating the stack a bunch of times, it worked.. Really I don't know what I messed up but finally I was able to recover the state of my app. My current config is the one above (with only 2 volumes)
Summary
I am using Freescout for a week now and i had to update my environment for an update of a module, it needed the latest freescout version so i updated the docker image to the latest. After that the Website was accessible but not working correctly.
Steps to reproduce
I updated my docker image from 1.17.44 to 1.17.48 after that the website is not accessible "Whoops, looks like something went wrong — check logs in /storage/logs"
What is the expected correct behavior?
Website accessible and working environment.
Relevant logs and/or screenshots
Environment
version: '2' services: freescout-app: image: tiredofit/freescout container_name: freescout-app ports: - 8282:80 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. - ./data:/data ### If you want to just keep the original source and add additional modules uncomment this line - ./modules:/www/html/Modules - ./logs/:/www/logs environment: - CONTAINER_NAME=freescout-app - DB_HOST=freescout-db - DB_NAME= - DB_USER= - DB_PASS= - APP_NEW_FETCHING_LIBRARY=true - SITE_URL= - ADMIN_EMAIL= - ADMIN_PASS= - ENABLE_SSL_PROXY=FALSE - DISPLAY_ERRORS=FALSE - TIMEZONE=Europe/Berlin restart: always freescout-db: image: tiredofit/mariadb container_name: freescout-db volumes: - ./db:/var/lib/mysql environment: - ROOT_PASS= - DB_NAME= - DB_USER= - DB_PASS= - CONTAINER_NAME=freescout-db restart: always freescout-db-backup: container_name: freescout-db-backup image: tiredofit/db-backup links: - freescout-db volumes: - ./dbbackup:/backup environment: - CONTAINER_NAME=freescout-db-backup - DB_HOST=freescout-db - DB_TYPE=mariadb - DB_NAME= - DB_USER= - DB_PASS= - DB01_BACKUP_INTERVAL=1440 - DB01_BACKUP_BEGIN=0000 - DB_CLEANUP_TIME=8640 - COMPRESSION=BZ - MD5=TRUE restart: always
Possible fixes