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

login issue #8420

Open
chandtech89 opened this issue Sep 9, 2020 · 2 comments
Open

login issue #8420

chandtech89 opened this issue Sep 9, 2020 · 2 comments
Labels

Comments

@chandtech89
Copy link

I was trying to login into snipe IT but unable to login. It doesn't throw any error, only page get refreshed.
Initially it is working fine.

I have enabled debug mode

Log:
production.ERROR: Failed to authenticate on SMTP server with username "YOURUSERNAME" using 2 possible authenticators. Authenticator LOGIN returned Expected response code 334 but got code "530", with message "530 Must issue a STARTTLS command first
#89 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Session/Middleware/StartSession.php(63): Illuminate\Routing\Pipeline->Illuminate\Routing{closure}()
#90 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(149): Illuminate\Session\Middleware\StartSession->handle()
#91 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
#92 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(46): Illuminate\Routing\Pipeline->Illuminate\Routing{closure}()
#93 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(149): Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode->handle()
#94 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
#95 /var/www/html/snipe/vendor/barryvdh/laravel-cors/src/HandlePreflight.php(29): Illuminate\Routing\Pipeline->Illuminate\Routing{closure}()
#96 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(149): Barryvdh\Cors\HandlePreflight->handle()
#97 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\Pipeline\Pipeline->Illuminate\Pipeline{closure}()
#98 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(102): Illuminate\Routing\Pipeline->Illuminate\Routing{closure}()
#99 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(151): Illuminate\Pipeline\Pipeline->then()
#100 /var/www/html/snipe/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\Foundation\Http\Kernel->sendRequestThroughRouter()
#101 /var/www/html/snipe/public/index.php(58): Illuminate\Foundation\Http\Kernel->handle()
#102 {main}

no, I am facing this suddenly - Is this a fresh install or an upgrade?
PHP 7.4.3 - Version of PHP you're running
mariadb 10.4 - Version of MySQL/MariaDB you're running
centos 8 - What OS and web server you're running Snipe-IT on
manual installation - What method you used to install Snipe-IT (install.sh, manual installation, docker, etc)
yes - WITH DEBUG TURNED ON, if you're getting an error in your browser,
login page - What specific Snipe-IT page you're on, and what specific element you're interacting with to trigger the error
No- Any errors that appear in your browser's error console.

https://snipe-it.readme.io/docs/getting-help

@snipe
Copy link
Owner

snipe commented Sep 9, 2020

Check your .env and make sure your cookie session values make sense for your setup. The COOKIE_DOMAIN should be set to the domain name you're hosting it on, and SECURE_COOKIES should only be set to true if you're running over https.

@stale
Copy link

stale bot commented Dec 25, 2020

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

@stale stale bot added the stale label Dec 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants