Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

0% Progress uploading map

Hey all! I'm using Chrome, no extensions running, cleared cache. Tried to upload a map (just under 4mb so not too big). Getting no progress whatsoever. Any ideas what to try?
Do you have enough free space? Go to your Account Settings and check your quota. If you are near your limit, try deleting older files you no longer need... What format has your map (PNG / JPEG / JPG / ...)?
1703256632
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
You could also try again. Roll20 has been undergoing a DDOS attack for the last day or so. You may have lost connection mid-upload. It might also be a good idea to check your Art Library and delete any partial uploads.
This happens regularly with me as well, and it's not a storage issue. After about five or ten minutes of launching my game it stops letting me upload maps as well as tokens. My players are also having trouble with the charactermancer getting stuck after they finish making their sheets, it just doesn't finish and they can't access their sheets normally.
Though I should clarify this didn't start happening until the DDos attack
Hi all, Thanks for getting back. @TheMarkus1204 - its not storage I've plenty at present. I suspect it is the DDOS. @keithcurtis re checking the art library/deleting partial uploads is this just done in game? Not sure where to look.
1703348430
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
In-game would probably be best. They would exist at the top of the Recent Uploads list. But it doesn't always happen on a failed upload; it's just something to check. Deleting cache and cookies then reloading the site can also help.
Thanks again Keith.  FYI the workaround for this turned out to be using Firefox instead of Chrome.