Modify

Opened 13 days ago

Last modified 7 days ago

#23793 needinfo defect

I CANNOT UPLOAD

Reported by: tmaqelepo@… Owned by: tmaqelepo@…
Priority: normal Milestone:
Component: Core Version:
Keywords: Cc:

Description

its been about two weeks now and I cannot upload my work and I get a wiki server error 403 message. at first I thought it had to do with the JOSM old version I am using on a Windows 7 x86 Desktop but I also get the same problem on windows 10 x64 with a recent version of JOSM. This is massively frustrating as I am validating, adding and correcting a whole lot of data in Lesotho using the official (but offline) maps. which includes villages, rivers, mountain peaks, road names, survey marks and institutions amongst others "the whole works". so this server error turned to be a show stopper, so guys please help us out.

boocha34

Attachments (1)

Capture_OSM 29062024_2053.jpeg (3.1 MB ) - added by tmaqelepo@… 13 days ago.
My current OSM project for LESOTHO

Change History (4)

by tmaqelepo@…, 13 days ago

My current OSM project for LESOTHO

comment:1 by GerdP, 12 days ago

If you are able to upload small changes (in a small bbox) you probably hit a new server limit which was introduced to reduce the ongoing vandalism. In that case you can try to contact the DWG to be whitelisted.

comment:2 by taylor.smock, 12 days ago

Owner: changed from team to tmaqelepo@…
Priority: criticalnormal
Status: newneedinfo

As @GerdP said, you may be running into a new server limit.

I have no clue what you are trying to get across with the screenshot for Lesotho. Is pink the working area? How many objects are modified? When you go to upload, how many new/modified/deleted objects are you uploading? How big is the bbox that you are trying to upload (just give us an approximation)?

Also, "old" and "recent" versions of JOSM may be relative. It would help to know the actual version numbers.


Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.

Please add all needed information according to this list:

  • The required parts of the Status Report from your JOSM.
  • Describe what behaviour you expected.
  • Describe what did happen instead.
  • Describe if and how the issue is reproducible.
  • Add any relevant information like error messages or screenshots.

To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Helpsource:trunk/resources/images/bug.svg Report Bug.


comment:3 by Hufkratzer, 7 days ago

I also had some problems uploading small changesets yesterday (JOSM version 19067 tested, Win 10), but as far as I remember it always worked on the third attempt. I have not investigated this further and don't remember the exact error message.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as needinfo The owner will remain tmaqelepo@….
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from tmaqelepo@… to the specified user. Next status will be 'new'.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from tmaqelepo@… to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.