-
Notifications
You must be signed in to change notification settings - Fork 14
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 #29
Comments
I see the error logs, and the problem is with the route you are trying to log. Are using a custom location for this route? If so make sure you have coordinates filled out in the locations tab. |
Thanks for the heads up on that... I didn't enter the "k" before the airport identifier as I should have. I'm new to the site and still learning how it accepts data. Seeing that it is open source (I'm not the best programmer out there...) perhaps someone could add a line of code to be a bit more descriptive. For example, when such an error as mine occurs, flagging the error specifically as a route entry error or perhaps even suggesting checking for a custom location or a "k" would be helpful. After the 500 error, all it said was that a system administrator was notified of the issue and that it would be resolved quickly. Had I have known it was my error, it would've been easy to correct. Thanks for the help though! |
Ok, just tried to enter the data again with the "K" and still no luck. Both airports are valid airports. I've entered KEYE a number of times already in the log, and KIND is a mere 20 or so minutes south of there (Indianapolis international airport... that's a valid major airport as well already in the database). The attempted route is KEYE KIND KEYE, a there and back cross country |
Everything was working great until about a week ago. I can not enter any new flights whatsoever. Username is flychick...
The site keeps presenting a 500 - Internal Server Error. Same result when I try from the "new entry" page or the "mass entry" page. Any help is appreciated
The text was updated successfully, but these errors were encountered: