mirror of
https://github.com/koel/koel.git
synced 2026-04-25 00:36:03 +03:00
[GH-ISSUE #1262] i can't login #722
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#722
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kroyoo on GitHub (Nov 24, 2020).
Original GitHub issue: https://github.com/koel/koel/issues/1262
hyzual/koel
I use the Docker version.Yesterday I was able to log in normally. Today, after I restart the server, there will be a logon problem.At first I thought it was a password error, then I looked at the console and found 'https://***/ API /data 500 '.
This is my
nginx log cat **. Log | grep/API /dataAs you can see from the above log, when I hit login like crazy, I finally log in successfully.I don't know what the problem is.
This is my Nginx proxy configuration:
Thank you
@BrookeDot commented on GitHub (Dec 30, 2020):
What version or Koel, what platform, and what commands did you run? Can you follow the issue template?
https://github.com/koel/koel/blob/master/.github/ISSUE_TEMPLATE/--bug-report.md
@phanan commented on GitHub (Dec 30, 2020):
nginx log isn't super useful, as the error appears to have happened from upstream (Apache?). You can also try checking the application log under
storage/logs/laravel.logto see what the problem was.That said, I'm closing this because you didn't follow the issue template.