Jump to content
Please read the rules and FAQ before starting a new topic
Currently supported: All versions

[1.16.1] Failed to synchronize registry data from server.

HadronHarve

By HadronHarve
in Support & Bug Reports

 Share

Recommended Posts

HadronHarve Tree Puncher

HadronHarve

Posted
Posted (edited)

I made modpack and server by editing another.

Everything is fine when I connect to the server using the local network.


But when my friend connects to my server using an external IP, he has this error:

unknown.png?width=960&height=600

Client log: 

[12:38:13] [Render thread/INFO]: Connecting to 82.193.116.197, 25565
[12:38:15] [Render thread/INFO]: Injecting existing registry data into this CLIENT instance
[12:38:15] [Render thread/INFO]: Registry TileEntityType: Found a missing id from the world quark:matrix_enchanting
[12:38:15] [Render thread/INFO]: Registry ContainerType: Found a missing id from the world quark:matrix_enchanting
[12:38:15] [Render thread/ERROR]: Unidentified mapping from registry minecraft:block_entity_type
    quark:matrix_enchanting: 70

[12:38:15] [Render thread/ERROR]: Unidentified mapping from registry minecraft:menu
    quark:matrix_enchanting: 33

[12:38:15] [Render thread/ERROR]: Missing registry data for network connection:
    minecraft:menu: quark:matrix_enchanting
    minecraft:block_entity_type: quark:matrix_enchanting

[12:38:15] [Netty Client IO #2/ERROR]: Failed to load registry, closing connection.
[12:38:15] [Netty Client IO #2/ERROR]: Connection closed, not continuing handshake

Server log: 

[12:38:15.319] [User Authenticator #3/INFO] [net.minecraft.network.login.ServerLoginNetHandler/]: UUID of player AngelHalfDaemon is 5eeabda8-e8c0-4afa-9f5e-4c02d058f76f
[12:38:16.466] [Server thread/INFO] [net.minecraft.network.login.ServerLoginNetHandler/]: com.mojang.authlib.GameProfile@11644c47[id=5eeabda8-e8c0-4afa-9f5e-4c02d058f76f,name=AngelHalfDaemon,properties={textures=[com.mojang.authlib.properties.Property@46072232]},legacy=false] (/82.193.122.171:49789) lost connection: Disconnected

 

What we do:

  • Reinstall server and client;
  • Recreate server and client;
  • Delete quark config from client and server to regenerate it.


Nothing has changed, but when we remove the quark, then there will be no error.

I would like to return the quark so I need your help.

if It needs, I can upload the modpack and server.

Edited by HadronHarve
HadronHarve Tree Puncher

HadronHarve

Posted
  • Author
Posted
9 minutes ago, diesieben07 said:

This looks like the client does not have the same version of Quark or it is wrongly configured.

I check versions of client`s and server`s mods using total commander, so version are same.
Also, I export and install modpack via twitch.

HadronHarve Tree Puncher

HadronHarve

Posted
  • Author
Posted
7 minutes ago, diesieben07 said:
  1. That file is not available.
  2. That file is called debug-1.log. You need to post debug.log. Not any other file.
  3. You need to post both server and client log. That means you need to post two files.

The name is debug-1.log because the last log was started after deleting the config. My files are queued.

HadronHarve Tree Puncher

HadronHarve

Posted
  • Author
Posted
3 minutes ago, diesieben07 said:

Both of those are archived latest.log, not debug.log.

And your log is not really helpful, since you can connect fine.

 

Please respond once you have obtained the necessary log files from your friend.

 

 

OPS, I edited my post with debug.

HadronHarve Tree Puncher

HadronHarve

Posted
  • Author
Posted (edited)
24 minutes ago, diesieben07 said:

Now I have the server debug log (which I already had before).

I still do not have your friend's client debug.log.

 

 

Ok, i will upload soon as i can.

Edited by HadronHarve
  • 5 weeks later...
DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted
10 minutes ago, lspacebarl said:

Hi, i am having an identical issue with a server I am renting. Did you ever find a solution?

Please make your own thread

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept