Как исправить ошибку connection closed mismatched mod channel list

Java


  • Search


    • Search all Forums


    • Search this Forum


    • Search this Thread


  • Tools


    • Jump to Forum


  • #1

    Mar 4, 2021

    I made myself a server using forge, and so far we only have 5 mods in the server. my friend downloaded all 5 correctly, and for some reason it said this.

    Please do tell me whats wronge.


  • #3

    Mar 5, 2021

    im sorry but i have no clue what you just said


  • #4

    Mar 5, 2021


    TileEntity


    • View User Profile


    • View Posts


    • Send Message



    View TileEntity's Profile

    • Farlander
    • Join Date:

      9/20/2016
    • Posts:

      17,887
    • Location:

      Germany
    • Member Details

    Press Windows-Key + R

    Type:

    %appdata%/.minecraft/logs/

    Open the latest.log and copy all lines

    Paste it at paste.ubuntu.com — click on paste

    and add the link to it here

    space


  • #5

    Mar 5, 2021

    alright, i’m guessing this is what you wanted.

    not rlly sure what’s wrong. me and my friend have tried everything to get him into the server, so once you find the solution please tell me what was wrong.


  • #6

    Mar 5, 2021


    TileEntity


    • View User Profile


    • View Posts


    • Send Message



    View TileEntity's Profile

    • Farlander
    • Join Date:

      9/20/2016
    • Posts:

      17,887
    • Location:

      Germany
    • Member Details

    Add the log directly after that issue

    Is there a crash-report (crash-reports-folder) or a fml-client-latest.log (logs-folder)?

    If yes, add these, too

    space


  • #7

    Mar 5, 2021

    What do you mean by «add the log directly after that issue»?


  • #9

    Mar 5, 2021

    so apparently i was looking at the wrong thing and had to scroll all the way down and found a text file called «latest.log» if thats what you’re looking for.

    https://paste.ubuntu.com/p/RCSk5PJv7N/


  • #11

    Mar 5, 2021

    Remember that the issue isnt with me, but with my friend. he cant join the server even though he has every mod required, and my other friend in the server plays with DynamicSurroundings and he can play normally on the server, its just some other friend that has the issue. Not me


  • #13

    Mar 5, 2021

    i’ll do it as soon as he gets online.


  • #15

    Mar 6, 2021


    TileEntity


    • View User Profile


    • View Posts


    • Send Message



    View TileEntity's Profile

    • Farlander
    • Join Date:

      9/20/2016
    • Posts:

      17,887
    • Location:

      Germany
    • Member Details

    Looks like there are no mods loaded — does he have the mods in the right directory? Or does it work in Singleplayer?

    space


  • #16

    Mar 7, 2021

    we went into minecraft, he went to mods, clicked open mods folder and all of his mods were there. and it worked for him in singleplayer.


  • #19

    Mar 8, 2021


    TileEntity


    • View User Profile


    • View Posts


    • Send Message



    View TileEntity's Profile

    • Farlander
    • Join Date:

      9/20/2016
    • Posts:

      17,887
    • Location:

      Germany
    • Member Details
    [forge:split] rejected their server side version number during listping
    'forge:split' : Version test of 'ABSENT ?' from server : REJECTED

    I think he will need another Forge version
    He is using 1.16.5-forge-36.0.46

    space

  • To post a comment, please login.

Posts Quoted:

Reply

Clear All Quotes


When running or updating a modded Forge server, you can sometimes run into issues with mods or configs being different between the server and the client. While your server can sometimes automatically fix this issue, mainly in the case of configs being different, this can lead to players being unable to connect to the server. You can fix this issue by manually re-synchronising the mods and configurations on your server with the ones on your client, ensuring that they are the same.

  1. Stop your server. You can do this by clicking the Stop button at the top of the main panel page or at the top of your server’s console.
  2. As you will be deleting server files in order to update them, it is highly advisable to create a backup of your server prior to making any file edits. You can read our guide on how to do this here: How to Manually Backup Your Minecraft Server
  3. Connect to your server’s FTP. This can be done either using the web FTP accessible via the server panel, or by using an FTP client such as FileZilla. We suggest using an FTP client for this, as it makes uploading multiple files much easier (click here to read our FileZilla tutorial)
  4. Delete both the mods and config folders from your server. These are the two main folders that can lead to mods being mismatched; configs for mods also need to be synchronised for connections to be successful.
  5. Locate the modpack install folder for the modpack you are using. If you are using a modpack provided by an external launcher, you will be able to find the install folder according to this guide: How to Locate Your Minecraft Modpack Folder

    If you are using a self-made modpack that you installed manually, this will be in the .minecraft folder wherever you installed the game. This varies per operating system and install, but should look something like this depending on your platform:

    • Windows: %AppData%/.minecraft or C:/Users/(username)/AppData/Roaming/.minecraft
    • MacOS: ~/Library/Application Support/minecraft
    • Linux: ~/.minecraft
  6. After locating your modpack install folder, open it and upload both the mods and config folders.
  7. Once the uploads are complete, start your server! Your server should now be running with the same mods and configs as your client, and you should now be able to connect successfully.

It’s important to remember that some mods, such as OptiFine or any minimap mods, only work on the client and not the server. While Forge tries its best to disable these mods by detecting that they’re client-only, sometimes this doesn’t work and will result in your server crashing while loading. If this happens to be the case, simply remove any mods that are client-side only, or contact our support team for assistance! We’re always on hand to help you resolve server issues.

If you require any further assistance, please contact our support at: https://shockbyte.com/billing/submitticket.php

Comments

@MEathy

@MEathy
MEathy

changed the title
[Problem] Can’t join my server, «mismatched mod channel list»

[Problem] Can’t join my friend’s personal server «mismatched mod channel list»

May 17, 2022

@MEathy
MEathy

changed the title
[Problem] Can’t join my friend’s personal server «mismatched mod channel list»

[Problem] Can’t join my friend’s personal server. «mismatched mod channel list»

May 17, 2022

@MEathy
MEathy

changed the title
[Problem] Can’t join my friend’s personal server. «mismatched mod channel list»

[Problem] Can’t join my friend’s personal server. «mismatched mod channel list» [CLOSED CASE]

May 17, 2022

Connection closed — mismatched mod channel list

so, we started a Minecraft SMP and everyone is having no problems except one person. She keeps getting the error “ Connection closed — mismatched mod channel list “ . We’ve triple checked her mods and she has every one, and every correct version.

(She just installed a media fire link that everyone else did )

She has Minecraft forge 1.16.5 which is the client we’re using. No other mods are in her folder.

I’m not that tech-Savy so if someone could tell me what to do please help!

Archived post. New comments cannot be posted and votes cannot be cast.

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 .minecraftlogs.

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]

Возможно, вам также будет интересно:

  • Как исправить ошибку common dll
  • Как исправить ошибку api ms win crt convert l1 1 0 dll для windows 7
  • Как исправить ошибку api ms win core synch l1 2 0 dll для windows 7
  • Как исправить ошибку api ms win core localization l1 2 0 dll
  • Как исправить ошибку android process media

  • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии