3 formas de solucionar el error al sincronizar los datos del registro desde el servidor en Minecraft (09.24.21)
En Minecraft, los jugadores tienen la opción de crear su propio servidor privado y administrarlo todo por sí mismos. Una vez que han comprado un servidor, son completamente libres de cómo administrar ese servidor.
Lo que es más, es que pueden agregar diferentes tipos de modificaciones a su servidor. También pueden elegir quién se une a su servidor. Aparte de eso, pueden establecer una variedad de reglas de juego en su servidor para hacer cumplir algunas reglas. Por ejemplo, pueden establecer una regla que permita a los jugadores mantener su inventario incluso después de morir.
Lecciones populares de Minecraft
Como ya hemos mencionado antes, puede agregar múltiples modificaciones a su servidor. El problema es que algunos usuarios han informado que enfrentan un error que dice «No se pudieron sincronizar los datos de registro del servidor» cada vez que intentan unirse a su servidor en Minecraft.
Hay varias razones por las que su servidor podría estar mostrándote este error. Por eso hoy; analizaremos todas las formas de solucionar este problema. Entonces, ¡vamos!
La primera razón por la que este error podría estar ocurriendo podría deberse a el hecho de que tienes diferentes versiones del cliente y mod de Minecraft instaladas en tu computadora. O tienes una versión anterior del cliente o alguno de los mods instalados en tu servidor no está actualizado.
Lo que tendrás que hacer es actualizar tu cliente y cada uno de tus mods uno por uno. Después de haberlos actualizado todos, ya no debería enfrentar este error. Si todas las modificaciones y los clientes ya están actualizados, continúe con el siguiente paso.
Si ya tiene la última versión del cliente y los mods instalados en su computadora. El siguiente paso para ti sería instalar la última versión de Forge. Casi todos los jugadores que tienen mods instalados en su Minecraft suelen tener Forge instalado en su computadora.
En este caso, deberá asegurarse de actualizar Forge a la última versión. Una vez que haya terminado, y aún enfrenta el mismo problema, hay una última cosa que puede intentar.
La última razón por la que podría estar enfrentando este problema es que hay un mod que tiene un problema. En este caso, intente eliminar todos sus mods uno por uno. Después de eliminar cada mod, intenta reiniciar tu juego y cargar el servidor.
Haz esto cada vez que elimines tu mod. Con suerte, podrá solucionar el problema de esta manera.
Conclusión
Estas son las 3 formas de solucionar los errores de sincronización datos de registro del servidor en Minecraft. Asegúrese de seguir todas las instrucciones que están escritas anteriormente.
Video de Youtube: 3 formas de solucionar el error al sincronizar los datos del registro desde el servidor en 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:
We are unable to convert the task to an issue at this time. Please try again.
The issue was successfully created but we are unable to update the comment at this time.
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
3 Ways To Fix Failed To Synchronize Registry Data From Server In Minecraft
Though we normally don’t really specialize in gaming-related issues here, every now and then, an interesting issue comes to our attention.
So, naturally, we need to give it at least a good shot. Having looked into an issue that a lot of you seem to be having on your Minecraft servers, we decided to put together a little guide to clear up a few things.
Popular Minecraft Lessons
For us, one of the coolest things about Minecraft is that it allows players to create their own server and manage it as they see fit.
Effectively, you are thus enabled to build a world of your own and decide exactly what happens there. I mean, who doesn’t want that!
From here, the user can also add mods to the server to refine and modify their gaming experience. You then get to choose who is allowed into the server that you have created.
Rules can be created. The whole thing is actually really intricate, yet surprisingly easy to use when you know how to.
That being said, we know there isn’t a chance you would be here reading this if all of this was actually working as it should be.
Having trawled the internet to find the fixes that actually work, we have finally found the way to get around the “failed to synchronize registry data from server” problem that a lot of you seem to have with your servers.
So, if you are sick and tired of getting that message, we’ve got you covered. Just follow the tips below, and you should be back up and running in no time!
How to Fix Failed To Synchronize Registry Data From Server In Minecraft?
We’re glad you asked! You may have noticed that we mentioned above that it is possible to add a large range of mods to your server.
But, after doing so, a lot of users have noticed that they are starting to get errors straight away afterward.
To be more specific, most of you are getting the “failed to synchronize registry data from the server” warning every time they try to get into their server.
The bad news is that there are a huge number of reasons as to why this could be happening to you.
So, to get to the bottom of this, we aren’t exactly going to explain all of the possible causes.
Instead, we are just going to get straight into it and run through some fixes that will straighten things out, no matter what the cause. With that, let’s get stuck right into it!
1. Check That Your Mods and Client Have the Same Version
To start things off, we begin with the most common cause of the issue. It is relatively easy to have different versions of mods and the Minecraft client installed by accident.
So, you will need to check that all of these are on the same version. If they are not running on the same version, there is no chance that they will work.
After you have updated everything that is needed, things should start working as they should be again.
However, this trick won’t work for all of you. If you are still not getting the desired results, it is time to move onto the next step.
2. Make Sure You Have Installed The Latest Version of Forge
Though the above fix will have worked for most of you, there are still some other things that can cause the problem that we need to rule out.
Another really common cause of the problem is that you may not be running the right version of Forge. Perhaps you accidentally missed an update somehow.
Given that pretty much every online Minecraft player will have Forge installed, it is important to keep on top of version changes on this front too.
Again, this will have worked for quite a lot of you, but not everyone. So, if you are still having problems, it is time to try our last fix.
This one up the ante a little, but it will give you a decent chance of getting back up and running again.
3. Remove All of Your Mods
Though this may seem like a bit of a crazy suggestion, it wouldn’t be here if it didn’t work.
At this point, if nothing else has worked, we can only attribute the problem to a broken mod that is causing absolute havoc.
This way, when it works again, you will know which mod was the cause of the problem in the first place.
Yes, we will admit that this can be a bit painstaking, especially if you are running quite a few mods, but it will help you get to the bottom of it.
The Bottom Line
Unfortunately, these are the only problems that we could find that actually worked.
However, we are always aware that there is a possibility that we may have missed something that seemed obvious to one of you reading this.
So, if you happen to be reading this and are a bit of an innovator in this regard, we would love to hear how you did it in the comments section below.
That way, we can pass on the word to our readers and save some headaches further down the line. Thanks!
2 thoughts on “3 Ways To Fix Failed To Synchronize Registry Data From Server In Minecraft”
MY MINECRAFT WONT WORK AND MINE RAFT IS MY FAVOURITE GAME IM 13amd I will still play it help me with my Minecraft it just wont load it stays on white I have been playing Minecraft for 6 years so help me
I tried the steps on this page but it still doesn’t work. The host computer is a PC while the one trying to join is a Mac. We have the latest versions (forge and optifine) and no mods installed but it still says failed to synchronize registry. I wonder why this could be, do you guys have any things else we could try? Thanks.
Leave a Comment Cancel reply
Minecraft
Subscribe To Email List
Free Latest Gaming News, Update & Tips!
Don’t Miss Out On Interesting Gaming Videos!
We won’t send you spam. Unsubscribe at any time.
Pages
Privacy Overview
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category «Analytics». |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category «Functional». |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category «Necessary». |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category «Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category «Performance». |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category «Performance». |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
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:
We are unable to convert the task to an issue at this time. Please try again.
The issue was successfully created but we are unable to update the comment at this time.
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 from server, closing connection #2847
Comments
Tunaey commented Sep 24, 2020
When I try to log into my 1.16.1 server it says «Failed to synchronize registry data, closing connection.» After removing Ice and Fire I can log back in again.
Also this is in the debug file:
[Render thread/ERROR] [net.minecraftforge.registries.GameData/REGISTRIES]: Unidentified mapping from registry minecraft:item
iceandfire:banner_pattern_ice: 1384
iceandfire:banner_pattern_bird: 1390
iceandfire:banner_pattern_ice_head: 1387
iceandfire:amphithere_skull: 1380
iceandfire:banner_pattern_amphithere: 1389
iceandfire:banner_pattern_fire: 1383
iceandfire:mountain_troll_leather_helmet: 1371
iceandfire:banner_pattern_hippogryph_head: 1396
iceandfire:banner_pattern_fire_head: 1386
iceandfire:banner_pattern_lightning: 1385
iceandfire:mountain_troll_leather_chestplate: 1372
iceandfire:troll_leather_mountain: 1370
iceandfire:banner_pattern_lightning_head: 1388
iceandfire:stymphalian_skull: 1378
iceandfire:hippogryph_skull: 1375
iceandfire:banner_pattern_mermaid: 1397
iceandfire:banner_pattern_hippocampus: 1395
iceandfire:mountain_troll_leather_boots: 1374
iceandfire:cockatrice_skull: 1377
iceandfire:mountain_troll_leather_leggings: 1373
[net.minecraftforge.fml.network.FMLHandshakeHandler/FMLHANDSHAKE]: Missing registry data for network connection:
minecraft:item: iceandfire:banner_pattern_hippocampus
minecraft:item: iceandfire:mountain_troll_leather_boots
minecraft:item: iceandfire:banner_pattern_mermaid
minecraft:item: iceandfire:cockatrice_skull
minecraft:item: iceandfire:mountain_troll_leather_leggings
minecraft:item: iceandfire:banner_pattern_lightning_head
minecraft:item: iceandfire:banner_pattern_fire_head
minecraft:item: iceandfire:troll_leather_mountain
minecraft:item: iceandfire:banner_pattern_hippogryph_head
minecraft:item: iceandfire:banner_pattern_bird
minecraft:item: iceandfire:banner_pattern_lightning
minecraft:item: iceandfire:mountain_troll_leather_helmet
minecraft:item: iceandfire:banner_pattern_amphithere
minecraft:item: iceandfire:amphithere_skull
minecraft:item: iceandfire:banner_pattern_fire
minecraft:item: iceandfire:banner_pattern_ice
minecraft:item: iceandfire:banner_pattern_ice_head
minecraft:item: iceandfire:hippogryph_skull
minecraft:item: iceandfire:mountain_troll_leather_chestplate
minecraft:item: iceandfire:stymphalian_skull
The text was updated successfully, but these errors were encountered: