mirror of
https://github.com/koel/koel.git
synced 2026-04-25 08:46:00 +03:00
[GH-ISSUE #20] Error 422 Unprocessable Entity #14
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#14
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 @bhulsman on GitHub (Dec 14, 2015).
Original GitHub issue: https://github.com/koel/koel/issues/20
I just installed Koel on Laravel's Homestead and tried adding a directory containing some music. When clicking scan I get the error '422 Unprocessable Entity' (POST http://koel.local/api/settings 422 (Unprocessable Entity)).
Request payload:
Response
@phanan commented on GitHub (Dec 14, 2015):
Can you try
E:\\koel_demo\music?@bhulsman commented on GitHub (Dec 14, 2015):
Still getting the same error, no difference.
@phanan commented on GitHub (Dec 14, 2015):
Sorry, but I've not tested Koel on Windows yet – other users don't seem to have this problem though. From how it looks, the error comes from here.
@bhulsman commented on GitHub (Dec 14, 2015):
My mistake! The 'homestead vagrant box' cannot reach directories that aren't shared, in this case, a local directory on my Windows PC.
Not very handy that no error was provided, so that's the real issue here.
@phanan commented on GitHub (Dec 14, 2015):
You're right. I'll be adding better error handlers. Glad you sorted it out!
@bhulsman commented on GitHub (Dec 14, 2015):
Great! Hopefully I can contribute something to this project, I really like it 👍