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.

Sign up for GitHub

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

Jump to bottom

Cant log in after upgrade to 5.1 #9951

Closed
SnipeJuan opened this issue Aug 18, 2021 · 10 comments
Closed

Cant log in after upgrade to 5.1 #9951

SnipeJuan opened this issue Aug 18, 2021 · 10 comments

Comments

@SnipeJuan
Copy link

Expected Behavior (or desired behavior if a feature request)

We are using LDAP to auth into snipeit. Before the upgrade there werent any issues.

Actual Behavior

When I log in, the pages refreshes back to the login screen. Cant get beyond it. I have tried creating a new admin account from the CLI and that doesnt work either. The page just goes back to the login and cant proceed.

Please confirm you have done the following before posting your bug report:

Provide answers to these questions:

  • Is this a fresh install or an upgrade?
    Upgrade
  • Version of Snipe-IT you're running
    5.1.8
  • Version of PHP you're running
    PHP 7.4.22
  • Version of MySQL/MariaDB you're running

5.5.68-MariaDB

  • What OS and web server you're running Snipe-IT on
    Operating System: CentOS Linux 7 (Core)
    CPE OS Name: cpe:/o:centos:centos:7
    Kernel: Linux 3.10.0-1160.36.2.el7.x86_64
  • What method you used to install Snipe-IT (install.sh, manual installation, docker, etc)
    upgrade.php
  • WITH DEBUG TURNED ON, if you're getting an error in your browser, include that error
    not getting an error. its just refreshing
  • What specific Snipe-IT page you're on, and what specific element you're interacting with to trigger the error
    /login
  • If a stacktrace is provided in the error, include that too.
  • Any errors that appear in your browser's error console.
    No
  • Confirm whether the error is reproducible on the demo: https://snipeitapp.com/demo.
  • Include any additional information you can find in storage/logs and your webserver's logs.
  • Include what you've done so far in the installation, and if you got any error messages along the way.
  • Indicate whether or not you've manually edited any data directly in the database
    No

Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.

https://snipe-it.readme.io/docs/getting-help
@welcome
Copy link

welcome bot commented Aug 18, 2021

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@snipe
Copy link
Owner

snipe commented Aug 18, 2021

Include any additional information you can find in storage/logs and your webserver's logs.
Include what you've done so far in the installation, and if you got any error messages along the way.

@snipe
Copy link
Owner

snipe commented Aug 18, 2021

(Also did you clear browser cookies, etc etc)

@SnipeJuan
Copy link
Author

SnipeJuan commented Aug 18, 2021 via email

@snipe
Copy link
Owner

snipe commented Aug 18, 2021 •
edited by unfurl-links bot

Did you try running the commands mentioned here?
https://snipe-it.readme.io/docs/common-issues#quick-tip-handy-commands

I'd also maybe try deleting the vendor directory and re-running composer install --no-dev

Snipe-IT Documentation
These commands should be run from your Snipe-IT project root, just like every other cli command we mention. They should not need to be run as root/sudo/admin.Or to run them as a one-liner all at once:These commands clear out cached service files that help speed up modern PHP applications but can a...

@SnipeJuan
Copy link
Author

SnipeJuan commented Aug 18, 2021 via email

@snipe
Copy link
Owner

snipe commented Aug 18, 2021 •
edited

Every time you upgrade, you always have to run migrations, or at least check that upgrade.php completed migrations correctly. If you're seeing permissions issues, you should fix those as well. Everything (files and directories) in storage needs to be writable by the web server.

When I run the composer install --no-dev I get:

composer install --no-dev
Loading composer repositories with package information
Installing dependencies from lock file
Nothing to install or update

Did you remove the vendors directory first as I suggested?

@SnipeJuan
Copy link
Author

SnipeJuan commented Aug 19, 2021 via email

@snipe
Copy link
Owner

snipe commented Jun 21, 2022

Hi there - We haven't heard back in a bit, so I'm going to close this ticket for now, but will re-open it if you're still having issues.

hackerman-hacking

@snipe snipe closed this as completed Jun 21, 2022
@cartzlink
Copy link

at last I figure out what was wrong
you are viewing the page with http
change that to https and login will work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@snipe @cartzlink @SnipeJuan