Problem: Trying to add a Gmail node but adding the Google client credential fails with this error? You can't sign in to this app because it doesn't comply with Google's OAuth 2.0 policy for keeping apps secure. Error 400: invalid_request Request details:
Your apps and CI pipelines might fail with errors like: [internal] load metadata for docker.io/library/node:18 2025-Sep-24 23:25:31.336478 #3 ERROR: pulling from host registry-1.docker.io failed with status code [manifests 18]: 401 Unauthorized Don't worry, it's not you, Docker
Here is a summary of the key updates in MariaDB from versions 12.0 to 12.2 MariaDB 12.x Series Summary * Latest release: 12.2 (Preview) * 12.1 is the current rolling release candidate. * 12.0 is the first general availability (GA) version of the 12.x line. * Focus
In n8n, some workflows suddenly stopped working. ⚠️ They were still listed, but when I tried to access them — 404 Not Found. Yet, I could find them in the Postgres DB, so clearly the 404 was wrong. ⁉️ Digging Deeper 🕵️ * Only the workflows with a Gmail trigger were broken. * Tried creating a
* EDITED: 4 November 2025 - Added EX63 benchmarks I wanted to quickly compare how different Hetzner servers are doing (especially in single-threaded), for CPU-intensive tasks. I ran sysbench on four different machines: * Hetzner Cloud CPX21 (AMD EPYC Processor, 3vCPU, 4GB RAM) ~9EUR/mo * Hetzner Dedicated EX44 (i5-13500, 64GB RAM) ~40EUR/
The Postiz Coolify template doesn't seem to work by default. Use this docker-compose.yml instead: services: postiz: image: ghcr.io/gitroomhq/postiz-app:latest container_name: postiz restart: always environment: - SERVICE_FQDN_POSTIZ_5000 - MAIN_URL=${SERVICE_FQDN_POSTIZ} - FRONTEND_URL=${SERVICE_FQDN_POSTIZ} - NEXT_
Problem: I tried running ChartBrew on Coolify, but it initially didn't work, as I was getting this error: ArgError: option requires argument: -l (alias for --listen) Solution: Use this Docker Compose file and set the env variables mentioned at the end (using the Developer View in Environment Variables
Problem - Styles missing in live build npm start shows the correct styles, but on build it looks like all styles are missing. There are no JS or network errors live. Local (working): Live (not working): Solution This problem seems related to occur on the new 3.8 release, for
I always feel trapped when one of those product tours starts. They show me buttons and features before I even have any idea what the product is about. I personally prefer exploring freely. It's the same in computer games. This kind of "Press A to jump, go
Discourse does not officially provide a Docker image to run their forum software, which makes it harder to install on Coolify. ⚠️NOTE: The Bitnami Discourse Docker image might not be available anymore from October 2025: https://meta.discourse.org/t/bitnami-discourse-container-image-is-deprecated/374875 Solution: Use the Bitnami Discourse Docker Image with
⚠️After restarting my Ghost instance on Coolify v4.0.0-beta.366, my blog started showing 404 Not Found Errors. There is a bug in this Coolify version which causes this. Solution: The fix for me was to go Configuration → Edit Compose File and to add this line to my ghost
Coolify provides a way to locally set the retention for backups (how many copies to store): The problem with this is that it only applies to the local backups, stored in your Coolify instance, and not to the remote S3 backups. Without any retention policies, your S3 will retain all