Current Common Issues (Updated: November 30th 2018)

Discussion in 'Minecraft Community Support' started by Richard_BN, Nov 25, 2018.

Thread Status:
Not open for further replies.
  1. Richard_BN

    Richard_BN
    BeastNode Staff

    Joined:
    Dec 18, 2015
    Messages:
    512
    Likes Received:
    130
    Trophy Points:
    108
    Gender:
    Male
    Occupation:
    BeastNode Support Agent
    Location:
    The Realm of Obscurity.
    These are just some of the common issues that I am seeing a lot on the tickets currently.



    ----Minecraft 1.13-1.13.2 Specific Common Issues----

    ------------------------------
    When purchasing a new server and switching to anything except for 1.13-1.13.2 (especially when switching to a modpack) - make sure to generate a new world!
    ------------------------------
    As the world generation/data format has been changed considerably in the 1.13 update, a 1.13+ world cannot be used on an older MC version - it will cause issues, if it is able to load up at all without crashing on world load.
    When starting your server up on 1.12.2 or older, or on a modpack, after purchasing a new server please make sure to have either deleted the world in the files or to enter a new world name in the World box on the control panel and save changes before restarting the server on the new option.
    ------------------------------

    ------------------------------
    Minecraft 1.13/1.13.1 is full of bugs and general issues, and has a number of performance issues. 1.13.2 fixes a number of these but it is still not the best performance wise.
    ------------------------------
    Currently performance will be worse on a 1.13+ installation compared to other non-modded server setups (even a completely new Vanilla 1.13.2 installation compared to an old/in use Vanilla 1.12.2 installation).
    Note that this is not (entirely) due to an increase of RAM usage in 1.13, it is just generally slower overall so having a higher package will not help with this. However - it does have a slightly higher RAM usage than 1.12.2 and older, so the 512MB/1GB plans may not be enough for 1.13+.

    Suggestions that may help:
    Using a world generated on 1.13+ may help (as noted in the next common issue, older worlds may cause problems), or try reducing server settings - in particular the serverside view-distance in the server.properties so that less chunks are being loaded in around each player on the server.

    Using Spigot 1.13.2 over Vanilla 1.13.2 may also help as it has a number of performance tweaks/patches that Vanilla lacks - you do not need to be using plugins to use Spigot. Note that if you do switch and have already been to the End/Nether on Vanilla that they may reset as Spigot loads them from a different location in the files.
    ------------------------------

    ------------------------------
    As above, 1.13+ is still not 'stable' and the most common cause of issues on 1.13+ servers being reported currently is due to using a 1.12.2 or older world.
    ------------------------------
    While a 1.13+ server will try and update chunks to the new 1.13 world format as you explore it is not guaranteed to work and even if a 1.12.2 or older world appears to be okay at first this does not mean that it is (just that the chunks you have loaded in on 1.13 up to that point are okay) and it can still cause issues at a later time simply due to not being a 1.13 world. For example as you explore the world the chunks will be updating to the new 1.13 chunk format so the CPU usage will be much higher, even in chunks that you already generated in 1.12.2 or older.

    If you do wish to update to 1.13+ and keep using your current worlds etc.. then please make sure to create a full backup of your server data before updating to 1.13+ so you can go back to 1.12.2 and restore the backup if necessary (in general this should be a general rule of thumb for any major MC update with the same worlds being used).
    Please also note that if you are using CraftBukkit/Spigot 1.12.2 and older then you should be updating to 1.13+ with CraftBukkit/Spigot - not Vanilla.

    Suggestions that may help:
    Unfortunately none, besides reducing the view-distance in the server.properties so less chunks are processing these updates at the same time.
    It is also strongly advised not to use 1.13/1.13.1 any longer - if you are planning on updating at this point use 1.13.2 .
    If you are waiting on specific plugins to update for/be usable on 1.13.2 then it would be advised to either stay on your current version till they have updated for 1.13.2, or update without those plugins and add them back later. Updating to 1.13.1 (for the few plugins that will work on 1.13/1.13.1 but not 1.13.2 yet) so you can update the server to 1.13+ sooner is not advised at this point.
    ------------------------------

    ------------------------------
    X plugin no longer works or similar...
    ------------------------------
    1.13.2 is still a new release (in the grand scheme of things) - a lot of plugins will not be 1.13.2 compatible without updates to make it so.

    As stated above - If you are waiting on specific plugins to update for/be usable on 1.13.2 then it would be advised to either stay on your current version till they have updated for 1.13.2, or update without those plugins and add them back later. Updating to 1.13.1 (for the few plugins that will work on 1.13/1.13.1 but not 1.13.2 yet) so you can update the server to 1.13+ sooner is not advised at this point.

    If you do update make sure to check for plugin updates regularly (development builds included), as well as update the server jar regularly to keep up to date with bug fixes etc...

    Suggestions that may help:
    If you are running a 1.12.2 or older bukkit server and wish to update it is generally advised to download a copy of your plugins and configs (and worlds if you are trying to keep them on update as well) and test them on a 1.13.2 Spigot/CraftBukkit localhost to see what does or does not work before updating your public server.
    All plugins should be updated as new releases come out for them (including development builds) to make sure they are 1.13.2 compatible and have minimal bugs.
    ------------------------------




    ----General Common Issues/Queries----

    ------------------------------
    New Server - Cannot connect or Server has a whitelist on connection when it has not been enabled on your server
    ------------------------------
    Please make sure that you are using the full IP:Port if you did not purchase a Dedicated IP addon. Without this addon the port must be included - ie instead of 123.45.67.890 you would be using 123.45.67.890:25585 or similar.
    If your Port is not listed as 25565 on the control panel (or in the Minecraft Server Information email you are sent on purchase of your server) then the port listed must be included or you will be connecting to a different server.

    If the IP:Port is correct, or you have a Dedicated IP or subdomain and still cannot connect - please make sure your launcher is running the same Minecraft version that the server is running (by default all servers are Vanilla 1.13.2 unless you have changed this via the control panel).
    If you have installed any mods/modpacks you need to have the same mods/modpack running on your end to connect (ie if you install TekkitClassic on the server then you need to use the TechnicLauncher set to the same version of TekkitClassic to connect - not your normal MC launcher).
    ------------------------------

    ------------------------------
    Please do not increase the view-distance setting in the server.properties, or the randomTickSpeed gamerule unless you know what you are doing/require it!
    ------------------------------
    Something that we get somewhat often are reports of high CPU or lag issues that shouldn't be there, and on checking it is due to these settings having been increased.
    In general on a shared hosting setup these options should never be increased - both will increase the CPU usage considerably.
    Increasing the view-distance setting increases how many chunks around each player the server is actively loading in and each of those chunks is then actively running processes such as plant growth and mob spawns etc.. Even increasing it just from 10 to 12 can have a large impact on the CPU usage.
    The same applies to the randomTickSpeed gamerule - increasing this makes the servers random block ticks occur more frequently. While this will result in faster leaf decay and plant growth etc... it will also increase the server load as a result (particularly when setting it to a high number - when we have seen it increased and causing issues it's usually due to having been set to 100+, when even increasing it to 10 would cause issues).
    In general - unless you specifically require this for something you are doing on the server, it is strongly recommended to never increase these settings on a shared hosting server (on a VPS/Dedicated Server it may be fine depending on what you set up on it/how high you increase the settings).
    If anything - particularly on 1.13+ and for newer modpacks that have chunk generation cascade lag issues - it is generally recommended to lower the view-distance to help with the server load.
    ------------------------------

    ------------------------------
    Please do not use Cracked plugins!
    ------------------------------
    It is surprisingly common how often we have reports of issues on servers that are caused by cracked plugins being used.
    Whether the plugin is one of the more expensive Premium resources or not, it should be paid for if you wish to use it and they do not provide a free download themselves (such as mcMMO which, while it is a Premium resource, they do link to their development builds which are free and work mostly as well as the full paid-for releases). Otherwise you should be finding a free alternative, or simply not using it at all.
    Using a cracked plugin opens your server up to a lot of potential issues, as there is a very good chance that they have been tampered with. They are also commonly outdated anyway and won't work properly as a result even if they have not been tampered with.
    The issues we commonly get reported due to cracked plugins are that the server is crashing/stopping on startup - removing the cracked plugin resolves this - but there have been issues reported as severe as all server data being deleted/corrupted when the cracked plugin is loaded up, which is not reversible unless you have a recent full backup of your server data.
    **Suggestions that may help**: Don't use them - simple as. There are usually either free alternatives, or free development builds available for those plugins, if you specifically require those features on your server - but it is never worth the risk to use a cracked plugin, it would be much wiser and safer to simply not have that feature on your server at all, or at least until you can purchase the plugin at a later date.
    ------------------------------
    On a side note of this ^^ This also applies to buying pre-made server setups. Make sure they are not using cracked plugins **before** you purchase the setup.
    ------------------------------




    ----Known issues host-end----

    ------------------------------
    No we will not be adding 1.8 back to the jarlist.
    ------------------------------
    It is 3-4 years old now and is heavily outdated - it cannot be supported forever and in general there is no real reason why you can't update the server (maybe not to 1.13.2 currently... but at least up to 1.12.2). We did post a lot of warnings on the jar list update posts during the 1.13 snapshot/pre-releases that it would be removed once 1.13's full release came out.
    Regardless, you can run 1.8 as a custom server jar if you wish - You are never limited to what is available on our jar list. We will just no longer provide the jar on our end or support it in general.
    - https://www.beastnode.com/portal/index.php?rp=/knowledgebase/72/How-To-Upload-a-Custom-JAR-File.html
    ------------------------------

    ------------------------------
    For anybody wondering if we are going to be adding the new official Bedrock server to our list - No.
    ------------------------------
    It does not run off of Java at all (as NukkitX does and as MultiCraft is designed to use) so it's unlikely to ever be usable with our setup/with MultiCraft at all.
    As it is also only an Alpha release currently - NukkitX is still going to be more stable/usable.
    ------------------------------

    ------------------------------
    We are aware that the plugin installer sometimes fails to install plugins from the SpigotMC resources. However, as it appears to be an API compatibility issue with the installer itself it is unlikely that we will be able to fix it from our end unless the developers of the installer itself resolve the issue (we do not develop or maintain the installer it is a 3rd party addon, and should not be depended on in general).
    For the time being any plugins from SpigotMC when the installer is not working correctly will need to be installed manually by uploading the plugin .jar files to the servers jar directory via the FTP (in general manual installation is advised over depending on the installer regardless of whether it is working correctly or not).
    --------------------
     
Thread Status:
Not open for further replies.

Share This Page