You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: tom[at]compton.nu [Added to the original trac issue at 11.51am, Sunday, 3rd May 2009]
There are basically two reasons for a 500 error.
One reason is a timeout on the server, which was happening quite a bit to start with after the API 0.6 upgrade. That usually leads to an intermittent error where the same changeset will eventually upload. These errors should be largely resolved now.
The other is a coding error on the server, and it sounds more likely that this is what you were seeing here as the same changeset has failed multiple times.
The most likely cause is that the changeset is invalid but the server was failing to report this to you properly - there were a number of issues like this in the code but I believe they are all fixed now.
I'm going to assume this is fixed for now (in that the server will now correctly report what is wrong with the changeset) but please reopen the ticket if you are still having problems.
Reporter: matti[at]mversen.de
[Submitted to the original trac issue database at 4.39pm, Sunday, 26th April 2009]
I'm using josm 1553 and i get an Internal server error while uploading a set of changes.
josm reports only :
POST http://www.openstreetmap.org/api/0.6/changeset/975859/upload... Internal Se
rver Error
and gives up after 4 or 5 tries.
I uploaded the changes to an OSM file which can be found here :
http://mversen.de/temp/rel.osm
The text was updated successfully, but these errors were encountered: