Skip to content
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

[Bug]: Configuration Variables Referenced but Not Set – Unable to Resolve Warnings #4949

Closed
Shamsuddeen opened this issue Jan 24, 2025 · 1 comment

Comments

@Shamsuddeen
Copy link

Error Message and Logs

I am encountering an issue where Laravel references multiple environment variables in my application configuration, even though these variables are not explicitly defined or set in my code or .env file. Despite my efforts to add these references in my Environment Variable, the warnings persist.

The warnings appear in the logs as follows

[laravel:warn] Your app configuration references the DB_CACHE_CONNECTION environment variable, but it is not set.
[laravel:warn] Your app configuration references the DB_CACHE_LOCK_CONNECTION environment variable, but it is not set.
[laravel:warn] Your app configuration references the DB_CACHE_LOCK_TABLE environment variable, but it is not set.
[laravel:warn] Your app configuration references the MEMCACHED_PERSISTENT_ID environment variable, but it is not set.
...
[laravel:warn] Your app configuration references the SESSION_SECURE_COOKIE environment variable, but it is not set.

Steps to Reproduce

Example Repository URL

No response

Coolify Version

v4.0.0-beta.389

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

No response

@Shamsuddeen Shamsuddeen added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 24, 2025
@peaklabs-dev
Copy link
Member

peaklabs-dev commented Jan 24, 2025

This is probably a problem with your application. Please open a support thread on Discord and you will get help there, if this should be a bug inside Coolify we can reopen this. Also there is already another open issue with this exact error.

@peaklabs-dev peaklabs-dev closed this as not planned Won't fix, can't repro, duplicate, stale Jan 24, 2025
@github-actions github-actions bot removed 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants