failed to synchronize registry data from server minecraft что делать
[1.16] «Failed to sync registry data with server» #2556
Comments
Khytwel commented Oct 7, 2020
Many people who play on our Valhelsia 3 modpack encounter this problem when connecting to their server (Failed to sync registry data with server).
On our side, we looked a little bit at the logs and the same problem seems to happen every time.
For some reason, the client-side configuration file seem to be enabling matrix enchanting sometimes even when it is disabled in the config (it is also disabled on the server side by default). This breaks everything.
The problem is sometimes solved by restarting the modpack or making a new installation which is very annoying.
Here is the client-side logs file: https://gist.github.com/Khytwel/d56d2aa8bf2bdae0863effbb7d7a4747
Quark version: r2.2-262 (version used on the logs provided)
The bug is still present on the latest version.
The text was updated successfully, but these errors were encountered:
HowellTheOwner commented Oct 10, 2020
My friends and I have consistently day by day had to go through and copy a fresh server file to our personal client side which i actually have to download from the server itself, it’s been quite trouble. I can upload client logs as well but it’s the same as the original post and server side seems to somehow be changing day to day.
Londran commented Oct 10, 2020 •
Same issue. Log attached from client.
Was able to resolve it, do not know if temporaly:
Attaching log of failed attempt
client.log
UPDATE: false fix. only randomly working :/
100xdonaldx001 commented Oct 12, 2020 •
Well we hopefully fixed that issue
with deleting Quark Oddities from our server and Clients.
We also deleted all the config parts in the Quarks Config from Oddities
Edit: Again just a temporarely Fix like the Person above me.
But we cant figure out where the problem is since when we start over GD Launcher we get that error bot over Twitch we can just join.
martindanielsson commented Oct 13, 2020
Well we hopefully fixed that issue
with deleting Quark Oddities from our server and Clients.
We also deleted all the config parts in the Quarks Config from Oddities
Edit: Again just a temporarely Fix like the Person above me.
But we cant figure out where the problem is since when we start over GD Launcher we get that error bot over Twitch we can just join.
What is your log file saying is wrong, after you’ve removed Oddities? We’ve run into similar issues on our server. Just trying to debug.
100xdonaldx001 commented Oct 13, 2020
Well we hopefully fixed that issue
with deleting Quark Oddities from our server and Clients.
We also deleted all the config parts in the Quarks Config from Oddities
Edit: Again just a temporarely Fix like the Person above me.
But we cant figure out where the problem is since when we start over GD Launcher we get that error bot over Twitch we can just join.
What is your log file saying is wrong, after you’ve removed Oddities? We’ve run into similar issues on our server. Just trying to debug.
Well its the same error as the first post.
even tho the mod isnt on the server or in any client configs.
Some players can still join the server with the mod still installed, some cant join it anymore
some players fixed it with installing a fresh version of the Forge versios we are using (1.16.1-32.0.108) and joining afterwards
so its still random.
jblosser commented Oct 13, 2020
This is also present on 1.15.2, with Quark-r2.1-245.jar. It all works fine locally but once I start up a remote server and try to connect, I get the same failure and very similar debug.log with registry errors around matrix enchanting, despite having it disabled in the config. The client and the server have 100% the same config file, but that doesn’t matter.
jblosser commented Oct 14, 2020
I did some digging and it appears this only shows up with Apotheoisis also loaded. I have that in my list, and I see the original report mentions Valhelsia 3, which also includes it. The latest Apotheosis for 1.15.2 is Apotheosis-1.15.2-3.3.7.jar. If I downgrade to Apotheosis-1.15.2-3.3.5.jar, I don’t see this error. I’m not running 1.16.x so I didn’t try the same checking around there, but based on release dates you might try Apotheosis-1.16.2-4.2.1.jar.
leahlouisa commented Oct 18, 2020 •
Same issue. so far only our player who has played a singleplayer Valhelsia 3 game is having the issue.
Edit to add: not sure if it is purely a coincidence or not, but of the 5 players on our Valhelsia 3 server, 2 players tried the modpack out singleplayer before joining, and three players did not. Only the two players who tried out a single player game first are having the issue. They have tried deleting and replacing their quark-common.toml file multiple times; sometimes it seems to fix things and sometimes it does not. Completely uninstalling and reinstalling the modpack doesn’t seem to help.
martindanielsson commented Oct 18, 2020
Vaelzan commented Oct 19, 2020
@martindanielsson Quark is (for the moment) on 1.16.1, the Apotheosis patch was for 1.16.3. A 1.16.1 version with the patch was not released and is not planned to be (according to the Apotheosis developer), so the uploaded fix won’t do anything at all to help with this issue since they’re different Minecraft versions.
martindanielsson commented Oct 19, 2020
@martindanielsson Quark is (for the moment) on 1.16.1, the Apotheosis patch was for 1.16.3. A 1.16.1 version with the patch was not released and is not planned to be (according to the Apotheosis developer), so the uploaded fix won’t do anything at all to help with this issue since they’re different Minecraft versions.
Shoot! I didn’t see he had already upgrade to 1.16.3 in the 1.16 branch 🙁
100xdonaldx001 commented Oct 19, 2020 •
Well we hopefully fixed that issue
with deleting Quark Oddities from our server and Clients.
We also deleted all the config parts in the Quarks Config from Oddities
Edit: Again just a temporarely Fix like the Person above me.
But we cant figure out where the problem is since when we start over GD Launcher we get that error bot over Twitch we can just join.
What is your log file saying is wrong, after you’ve removed Oddities? We’ve run into similar issues on our server. Just trying to debug.
Well its the same error as the first post.
even tho the mod isnt on the server or in any client configs.
Some players can still join the server with the mod still installed, some cant join it anymore
some players fixed it with installing a fresh version of the Forge versios we are using (1.16.1-32.0.108) and joining afterwards
so its still random.
Need to update my message here. After a couple days everyone got their errors under control with the things I already said. We all looked at each other’s logs and could eliminate all the errors that were made by cleaning up their files from quark oddities. Everyone can connect to our server fine now. And over the last days noone got the error anymore.
So I can say it was a successful fix it just took some time for everyone to set it up right.
So it was my mistake here that I said it didn’t worked.
Edit 1: Hope that others can test this fix too and say if it worked or not.
Edit 2: we just installed a gravestone mod instead of the one oddities had
Fix: ‘Failed to synchronize registry data from server’ Minecraft
Minecraft is a 3-D computer game in which players may construct anything. The game, which has been compared to an “online Lego,” includes assembling bricks and constructing buildings across various locations and terrains. The game takes place in a virtual environment and includes resource collecting, creating goods, construction, and fighting.
It is now one of the most prominent games in the world and maybe a great method for children to educate about innovation and teamwork.
Minecraft may be played on a computer, a smartphone, a tablet, or a gaming console. Depending on the gadget you choose, the game may cost about €20.00.
Minecraft is very popular among children, especially those aged 6 to 13. The fact that players may build anything is what makes the game so popular. There are no restrictions in the game, and the options are limitless, from cities to roller coasters and everything in between.
The game also has a multiplayer option, which is popular among young players who love playing with their friends and assisting one other in building new inventions. The flexibility that the game provides is appealing to the majority of youngsters.
Fix: ‘Failed to synchronize registry data from server’ Minecraft
Recently, players in Minecraft have been reporting an error which has proven to be quite frustrating.
Several players have resorted to social media to report that they are facing an issue where they constantly receive the message, failed to synchronize registry data from the server.
Now, as per our understanding, this error usually appears when players are using mods in the game.
Generally, the game means that the player doesn’t have the same versions of some mod. It could also be a problem with the client log.
Minecraft has made it possible for its players to add a wide array of mods to their servers. So, as a result of that, players have been implementing a lot of mods on their games.
Apart from that, it has also come to our attention that people who have a different version of Forge installed on their device are encountering this error more than the others.
If the version of Forge installed on your device is different from the version of the server, then you might get the failed to synchronize registry data from the server closing connection in Minecraft error.
Because of that this error has been popping up and hampering the gameplay of a lot of people from the Minecraft community.
In the following segment, we will be discussing how you guys could go about trying to solve the issue at hand so you don’t have to compromise on playing Minecraft again
#1 Verify that your mods and client are running the same version.
Step 1: Check the mods
To commence, we’ll look at the most frequent source of the problem. It is very simple to install various versions of modifications and the Minecraft client by mistake.
Step 2: Ensure all of them are on the same version
As a result, you must ensure that all of them are in the same version. There is no way they will function if they are not operating on the same version.
Step 3: Upgrade the client if necessary.
Upgrading the client is simple and may be completed in a single step.
Step 4: Verify and check the mods
The modifications, on the other hand, are a different story. You would need to go through and verify each of them one by one.
Step 5: Update as per requirement
After you’ve upgraded everything that’s required, things would be back to normal.
This technique, unfortunately, will not work for everyone. If you’re still not receiving the results you want, it’s time to move on to the next stage.
#2 Verify that you have most recent version of Forge installed
Although this preceding solution should have worked for most of you, there are still a few additional possibilities that may be causing the issue that we require to rule out.
Step 1: Check for missed updates
Another frequent reason for the issue is that you are not using the correct version of Forge. Possibly you unintentionally skipped an update.
Step 2: Install the latest version of Forge
Given that almost every online Minecraft player will have Forge installed, it is critical to stay up to date on version updates in this area as well.
Step 3: Keep an eye out for future updates
So, all you have to do here is keep an eye out for developments.
Apparently, this would have worked for many of you, but not for all. So, if you’re still experiencing issues, it’s time to attempt our last solution. This one raises the stakes a bit, but it will offer you a good chance of getting back up and running.
#3 Uninstall All of Your Mods
Though this may seem to be an outlandish idea, it would not be here if it did not function.
Step 1: Delete corrupt Mods
At this point, if nothing else has worked, we can only blame the issue on a faulty mod that is wreaking havoc.
Step 2: Find and locate the Faulty mods and uninstall
So, the only logical next step is to uninstall your modifications one by one.
Step 3: Check the servers in Between
While you’re at it, be sure to give your server a shot after each one. This way, when it starts working again, you’ll know which mod caused the issue in the first place.
Yes, we agree that this may be time-consuming, particularly if you have a lot of modifications running, but it will help you get to the bottom of it.
Follow us on Twitter & like our Facebook page for more post-updates.
Check out related Minecraft posts
Abhigyan identifies himself as a tech geek, gaming cognoscenti, and also a connoisseur of music. Unidentified and mysterious phenomena never fail to gather his undivided attention. When not reading about bizarre and perplexing entities across the Universe, he can often be found cheering for his favorite teams in Football.
Failed to synchronize registry data, closing connection on 1.16.5 #3270
Comments
Sorrow-Scarlet commented Jul 1, 2021
The text was updated successfully, but these errors were encountered:
Vazkii commented Jul 18, 2021
Is this a vanilla server?
Vazkii commented Jul 18, 2021
Oh, it’s definitely not vanilla if you have quark chests.
This strikes me as suspect in the log. What mod is this?
Sorrow-Scarlet commented Jul 19, 2021
oh. first,this is not a vanilla server,i just played with my friend,haha
not a real big server,p2p,
second i suspect this mod is Project:War Dance,this was the only mod which changed the combat mode.
link:https://github.com/Jackiecrazy/WarDance
but i need to say. my friend an me didn’t meet the crash and the error of Failed to synchronize registry data, closing connection until we developed certain level of the game,the interference factors are too more. first i was not a vanilla,and i used about 110 mods（but over 30mod were performance improving mods,haha）,which contained botania,slashblade,
my friend and i wanna keep quark still, ’cause quark chests contained all of our items. and our caves cant work without quark
Sorrow-Scarlet commented Jul 19, 2021
by the way,my device: 16g 3200mhz rtx 2060 R7 4800H
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Failed to synchronize registry data, closing connection on 1.16.5 #3270
Comments
Sorrow-Scarlet commented Jul 1, 2021
The text was updated successfully, but these errors were encountered:
Vazkii commented Jul 18, 2021
Is this a vanilla server?
Vazkii commented Jul 18, 2021
Oh, it’s definitely not vanilla if you have quark chests.
This strikes me as suspect in the log. What mod is this?
Sorrow-Scarlet commented Jul 19, 2021
oh. first,this is not a vanilla server,i just played with my friend,haha
not a real big server,p2p,
second i suspect this mod is Project:War Dance,this was the only mod which changed the combat mode.
link:https://github.com/Jackiecrazy/WarDance
but i need to say. my friend an me didn’t meet the crash and the error of Failed to synchronize registry data, closing connection until we developed certain level of the game,the interference factors are too more. first i was not a vanilla,and i used about 110 mods（but over 30mod were performance improving mods,haha）,which contained botania,slashblade,
my friend and i wanna keep quark still, ’cause quark chests contained all of our items. and our caves cant work without quark
Sorrow-Scarlet commented Jul 19, 2021
by the way,my device: 16g 3200mhz rtx 2060 R7 4800H
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.