Posts by Roman

Take a screenshot of the connection details entered in your server list

Please try generating a new world.

Create a backup beforehand

You probably don't have the same collection of mods installed on your computer as on the server.

You could try to download the world and delete unused chunks using a 3rd party tool like MCA selector

On which version did you use the world when you downloaded it?

Which version are you using now?

Please follow the instructions of this article: https://support.aternos.org/hc…ut-your-server-connection

Make sure you have the same collection of mods installed on your computer as on the server, if that's the case try deleting the config folder on your computer and on the server.

Remove the mods one by one from your server.

Every time you remove a mod from your server, you need to restart it, then check if the problem still occurs.

If the problem doesn't occur anymore, know that it was probably due to the modification you last removed.

Quote from jose_jojo

mobile data it throws an error

Which error?

We can't really help you if the issue is caused by mods.

You can try removing them one by one to find out which mod causes this

Do you get the same error message with the DynIP?

Any messages in the console of the server when you try to join it?

You probably have to enable it for the specific world in the Multiverse settings

You can just create that folder on your own if it's missing: https://aternos.org/files/world

1. Share your client log
2. Share a screenshot of the mods folder on your computer
3. Share a screenshot of the mods folder on the server

fixed: https://aternos.org/addons/a/curseforge/mutil

Try removing mod by mod

In addition, you can't play on a Fabric with mods via Geyser...

That message typically occurs when the mod collection on the players computer is not the same as on the server.

You may want to report a bug report at Mojang as this is not really related to Aternos, but to the Minecraft server software.

Unfortunately, you can't access that file on Aternos and there are currently no plans to change that behavior.

Tbh. The plugin should not create its own log file, it should log into the main log as every other plugin does.