mojira.dev
REALMS-1444

Cannot upload a world to my realm (Upload failed! (-1)

So i have been trying for 1.5 days to upload my fresh and newly started singleplayer world with a couple of datapacks to my realm. (I have also tried one without any datapacks) But everytime i try to upload any world, it gives me the: "Upload failed! (-1)" error.

I have been searching on the internet and there is nothing to be found about this error. Only people having the same error with no response.

 

Please help me in fixing this matter!

Here is the log output from the launcher:

Caught exception while uploading: org.apache.http.conn.HttpHostConnectException: Connect to 54.229.163.19:8080 /54.229.163.19 failed: Connection refused: connect at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) at com.mojang.realmsclient.client.FileUpload.requestUpload(FileUpload.java:93) at com.mojang.realmsclient.client.FileUpload.lambda$upload$0(FileUpload.java:71) at com.mojang.realmsclient.client.FileUpload$$Lambda$1060/1910233141.get(Unknown Source) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1582) at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1574) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1689) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) Caused by: java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72) at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:117) ... 18 more 10:57:07 com.mojang.realmsclient.client.FileUpload ForkJoinPool.commonPool-worker-4 error Caught exception while uploading: org.apache.http.conn.HttpHostConnectException: Connect to 54.229.163.19:8080 /54.229.163.19 failed: Connection refused: connect at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:140) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:314) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) at com.mojang.realmsclient.client.FileUpload.requestUpload(FileUpload.java:93) at com.mojang.realmsclient.client.FileUpload.lambda$upload$0(FileUpload.java:71) at com.mojang.realmsclient.client.FileUpload$$Lambda$1060/1910233141.get(Unknown Source) at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1582) at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1574) at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1689) at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) Caused by: java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:72) at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:117) ... 18 more

Comments 5

Same error here, except that the server address is 54.236.41.123:8080.

I tested the connection to that instance and port with nmap, and found the port closed.

Switching accounts, restarting realms and new worlds etc. didn't help, leading me to the same server and port.\
I'm using Java Version but I believe this should apply to any other platforms.

@Gan thanks for troubleshooting it a bit. @Anders This might happen when the server starts, but fails to accept connections. We're working on detecting this type of failure better and correcting it. Is this error reproducible for a given resource pack? It would be interesting to see if we can reproduce it and find the root cause.

On second thought, if you're not using datapacks, this should definitely not be happening. We did have issues with the uploading functionality on PC beteen december 11 and 14. Is it working for you now?

We were not using data packs by then.  Now uploading works for me.

Same issue here, (-1).

Anders Flygenring-Harrsen

(Unassigned)

Retrieved