Error 500 when trying to upload a world

Got the same problem with my 1.13.2 world now 1.14 has come.
With the full version of the map and an older backup I get the (-1) error.
With a version where I deleted all far away region files to find new villages/biomechanges, I get the (500) error.

My world uses multiple datapacks/commandblocks/gamerule changes.
Tried the optimize for 1.14 function, with and without deleting cashed data. But nothing changed.
I can open the world in singleplayer 1.14 but the world loads extremely slow.
I can send the world if needed.

I'm getting the same error.  I downloaded a 1.14 realm to prune the regions and was unable to reload.

Datapacks are the problem. Doesnt matter which datapack I have, the datapacks are the reason for the failure. Removing all of them fixes this problem.
My server uses datapacks a lot for quality of life and extras to make my server unique and fun. It's a huge blow to my server now that I can't use any of them. But at least I can play again.

Duplicate MC-149127 also talks about datapacks.

I had the same problem. Check the datapacks folder and make sure the packs are still in proper zip format and no extra layers of folders. A folder with a .zip extension does not make it a .zip

Thanks Jakob!
I see whats going on now.
When you download a world from your Realms backups it changes the datapacks from zips to folders. So we uploaded usable datapack zips, but when we download the worlds we get datapack folders instead.

So this bug consists of 2 things.
-A totally non-descriptive (500) error message. It should have said something about unrecognizable datapacks.
-A bug in downloading backup worlds. When we download backups from Realms it makes our datapacks unusable for re-upload to Realms.

Thanks for diagnosing this error. We'll take a look at this. BTW, does the log contain more info than the 500 screen?

Don't think the client logs tell anything about this. In this log I did this:

1. Started 1.14

2. Went into Realms world 2

3. Downloaded my working map with datapacks from the Realms backups

4. Switched to world 3

5. Uploaded the map I just downloaded

6. Got the (500) error message

7. Closed the game

[12:09:26] [Client thread/INFO]: Setting user: MuMe
[12:09:29] [Client thread/WARN]: Skipping bad option: lastServer:
[12:09:29] [Client thread/INFO]: LWJGL Version: 3.2.1 build 12
[12:09:33] [Client thread/INFO]: Narrator library for x64 successfully loaded
[12:09:33] [Client thread/INFO]: Built for minecraft version 1.14
[12:09:53] [Client thread/INFO]: OpenAL initialized.
[12:09:53] [Client thread/INFO]: Sound engine started
[12:09:53] [Client thread/INFO]: Created: 1024x512 textures-atlas
[12:09:53] [Client thread/INFO]: Created: 256x256 textures/particle-atlas
[12:09:53] [Client thread/INFO]: Created: 256x256 textures/painting-atlas
[12:09:53] [Client thread/INFO]: Created: 256x128 textures/mob_effect-atlas
[12:09:58] [Client thread/INFO]: Built for minecraft version 1.14
[12:09:58] [Client thread/INFO]: Realms library version == 1.14.13
[12:09:58] MCO Compatability Checker #1/INFO: Realms is available for this user
[12:16:42] [Client thread/INFO]: Stopping!

And checked the downloaded world. The datapacks zips became folders again.

So I found a solution, but its a dang crappy one.

The problem for me were, that I were using Datapacks, after I removed those, it worked just fine, no problem uploading anymore, but I hope Mojang still will try to fix it, and let me/us use datapacks again,

P.S remember to copy ur saved map before removing ur datapacks just in case 🙂 

A fix is on the way. Another temporary workaround is to modify the world zip by re-zipping any datapack zips inside it which have become folders.

Serverside fix, live as of now

I am still having this issue as of 5/3/2020

Still happens – REALMS-2146

Having the same issue.