When pressing the "Minecraft Realms" button to bring up the list of realms I have joined, I get the following error message with no other details:
"Realms (429):"
Everything was working just fine less than 30 minutes ago with no new changes or configurations made since then.
Restarting Minecraft does not fix the issue.
Linked issues
is duplicated by 91
Attachments
Comments 147
Issue still persists.
I confirm it is present as of time I write this comment.
As this is paid service I'd assume this type of tickets should be handled quite let no one from Mojang team are not even changing state to Confirmed.
While resolving this issue please provide references how can one who pays for service can get refund for unavailablity time.
I assume this type of complain should be covered by Terms of Service.
Had the same problem, but fixed it:
in the Minecraft, launcher go to installations
go all the way to the right on the latest release tab
you will see "play" and 3 dots
Click on the 3 dots and then click on the duplicate
finally, run the game on the duplicated version, should say Latest release (2)
I also found a fix, different from yours Logan, all I did was shut my computer all the way off and turned it back on, if you have tried uninstalling Minecraft and it still doesn't work, you should try powering down your system, for me I had to do it three times but now its all fine, I believe it is because every so often, java gets confused with a computer.
i am having the same issue. i am unable to open the realms tab. does anyone know how to fix this issue?
same issue fine 10 mins prior to trying to relog
duplicated installation
ended all java programms
restarted pc
I had this same problem. I tried Logan and Andrew solutions and they didn't work. I uninstalled and reinstalled the launcher and it worked after that.
I too have this issue. I have 2 computers that are in the same network, On both computers when using 2 different accounts and in menu when trying to click on Minecraft Realms it just says Realms (429):
Both are windows 10 computers running Java edition of Minecraft
I have tried renewing my ipconfig, uninstalling + reinstalling minecraft (both launcher and game), shutdown my network for a while, restarting computer several times, killing all java programs. I also tried to run older version of minecraft and tried to duplicate the latest version. Both computers still not working. This has been going on for a week or two maybe. Everything else seems to work as they should except realms. Luckily I'm still on the free time for my own Realm and if this issue persists I might not continue my Realm subscription because this has now happened several times. I bet if I try again in 4 or 5 hours it will work. But now it has been giving this error for the last hour or so.
i tried Sohpias solution and it worked for me. Just delete the minecraft launcher and install it again. No data will be lost doing this btw.
I was having the same issue, first time I resolved it I restarted my computer. 2nd time it started happening I opened the Minecraft launcher as an administrator and it started working again, these two solutions I believe have nothing in common so a proper fix is probably not easy to do or possible client side.
Me and my girlfriend are playing from the same IP. Could that possibly have something to do with it?
I tried several of the suggestions in this thread, but to me they all seem like descriptions of doing something that takes a little bit of time, and then the error incidentally went away after some time had passed.
For me what finally did the trick was to switch my laptop off of Wifi over to a tethered 4g connection from my phone. Once I had loaded the list of realms servers, I could switch back to Wifi again, and connect without problems.
Happened to me today (8 Dec). Quitting out of Minecraft and relaunching 3 times did not resolve it. Rebooting the PC did, but I agree with the comment about the particular steps not being important. It seems like the bug is caused by planetary alignment.
And after 5 minutes of waiting it disappeared. Please fix this Mojang, or at least give this bug some attention.
This is an issue I've been having for several months. The only lead I ever saw on it was that "429" was a Network Code to say "Too Many Requests". Now I don't have enough knowledge in the field to know that for sure or what it really means at the root level, but I have to lean towards that because:
- Rebooting the device
- Reinstalling Java
- Deleting all Minecraft files and restarting the client launcher,
All worked for some people, and didn't work for others.
The most common "fix" is to simply 'give it a while'. One of my buddies got into a realm we all play on just fine and I couldn't so it has nothing to do with the realms themselves, just the option to access a page that connects us to servers that ping back info for the "realms" servers themselves (Which is apparently hosted by Microsoft, who would have thought?). Another observance; my buddy that was in just fine is way out on the other end of the states from where I am, and they had 0 issues while I waited ~20 minutes for the 429 to clear. So I'm throwing it to the wall just to see if it sticks... I know that some video game companies have large server centers spread out throughout major areas, so I'm going to assume some of them are just being overloaded.
That is my best educated guess. Hope this helps someone or sparks something.
this is happening to me, my friends all live less than a mile away so we couldnt be different servers
3 hours ago, I bought Relam for the first time, and I have been watching 429 error for 3 hours now.
Now I can see why my friends don't recommend Minecraft to me.
I just had the same 429 error. For me the issue resolved itself after about 30 minutes. Obviously not a solution for everybody but thought I'd chime in.
this error is back again, i haven't been able to connect for over an hour now, im on windows 10, java edition, i have tried restarts of the client and my pc, don't work with modded clients or vanilla
I am experiencing this problem now and for several minutes.
It's not clear whether the 429 refers to HTTP Status code 429 "TOO MANY REQUESTS" which would suggest clients are getting improperly rate limited (since we get it on the first attempt to connect).
Same issue. This has happened multiple times over the past 2 weeks. Waiting some unknown amount of time, this eventually resolves itself. VERY FRUSTRATING.
Getting this as well. Very disappointing 😞
I wonder if it's poor server-side spam protection? Currently waiting sadly…
I have reinstalled Java, connect to a server, then try, I have done everything possible and this comes up. Another member of my realm was getting the same thing and reinstalled MC to fix it. I refuse that as a solution. The last time I did that I lost my skin and there is no way with all that I have going on in my folder am I going to even try that... I have 3 realms between Java and Bedrock...if you want me to keep them, this needs to go away.
11:31:08.258
Realms error code: 429 message:
11:31:08.259
Couldn't connect to realms
429
at dgb.a(SourceFile:432)
at dgb.i(SourceFile:200)
at dfw$1.run(SourceFile:530)
Also having this issue. Worked fine, logged out for 10 minutes and now we can't join again, no changes made in the 10 minutes we were logged out. Hoping this will be resolved soon.
extremely disappointed that the workflow says this issue is POSTPONED when so many people are having the same issue. Just made my own post to hopefully get them to fix this for a PAID SERVICE
it just happened to me. I played Realms yesterday and it worked, nothing can fix it... Except Mojang so please fix it Mojang.
Came here to add "me too"
Yesterday it was myself and my daughter.
Today it's myself and my brother-in-law.
Followed some suggestions found on reddit (eg, re-installing, turn off java updates, run as admin), worked for me yesterday, but today I don't want to re-install. That's madness.
I thought it might be something to do with 5 of us coming in from the same IP address (we are currently staying at my BIL's place), but we have had all 5 of us in the realm. I'm the realm admin and I can't even get into the realm admin page/menu
edit: the time it took me to get this typed up, I tried again, and now I'm in - no changes. In fact I left the client running. Conclusion: not a client-side thing.
Yeah, I'm having the same issue.
Two of the people that I play on the realm with aren't able to get in (the others haven't tried). We've been researching this for about half an hour and after restarting our computers several times, still no change.
We only have another hour until one of them has to leave to fly back home. We were hoping to get some more time together in person playing on the realm, but it's not working.
This issue is really upsetting. Please fix.
edit: Well, it's working now. Don't know why you have to wait 30 minutes for it to work again. Very strange.
This is a possibly unnecessary reminder for all of you who have been bit by this bug to vote for it (upper right corner of the window). I expect Mojang prioritizes their bug fixing by how many people are affected by the bug. As of this moment, this bug is not assigned to any bug fixer.
Jeff, just to inform you, voting for a ticket gives Mojang a basic idea of how many people are affected by the issue. Voting for it will not get this bug fixed, or seen to any quicker.
Avoma, I'm not saying you are wrong, but if that is the case, then voting is utterly pointless. As a US citizen, I'm hoping that is not the case! 😃
From what I understand this has been a reason for some time. Couple of friends of mine have said they have been having this issue with Realms (first instance must have been over a month ago), and all they could do is wait for it to fix itself). Today I have been having the same issue myself.
It would be greatly appreciated as myself (and many others I assume) are long-time subscribers of Minecraft Realms, and we would like to be able to at least utilise the product for which we are paying.
I'm experiencing this issue and so are my friends! We tried restarting our computers as well as deleting and redownloading the game. Very frustrating to see that many other people are experiencing this issue and it has not been resolved yet.
Logging onto a regular multiplayer server and then trying realms again seemed to solve the problem for me.
11:48:54.49411:48:54.494Realms error code: 429 message: 11:48:54.494Couldn't get server list - 429 at dgb.a(SourceFile:432) at dgb.e(SourceFile:151) at dhl$c.a(SourceFile:208) at dhl$c.run(SourceFile:200) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)11:48:54.513Realms error code: 429 message: 11:48:54.513Couldn't get live stats - 429 at dgb.a(SourceFile:432) at dgb.f(SourceFile:169) at dhl$a.a(SourceFile:274) at dhl$a.run(SourceFile:267) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)11:48:54.523Realms error code: 429 message: 11:48:56.451Stopping!11:48:58.070
11:48:58.070Process ended with exit code 0
I have this issue also, i bought realms today cause i finally convinced my friend to play Minecraft with me. so she bought the entire game today just to find out we can't play together.
I'm tried everything in this thread, re-installed Minecraft and java, deleting the appdata for Minecraft, disabling automatic updates. waiting and trying again. nothing is working.
minecraft took us for a 50$ scam today.
I just received this error report on the realms just a few minutes ago. I tried the suggestion from David Foght restarted Minecraft two times and it started working again. I don't know if it was a direct fix or if it decided to start working again.
@kun__
From what I can tell, the error occurs when there has happened to much to the server administratively (reset many worlds, creating new worlds, anything in the configuration).
I got the error again even with the auto-updates turned off, but after waiting half an hour, where I had closed minecraft, it worked again.
I think that Mojangs servers think that we try to DDOS them, when we do to many things, and thats why they're cutting our connection.
TL;DR
If the disabling automatic Java updates didn't work, try closing Minecraft for about half an hour, and then maybe it'll work.
When I open control panel and search in programs for java nothing actually shows up. I have minecraft launcher there but that is it. Anybody know where I might be able to find java in my files?
I have this problem normally when I leave the home screen on for some time. Nothing I do to try to get back into my realm will work. I continue to get this error code. Does anyone have any advice?
I also use optifine it does not matter if I start the game with or without it. The game still gets that message.
I don't remember seeing this years ago when I tried realms. Tried all the things. Still have the same issue on three PC's. Super frustrating to see this after just making a decision to move from a third party VPS instance to realms for my family. I would have expected Mojang to be more proactive about this. I wonder if a refund is possible? Don't know what I'm paying for if the vendor isn't going to take this seriously.
I have this issue now. It has previously affected another player on the same realm I play on. For him it happened after leaving the home screen on for some time, though this is not the case for me now. I just launched the game not having played for a couple of days and wen't directly to the realms menu. I have MacOS and he has PC. I was playing on the Realm without any issues when it was affecting him. He did not find a clear way of fix it, but tried restarting the game, restarting the computer, selecting different installations (optifine, plain vanilla, etc.), reinstalling the game, disabling java autoupdates and so on. For him realms was working fine again within an hour, but it is unclear if it was his doing.
Mine was working correctly last night (12.26.20) but is getting this error now. My Java last updated on Friday, but it has worked since then. Today at noon, it isn't working. I've relaunched several times and rebooted twice.
I've been having this issue off and on for the past few days. It works if I switch to using the hotspot from my phone, but I get the error when I play from my home network.
Taken from Reddit (All credit to https://www.reddit.com/user/Nightshade_XD/)
in the Minecraft, launcher go to installations
go all the way to the right on the latest release tab
you will see "play" and 3 dots
Click on the 3 dots and then click on the duplicate
finally, run the game on the duplicated version, should say Latest release (2)
I've been reading all the comments on this bug since it happened to me. It seems likely that the bug is on the server side, and that none of the tricks anybody does on the client side are actually solving the problem. I think the only thing the tricks accomplish is to spend some time. It may be that simply closing Minecraft and finding something else to do for 30 minutes (or an hour, or whatever) would work just as well as the trick.
Does anyone else have any suggestions? I've been trying to do a lot of the suggested ways to fix the error including restarting my computer, running minecraft as administrator, the way mentioned by Barnav and much more. I need to be playing though because I have some videos to release pretty soon
Seems to be a timed issue with too many requests from sitting at the main menu.
The only way I've been able to 'resolve' it is to close the game for a few minutes and come back. The majority of 'google' fixes include this fix without them knowing as well.
As a paid subscriber of Relms, it's a little strange to me that Mojang hasn't done anything to resolve this as this is effecting everyone as of now.
One thing that worked for me was checking the port forwarding in this article: https://help.minecraft.net/hc/en-us/articles/360035130871-Java-Edition-Realms-connection-issues-
I didn’t actually forward the ports because they don’t have to be forwarded for Minecraft to work, but I had port 80 and 443 forwarded to another computer. When I removed the port forwarding rules to the other computer, the 429 error went away immediately.
NONE OF THESE WORK:
Duplicating the game "clicking on 3 dots" doesn't work.
Restart doesn't work.
Log out / login doesn't work.
Restarting network settings doesn't work.
Turning off Java updates from Java Control panel + restarting.
WHAT WORKED FOR ME:
What "worked" for me was switching from Wired Ethernet to Wifi on the same network. Not sure if this was even the culprit.
TECH DETAILS:
11:48:54.49411:48:54.494Realms error code: 429 message: 11:48:54.494*Couldn't get server list - 429* at dgb.a(SourceFile:432) at dgb.e(SourceFile:151) at dhl$c.a(SourceFile:208) at dhl$c.run(SourceFile:200) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at
Also getting this issue, nothing seems to resolve it, all the "fixes" seem to do is just waste time whilst it sorts itself out. I would really like to know something is being done about this, as my friend is not paying for a Realms server for it to be inaccessible when it is supposed to be available 24/7
Same thing happened to me after resetting a world that kept crashing the realm. have not found a fix but i am going to try to switch to a different wifi or something along the lines of that.
I think it is something to do with the requests to the server from your client being left open, as '429' is the HTTP error code for 'Too Many Requests'. However this is too annoying! I left my game open on the Realms screen for less than 5 Minutes, and when I came back I could no longer connect with the 429 error. A client update to send less requests or a server update is urgently needed.
I've gotten past the screen popping up after selecting the realms tab but when trying to join a realm it says "Connecting to realm" then at the bottom there is a red "-429"
Listen everyone.... this is not going to be fixed unless we flood these people with requests. Its an issue with their client sending too many requests. Go to the report a bug page on mojang's website, send a bunch of requests.. it is unacceptable that they have closed this issue that is clearly affecting so many people. It also seems to still be unassigned to anyone on their team. Even if the issue has gone away for you temporarily it WILL come back trust me. Send bug reports, heck even create more duplicate threads to GET THEIR ATTENTION!! For a paid service!!!
I also just encountered this problem. I was afking in the nether in the realm and was kicked for idling. when I tried to reconnect, I got the 429 error. Resetting internet connection didn't work, and duplicating the installation did not work either.
Listen everyone.... this is not going to be fixed unless we flood these people with requests. Its an issue with their client sending too many requests. Go to the report a bug page on mojang's website, send a bunch of requests.. it is unacceptable that they have closed this issue that is clearly affecting so many people. It also seems to still be unassigned to anyone on their team. Even if the issue has gone away for you temporarily it WILL come back trust me. Send bug reports, heck even create more duplicate threads to GET THEIR ATTENTION!! For a paid service!!!
By posting more requests you're not getting Mojang's attention, you'll just waste our time (and we're volunteers, not Mojang staff). This issue is not closed. Note that currently most Mojang staff is on vacation due to the holidays. Please be patient.
I just ran into this issue today when trying to get onto a realms server. Restarted the program a few times, and it still threw me the "Realms - 429" error. Resetting my internet did not work, HOWEVER, restarting my computer did immediately resolve the issue for me. First try. Hope this helps this issue along.
I've been seeing this "Realms (429):" error with greater frequency since November. I'd like to know what other fixes folks have found besides a full computer restart (edit: which didn't work for me, just tried it). Its very inconvenient to have to restart the computer about every time I wish to play minecraft.
Aric Goe - I don't think there is anything you can do except wait a few minutes and try again. Each time somebody posts a possible solution (such as rebooting) that worked, somebody else will say that they tried it and it didn't work for them. All of these attempted fixes take some time to complete, and I think it's just the passage of time that resolves the problem.
Same comment as Jeff. The best "fix" seems to just go grab a drink and wait it out for a few minutes. Any so-called fix shared here just sounds, as Jeff stated, as a consequence of time passing by while attempting things and the issue resolving by itself.
Just got New Years in my country, greeted with "Realms (429)". What I'm interested in is: what does the 429 mean? Is it an error code? Is it something Mojang just trashed onto us? Lots of questions.
I can't believe that with all these issues on the same error reported, no one besides @violine1101 has responded to this issue or acknowledged that it is being worked on. This issue has been popping up for me repeatedly over the last 2 weeks and there is no safe fix to get rid of this issue.
This has been like this for me now for 5 straight hours with no change. I was able to log in this morning and after I came back from work, I am unable to even see my realm page like many of you here. I'm hoping Mojang considers refunds for this month for those of us who own realms that aren't able to get past this page. I get better connection reliability when connecting to a server from a free make your own server website.
Our group of 4 players have been hitting this problem once to twice a day over the past three days. The problem is intermittent, but when it occurs it seems to last for at least 10-20 minutes. One outage was a couple of hours. Other websites work and we can watch movies – this does not appear to be a local internet connection problem.
It has been two hours and trying to connect to Realms still gives the (429) error message. What's up with the Realm servers?
I've just started my 30 days trial period and I could play 10 minutes, after that "REALM 429" appeared and here I am... I can't play, this is disgusting...
Running Minecraft launcher as administrator on Windows 10 (right click launcher and then click "Run as Administrator") seemed to work for me, and seems to work for some other people on Reddit also - but not everybody. Also, error seems to be client-side as my friend could get onto the Realm while I had this issue?
I took the following steps to get around the issue:
Ran launcher in administrator mode
Created a profile for the 1.16.3 version
Launched the game with the 1.16.3 profile
Closed Minecraft
Switched back to my latest release profile
Launched the game
Was able to join my realms server without the error appearing
tl:dr They are working on a fix! I got confirmation in a bug report I sent a while back, "We apologize for the inconvenience to your Java Realm, this outage was caused by a known issue. The team is working on a fix that we hope can be delivered as soon as possible."
@violine1101 well you should be getting paid for this I for one did not know that's how this platform works, however I am quite ashamed that it is being construed as a matter of patience, all anyone has to do is give the community an update and say that they are working on it! We have gotten no confirmation that it is being worked on and it strikes me as unfair that they are leaving it up to a volunteer to communicate that... the least they could do is let us know what is going on... we understand that everyone is on break but you also have to understand that paid services should have 24/7 working teams, an extrapolation but if everyone's phone service went out you wouldn't tell them to just be patient. The last bug report that I sent I got a response saying that this is a known issue though so maybe if a mod could update everyone and say that they are working on a fix it might dissuade any angry commenters! thank you for your service.
Excellent news, sam, but it makes me wonder what this web site is for. As I write this, it still says "unassigned" in the upper right corner.
Been happening for days, can't get on. Time to cancel realms account and use one of the MANY Minecraft service hosting places which are actually cheaper. Paying more for better QOS is fine, but when product is completely unusable - FREE would be too expensive. This is NOT a new issue, has happened on and off for months, but now it is persistent. They should have fixed this months ago. Good bye realms.
And no, they are NOT working on it as an above commenter said. If they were, the Assignee would not say "Unassigned".
I am also experiencing this issue. The first time it happened, I restarted my computer and that seemed to work, however, now that is no longer a fix. I've seen some people say it is supposed to be caused by too many requests or something, but I had not been on realms for over 12 hours. Restarting minecraft also does not fix the issue.
I've had this issue on my realm for a few weeks now and it's happened for all users. It happens for up to sometimes an hour then randomly goes away, and sometimes it's just for one user while others are on the realm playing. It just kicked me off now with the error. Like with others, restarting the game, or computer, or ip doesn't fix it.
Can we receive an update on this please? This was reported 23rd November and there is still no-one assigned.
I hope this error gets solved. idk whats wrong, i left the realm just to make it morning and now i cant go back ;-;
Two other people are in our realm but I'm not even able to get to the realm menu. I was playing just fine a few hours ago, but now no matter how many times I restart my computer or the launcher, nothing changes.
Just happened to me too. I also have tried restarting everything, without any success. The fact that this issue has been around for over a month without any solution is not acceptable and needs to be fixed ASAP.
Getting this issue for the first time on 1/3/21. Tried every solution in this thread, plus a few others from the realms subreddit. Simply leaving it alone has done absolutely nothing, even after an hour plus of waiting. Kind of ridiculous that this hasn't even been assigned yet. And as a response to the mod who seemingly answered angrily and told us staff was "on vacation for the holidays", this issue was reported on November 24th. It has been almost a month and a half and no answer or even attention from staff whatsoever.
Keep in mind that Mojang maintains an internal bug tracker as well; just because something is not assigned on Jira does not mean it's not being investigated. If Player Support is saying it's a known issue and is being worked on, it's a known issue and is being worked on.
I got home from a stressful day at work, and all I had to look forward to was playing some Minecraft with some friends. All day long it's been 429 over and over! I've tried every possible solution and absolutely nothing has changed. I've been checking back every 20 minutes or so, and I still can't log in. I just want to play some minecraft on the realm I'm paying for. This still hasn't been fixed or even acknowledged by the devs since November? Get your stuff together Mojang, this is ridiculous.
Ultimate fix
Since voting on this ticket seems not to bring enough attention of Mojang to resolve this issue promptly and issue occurs more and more I looked how this can be resolved by me, a paying client.
After looking at available options I decided to Vote with my money i.e.
Cancelling Realm Subscription and moving to Apex Minecraft Hosting.
Had minor issue migrating world to their server (custom requirement of mine) - got perfect customer support at first contact.
Now that I see how alternatives works won't go back to Realms anytime soon.
Just happened to me...it's been over 2 hours of receiving the error message. Used that time to uninstall/reinstall/restart everything (java, launcher, instances) as per suggestions in all the feeds. Nada. Going to be checking into Apex as well.
Just happened to me, tried all the solutions above, then tried to launch mc connected to another internet spot (like your own phone one) and now its working. Good luck.
Not sure if its coincidence or not (didn't spend long investigating). Just purchased Realms for my son and got this error straight away on Windows 10.
Launched "Windows Firewall with Advanced Security" and disabled the 2 x Java inbound rules that block Java connections, realms started working. I've since enabled the rule again and it still works.
After poking around the launcher logs i discovered it was complaining that my PCs time was off by more than 90 seconds. I synced the time and no longer get the error. Don't know if it was a coincidence.
I am getting so frustrated with this unresolved issue. It is a waste of my time and money. What other online game has errors where you can't even log into the server your paying for!
I'm kicked out again. I feel like this issue isn't getting enough attention. The work flow isn't even "in progress" or assigned to anyone. I might do @unknown's ultimate solution and get another server provider. At least then I could use mods too.
Mac OS X 10.15.7 - Using the distributed JVM with Minecraft. None of the solutions listed work. Seems random as to whether you get in. Have dried using Open JDK as well and no joy.
What is interesting is that the 429 shows up before even clicking on the join realms button and keeps repeating the same error every couple of seconds. Seems like a polling service is failing.
Debug output is:
19:15:54.997
dgb
pool-2-thread-1
Realms error code: 429 message:
19:15:54.998
dhl
pool-2-thread-1
Couldn't get pending invite count - 429 at dgb.a(SourceFile:432) at dgb.k(SourceFile:324) at dgb.j(SourceFile:319) at dhl$b.a(SourceFile:235) at dhl$b.run(SourceFile:228) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
19:16:04.991
dgb
pool-2-thread-1
Realms error code: 429 message:
19:16:04.991
dhl
pool-2-thread-1
Couldn't get pending invite count - 429 at dgb.a(SourceFile:432) at dgb.k(SourceFile:324) at dgb.j(SourceFile:319) at dhl$b.a(SourceFile:235) at dhl$b.run(SourceFile:228) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
19:16:14.995
dgb
pool-2-thread-1
Realms error code: 429 message:
19:16:14.995
dhl
pool-2-thread-1
Couldn't get pending invite count - 429 at dgb.a(SourceFile:432) at dgb.k(SourceFile:324) at dgb.j(SourceFile:319) at dhl$b.a(SourceFile:235) at dhl$b.run(SourceFile:228) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
19:16:24.982
dgb
pool-2-thread-1
Realms error code: 429 message:
19:16:24.983
dhl
pool-2-thread-1
Couldn't get pending invite count - 429 at dgb.a(SourceFile:432) at dgb.k(SourceFile:324) at dgb.j(SourceFile:319) at dhl$b.a(SourceFile:235) at dhl$b.run(SourceFile:228) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
Been locked out for 3 hours now happens daily at this rate, heading to server hosted now, all yous probably should also
I managed to get it to work by launching clear profile with no mods with it. Then I closed the game and started the Forge profile and everything worked fine
Support directed me here to report that we are getting this issue with a new Realm account setup we are unable to access.
I have had this problem over the last few days. Yesterday I updated Java and uninstalled the earlier versions which fixed the issue. Today (evening), the same thing is happening. No new Java update available. Computer restart does not help. I've had a few servers previously and opted for realms for a "just works" experience.
After 10 more mins of waiting I could attempt to connect to my realm, but the connection times out. My guess is that post Christmas the servers are too busy.
This particular error (and logging in - in general - ) has always been an indeterministic annoying roll of the dice. There is obviously the wrong infrastructure/architecture being employed to handle the volume of player logins. I suspect there is a mojang/microsoft update on the horizon and Mojang is just putting most of their networking energy into that update so fixing bugs with a sunsetting infrastructure has been destaffed.
Its hard to grow and even harder to migrate to become compliant with the new master.
All users can do is continue to point at the severity of the problem.
We are considering hosting our own server because of this flaky behavior.
It's a flipping disaster when you are streaming. You have the platform built, so you have to exit the realm to add players, so if one of your followers wants to join the server, you have to disconnect, then add them, then you go to join back and this is what you get. Not only do you lose that follower, but you lose your stream.
You want us to sell your product Mojang, and we can't do that with this going on. How do we keep a straight face when dealing with this, when something like this will make or break a stream? I will tell you how, because I watch it happen. The streams goes to a different game, because the streamer has to provide content and this right here, IS NOT CONTENT.
Despite what you say @Mark J Nohr, it isn't like they are giving us the Realm for free. We pay for it. They said it will hold 10 people. They said it. They take our money and do what with it? This here has no excusable excuse. Your customers Mojang are feeling jaded. I am also looking at hosting my own server at home, and sooner than later.
[media]Note that this bug report is EXCLUSIVELY about the issue with error code 429. Any other realms issues are not the topic of this bug report. Please file another bug report unless another bug report about the same bug already exists.
I beg to differ. This is INCLUSIVE... all these errors are from the same root cause!
C:\Users\Thurman>ping api.minecraftservices.com
Pinging 39ce87f4-minecraftapi-mine-f953-1806246087.us-east-1.elb.amazonaws.com [54.156.26.181] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 54.156.26.181:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\Thurman>tracert 54.156.26.181
Tracing route to ec2-54-156-26-181.compute-1.amazonaws.com [54.156.26.181]
over a maximum of 30 hops:
1 50 ms 50 ms 48 ms 108.62.202.217
2 48 ms 49 ms 49 ms v30.ce01.chi-11.us.leaseweb.net [23.83.91.189]
3 49 ms 49 ms 54 ms ae-1.br01.chi-11.us.leaseweb.net [23.83.86.0]
4 50 ms 50 ms 50 ms te0-0-2-2.nr11.b027749-0.ord11.atlas.cogentco.com [38.122.208.241]
5 49 ms 56 ms 50 ms te0-2-1-4.rcr51.ord11.atlas.cogentco.com [154.24.43.225]
6 51 ms 51 ms 51 ms be2021.ccr41.ord01.atlas.cogentco.com [154.54.1.29]
7 52 ms 52 ms 52 ms be2765.ccr41.ord03.atlas.cogentco.com [154.54.45.18]
8 51 ms 51 ms 50 ms 38.142.66.18
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 74 ms 74 ms 73 ms 52.93.28.172
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
@unknown, your issue is REALMS-6682, which only happens since today.
This appears to have everything to do with your public IP. I change my internet connection to my iPhone hotspot and everything works, go back to my Verizon Fios internet connection and i get -429 error. I can go back and forth without changing anything but the internet connection and this is the consistent behavior. Why is my public IP getting blocked Mojang when I pay for Realms service?
Lloyd Wright: But when I had the 429 error, I was finally able to connect with the same IP. You may have identified a clue, but there's probably more to it than a specific IP address. FWIW, I've been playing at least once a day since my 429 report (near the top of the comment list), and the 429 error has happened only one time.
Jeff - I would expect that after a certain amount of time, if a public IP block on their server is in fact the issue, that they (the infrastructure team supporting the Realms servers) will release the block after a certain amount of time. That would explain why your IP could work again after some time. This dynamic block behavior is common in firewall type software as well.
My next thought is on how to avoid any behavior I am in control of that may be causing this. I'm wondering if there is some behavior like 4 or 5 members of the same family (using the same public IP) disconnecting from the realm when it is time to go to bed to fast forward to daytime. Perhaps that disconnecting and reconnecting to the realm by multiple people behind the same public IP puts us on a blacklist - this is all just speculation. My family plays Minecraft a lot more than I do and this is just the first time I experienced the 429 error.
It has been happening to me and a few of my friends for the past few months. When it happens we usually wait and then it resolves. The weird part is that sometimes one of us can get on while the others can't. I think that this is ridiculous and it should not be happening. Especially since we are paying for the subscription. Mojang should get on this right away. It is unacceptable.
After seeing that the problem might be tied to a public IP, I was able to work around my 429 using a VPN.
Llevo usando este servicio desde el confinamiento del Covid 19. Casi un año llevo ya con esto. Cada dos por tres salta con este error, al principio fue en el servidor que pagaba, ahora en el comunitario con unos colegas. Igual tenemos un rato libre para minar y no podemos, o vamos a grabar y tenemos que aplazar un evento porque no funciona. Y así desde ya 9 meses. Me parece una VERGÜENZA que a pesar de que estemos pagando un servicio, ni nos den una solución ni una compensación, cuando además se supone que lleva el sello de Calidad de la empresa porque lo lleva la propia compañía.
Muy enfadado con el servicio y seguramente para el próximo mes cambie a otra empresa mas competente.
---------------------------------------------------------------------------------
I have used this service since the confinement of Covid 19. I have used this for almost a year. Every since and then this error jumps in. At first it was on the server that I paid, now in a community server with some friends. Maybe we have a free time to mine and we can't or we are going to record and we have to postpone an event because it doesn't work. And so for 9 months. It's a SHAME that despite the fact we are paying for it, they don't give us a solution or a compensation, when it's also assumed that it bears the company's quality seal of approval because it's carried by the company itself. Very angry with the service and surely the next month I will change to another more competent company.
same here ... realms doesn't work anymore. two different machines, two different accounts. worked fine this morning ... no clue why. silly "Fixes" on the web ...
Mod violine1101 posted above "By posting more requests you're not getting Mojang's attention, ..." Another poster implied that Mojang does not pay attention to the number of votes for fixing a bug.
What is the purpose of this forum?
Having the same problem.
Been playing for a couple of days, no issues.
Today, tried logging in, getting the error.
Searched the web what it might be, found out when connecting to a different network (neighbours wifi and mobile hotspot) I was able to log in.
Suppose this has to do with an IP conflict or wrongly assigned soft-ban by Mojang..
I updated my launcher by reinstalling and clicking the repair option in the installer, this worked for me, just thought I'd share in case this could work for anyone else
was playing fine one minute, logged off the realm for a second and now im once again getting the error. Please get this fixed!
What is the purpose of this forum?
This is not a forum. This is a bug tracker. The purpose of this website is to categorize known bugs in the game and make them known to Mojang.
From my limited amount of knowledge, this bug is known and on Mojang's side, and as far as I know there's nothing you personally can do about it to fix it permanently. Unfortunately the Realms team in particular is not very communicative here on this platform in my experience.
If you have this issue as well and don't have anything useful to add, please simply click on "Vote" in order to express that you're affected as well. This comments section is not meant for discussions, it is meant for important information supplementing the bug report. Keep in mind that every comment here currently sends an email to 83 people.
I was playing on my realm and I came across this issue twice. First time I've seen it. But after some time I relaunched Minecraft and was able to play on my realm. A few hours later when I finished playing I logged out but tried to log back in and got "Realms (429):" Please fix this bug Please!!
The solution in #comment-851245 (Logan Oropallo - 27/Nov/20 3:32 AM) worked for me.
This Has Happened to me multiple times on a realm i'm apart of and it usually goes away within 30 minutes but this time it still hasn't gone away for the past 4 hours, Ive tried re-installing, force quitting and a lot of other methods people have been recommending but nothing has helped. Please fix this.
What worked for me was accessing the 'multiplayer' tab and selecting a server, joining, then cancelling before I connected. After this I could access the realms tab without the message popping up. I did not get the red text error and it allowed me to join the realm. The red text was usually solved by restarting the game.
This is what worked for me, the other solutions shown here did not, and I ended up just playing about with what I had to see if anything worked and this ended up doing that. It is possible that all you have to do is wait and this was coincidental timing, although I had only been trying to solve it for about 5-10 mins.
IMPORTANT
I just received a full refund for my realms subscription. If you have been unable to access realms like I have just send a refund request at https://help.minecraft.net/hc/en-us/requests/new
under "what is the category of your questions" select "refund"
In the description section simply reword " If we've done something that has caused you to be unable to access your Realm, please let us know, and we'll try to fix it. If we can't fix it, you may be eligible for a refund." which is in their TOS and make sure to specifically reference the realms 429 error.
There are many cheaper and better constructed hosting platforms out there to which I will definitely be moving my business and I suggest everyone else here do the same, when I got in contact with support they essentially ignored the fact that this is a known problem. You might have to send a follow up email but just repeat the fact that this is a known issue that has yet to be solved and they will comply.
IT IS POSSIBLE FOR THE OWNER OF THE WORLD TO MIGRATE IT TO ANOTHER HOSTING PLATFORM. Tell your friends!!!
additionally, if you are going to migrate I would suggest having all players empty their inventories before doing so.
As an above commenter said, Apex Minecraft Hosting is where I will likely be moving my business. Great customer support
I've been reading through endless comments and trying everything to fix this error, I've been playing on my realm for two months now and I've NEVER had an issue. The only thing that seemed to work is connecting to my mobile hotspot which allows me to finally view my realm but when i switch back to normal wifi it no longer works.
It's not an IP block. I can get a 429 error on one machine, and see the realms just fine on another machine - same network, same public IP.
Error popped up for me a few days ago, then disappeared and I was able to access my Realm fine. Came back this morning when I tried to enter. Nothing I do seems to resolve it.
The "429" error isn't a bug. It is the server stability measures kicking in. A 429 error is common on pretty much every server or website and provides prevention against DDoS attacks. This means that if you try to log into your realm too many times inside a certain time frame, the server sees all the requests sent from your machine and decides to not let any of them through. This is why you may be locked out but other users can join, since the server hasn't gotten loads of requests from their machines.
Let me reiterate: THE 429 ERROR IS NOT A BUG! It is the server's anti-DDoS system. If you get this error, it is best to leave it for 20-30 minutes and try again to let the request backlog refresh. No amount of reloading your game or restarting your system can bypass it (unless you manage to switch IPs).
There are some exceptions, though. If you are truly getting on the realm for the first time that day and you are immediately met with one of these errors, it is most likely a server-side issue, which you can contact Mojang about. But if you have been leaving and reentering your realm frequently, don't be surprised when this error pops up. If you are disconnecting as a means of vanilla-style pausing, like if you are following a tutorial in survival mode, it's best to just build a box around you so that you don't get a backlog of requests.
Hope this clarifies everything.
This would make sense if I've logged into minecraft more than once from my computer today. This was only the second time.
@nicholas, although you are technically right about the description of what a 429 error should mean, shouting "THIS IS NOT A BUG" is incorrect.
My guess is the people that are following and upvoting this thread (me included) are the ones that have this issue on the first attempt of the day. Seen by the many upvotes this issue has, I don't think it's realistic to think that so many people are "DDOS'ing their own realm" I don't think a lot of people enjoy logging in and out every second.
And even then 429 should only prevent failed login connections (hacking attempts?). I'm paying for this server, so I should be able to log in and out whenever I want. Of course there should be protection for 100 logins in one minute, etc. But not for normal use of logging in and out, let's say once every minute (as long as it's a successful login attempt).
I got this error 3 days in a row around 18:00 (CET) one time it was fixed after about 40 minutes, the next in 20 minutes, and the day after that it connected at my second attempt, 2 minutes later.
The first day my Minecraft launcher + computer was turned on the entire day on the realms screen, so I thought that might have been the issue. But the other 2 days my computer was turned off and I had the same issue.
Didn't experience the issue since 3 days now, so I'm pretty sure there is something wrong on the server side, and it's effecting a lot of people, and because we're paying for this, they should make sure this doesn't happen (I've never had this issue with netflix/disney etc, which is the same price) And i just started using realms since 2 weeks ago.
Thank you for your report!
Minecraft Realms for Java Edition has received a lot of updates and fixes over the last two years, so this issue has probably already been fixed in the meantime (e.g. because it was a temporary outage or an issue with the base game).
Since this bug report has not been updated since at least two years, please let us know if this is still an issue in current versions of Minecraft and update the bug report if applicable. If this is no longer an issue, please let us know as well. Thanks!
This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki – 📖 FAQs
I am currently having this issue as well. Tried restarting Minecraft, I even tried restarting my laptop. Super frustrating.