-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
500 server error, versions after v0.11.17 dont work #895
Comments
Confirmed - I see the same behavior, I posted in #893 |
Since you're specifying your environment variables in your I also don't see an |
I have the same issue
Logs: [2023-11-12 20:55:48] production.ERROR: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'speedtest_tracker.cache' doesn't exist (Connection: mysql, SQL: delete from ������� prog: fatal: stopping the container. |
Had the same error (using the docker compose), I set the APP_KEY using |
Thank you, i done it. With Version v0.11.17, no issues. With he latest Version its not working. 🔒 SSL_MODE has been set to MIXED, setting the web server to work in HTTP + HTTPS... 🐇 Configuring Speedtest Tracker... 🔒 Fixing app path file permissions... ✅ Permissions fixed. 🧹 Clearing any previous caches... ✅ Cache cleared. ✅ Environment file exists. 🔗 Creating symlinks for config and log files... ✅ Symlinks created. ✅ An application key exists. 💰 Building the cache... ✅ Cache set. 🚛 Migrating the database... ✅ Database migrated. ✅ All set, Speedtest Tracker started. [12-Nov-2023 21:20:24] NOTICE: fpm is running, pid 123 [12-Nov-2023 21:20:24] NOTICE: ready to handle connections [12-Nov-2023 21:20:24] NOTICE: systemd monitor interval set to 10000ms [2023-11-12 21:20:31] production.ERROR: No application encryption key has been specified. {"exception":"[object] (Illuminate\Encryption\MissingAppKeyException(code: 0): No application encryption key has been specified. at /var/www/html/vendor/laravel/framework/src/Illuminate/Encryption/EncryptionServiceProvider.php:79) ������� |
the |
The *.env file is deleted already. API_KEY was generated by version: '3.3' |
yeah broken for me too using it via docker on a unraid server. 500 server error |
You have API_KEY not APP_KEY |
☝️ this, going to close this issue. If the |
Hi folks, I'm wresting with a similar issue. I'm not clear on what the fix is based on the above comments. Is there official documentation on this? My container was working then suddenly started erroring out with this encryption key error out of nowhere. The default docker compose yml reference file in this repo doesn't mention this. If there was a breaking change, it needs to be more up front for folks who have run this container for a long time. |
Yeah, it's stated that the API key format is the root of these problems, but I had all that correct and it didn't help. The only way I could make the container work was a total redo with all config and database cleared out and a fresh install. I saved all my old data with the hope to import my history back in but it's becoming less likely the more I look at it. |
Again, APP_KEY, NOT API |
run this command and get the APP_KEY: I use docker compose (stacks via portainer), so it is as easy as adding the APP_KEY to the environment variables. Here's my entire docker compose: (Key Redacted)
I hope this helps. |
Describe the bug
Nothing much to say, v0.11.17 is the latest version that works, latest (v0.13.1) and versions prior to that just refuse to work properly and throw empty error logs, then freeze and give a 500 error on the UI.
Error log:
docker-compose.yml
:The text was updated successfully, but these errors were encountered: