Replies: 2 comments 2 replies
-
You should not be editing (via composer update) the composer.lock. When you do so, we have no way of knowing what changed within the package, and unexpected errors occur. What's your APP_URL? |
Beta Was this translation helpful? Give feedback.
-
I have restored the vm snapshot to version 6.10, runnning with http. upgraded again to 6.12 with chown user and chmod 775. Then switched to user and upgraded with php upgrade.php. Laravel.log shows again the socialite Errormessage: |
Beta Was this translation helpful? Give feedback.
-
Hi,
i've got a running local installation of snipe-it, version 6.12, using http. PHP=7.4.33, Laravel=8.83.22, Debian11.
i tried to put a reverse proxy in front of the installation (a separate utm-firewall), which i've done succesfully with any other of our local server applications. My first GET-request is translated to https, but following request still used http. After a little try'n'error i come across the setting APP_FORCE_TLS which i set to true, then issuing php artisan config:clear. It works instantly. Yes!!
But during fixing my other issue with laravel not logging anything in /storage/logs/laravel.log i tried to fix a problem with SocialiteServiceProvider which could not be found, which i reinstalled with composer require laravel/socialite and php artisan config:cache.
After this change only the first request again is https, any following are http. It works again when issuing php artisan config:clear.
So in short: when i use php artisan config:clear everything seems to be ok. when i use php artisan config:cache only the first request is https. Then i cannot login because of browser security i think.
Anyone can help me with this?
Beta Was this translation helpful? Give feedback.
All reactions