-
Notifications
You must be signed in to change notification settings - Fork 30
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
500 Error on /api/input #32
Comments
Can you get more info on what the server says the 500 error is? Something from the MAMP logs. |
Thanks for the quick response - I don't get any errors logged from MAMP nor from the Console in Postman. All I get back is the 500 response and the "Whoops, looks like something went wrong." error page. I'm not sure if it's relevant but I get the same result whether or not artisan's queue listener is running. Do you have any tips as to where I to continue debugging here? |
check the log for the app, should be in It sounds like maybe the app isn't finished getting set up? You need a database and optionally Redis. I'm betting that log will tell you more. |
Does Compass not use mysql by default for the job queue? I have mysql up and running correctly I believe as far as storage is concerned. Are there any red flags we should be looking for - here are the tail'd logs for the 500 error from lumen.log:
|
Thanks, I need to see the top of that stack for it to be useful. Scroll up to where it says |
Looks like the default config file has |
I'm trying to use Compass + Overland and am encountering 500 Internal Service Error's when attempting to POST to
/api/input
while running in MAMP. I see this same issue when I test locally with Postman. It seems the server is rejecting the request due to invalid content types -"Request failed: unacceptable content-type: text/html"
.Is there a way to set acceptable content types for the server or is there something else causing this issue?
When testing with Postman, if I send the body GeoJSON data as text/html the server returns a 200 but just can't parse it, if I send as application/json it fails with a 500 even though it's seemingly correctly-formed.
Here's the full printed error Overland's side:
The text was updated successfully, but these errors were encountered: