I’ve attempted to upload maps using both the Forge Asset Library from within the World itself.
I get an unknown Error 0 message in the asset library.
I get these errors.
A similar problem occurred months ago but was resolved. The file I’m attempting to upload is a mere 2,850KB. I’m disinclined to continually have problems uploading maps for my games if this is going to be a reoccurring
This is the errors when I try to upload in world.
issue.
Before anyone suggests it’s an issue with my internet upload or download. I ran a speedtest these were the results
The previous case (Can't Import Maps) had since been resolved as mentioned here.
I don’t think what is currently occurring is the same issue, the image there shows a 408 Request Timeout - HTTP | MDN which usually means that there is a timeout waiting to receive data from the browser.
We’ve run into this issue a couple of times in specific regions when there’s some form of issue with routing. It’s generally not an issue that would show as poor upload or download speeds, because the issue is somewhere in the route between the user and the assets server rather than between the user and the speedtest server.
One important thing to test is to try the upload with a different connection (such as mobile tethering), or with a VPN or VPN-like service such as Cloudflare WARP which would use different routes.
If a different connection resolves it, then it’s likely a routing issue. If it doesn’t, then there may be something else at play.
The issue is my computer is wired directly to my router. I don’t have it set up for a wireless connection, and frankly don’t have much desire to do so.
Every other upload or download application I attempt seems to have no issue except for this one, with this service.
It’s possible to USB tether a mobile phone to use its connection if setting up a mobile hotspot is not an option. A VPN-like service like Cloudflare WARP is also free to use, but I can understand that it is a frustrating thing to be asked to test with.
The trouble is that if the issue occurs in a route it can be tricky to troubleshoot or confirm without testing the action using a different connection with different routes.
Some users did report that clearing the DNS cache on their local machine resolves the issue if it surfaces. I’ll link an article on DNS cache & clearing which may help. Since it’s something that appears sporadically, I’m inclined to think that some kind of routing or DNS issue is at play.
