coolify
coolify copied to clipboard
[Bug]: Payload is invalid" error in Storage Management and Deployment
Error Message and Logs
Bug Report: "Payload is invalid" error in Storage Management and Deployment
Issue Description
We're experiencing a "payload is invalid" error in two places:
- During deployment of our application
- When accessing the Persistent Storage management interface in Coolify
The error appears in Coolify's storage management view (/var/www/html/resources/views/livewire/project/service/storage.blade.php), suggesting it's a Coolify-specific issue rather than an application problem.
Steps to Reproduce
- Navigate to the development environment in Coolify
- Go to Persistent Storage section
- The error occurs immediately, showing:
500 Wait, this is not cool... There has been an error with the following error message: The payload is invalid.
Environment Details
- Coolify Version: [Please add your Coolify version]
- Docker Version: [Please add your Docker version]
- OS: [Please add your OS version]
Application Configuration
Our docker-compose.yml uses the following volume mappings:
volumes:
- /data/coolify/volumes/content-development:/var/www/html/content
- /data/coolify/volumes/storage-development:/var/www/html/storage
- /data/coolify/volumes/media-development:/var/www/html/public/media
Additional Context
- The error occurs in both the storage management interface and during deployment
- The error appears to be related to how Coolify handles volume management
- The error occurs in Coolify's own interface, not in our application code
- The same error message appears in both contexts, suggesting a systemic issue
Expected Behavior
- The Persistent Storage interface should load normally
- Deployment should proceed without the "payload is invalid" error
Actual Behavior
- The Persistent Storage interface fails to load with a 500 error
- Deployment fails with the same "payload is invalid" error
Additional Information
- This issue prevents us from managing persistent storage and deploying our application
- The error appears to be related to Coolify's internal handling of volume configurations
- The error occurs in Coolify's own interface, suggesting it's not an application-specific issue
Questions
- Is this a known issue with specific Coolify versions?
- Are there any specific volume path formats that Coolify expects?
- Could this be related to permissions on the host volumes?
Steps to Reproduce
Example Repository URL
No response
Coolify Version
v4.0.0-beta.401
Are you using Coolify Cloud?
Yes (Coolify Cloud)
Operating System and Version (self-hosted)
Ubuntu 24.10
Additional Information
No response