Upgrading from 2.0-beta.1 to 2.0-beta.2 – Apantic

Read the changelog: https://www.apantic.com/products/minesync.10/changelog

Estimated Upgrade Time: Less than 30 minutes

Vault Dependency Removed

If you had Vault installed without a permissions plugin in v2.0-beta.1 (because Vault and a permissions plugin were required prior to v2.0-beta.2) you can remove Vault and the permissions plugin (if you do not otherwise use them).

Update Configuration File

The configuration file has been changed in v2.0-beta.2. You will need to transfer your edits over manually. Replace your configuration file on your server, in /plugins/MineSync2/config.yml with: https://gist.githubusercontent.com/LordRobust/37984e271c4951e76099b12d24cbc021/raw/dc0db831456749eccf1bc82e04d726f1a0103f32/config.yml

You will need to carry over your previous edits. Edit the new config file to carry over any custom changes you made to your previous config.

You may notice some variables are not in the new config that were in the previous config. These variables are no longer used and should not be carried over.

Set API Key

Communications between the server and XenForo forum are authenticated in two ways:

Using an API key
Using IP whitelisting

Setting an API key

To set an API key, go to your admin panel in XenForo, then Options -> [A] MineSync -> API key

Put a long, random string into here. We recommend you make it at least 32 characters long. We recommend you use a mixture of letters (upper and lower case). You can generate a long string at: https://strongpasswordgenerator.com/

Setting up an IP whitelist

You can also whitelist IPs that are allowed to use your API. We highly recommend you do this step, but it is not necessary. If you leave this blank, the add-on will function as normal, but the add-on will throw warnings into your error log recommending you fill in your IPs.

Add in any IPs (typically your servers' IP addresses) into this box. This should be the numerical IP address of your server. Separate IPs using a comma. For example:

127.0.0.1,192.168.10.1

By using the above example, only 127.0.0.1 and 192.168.10.1 will be allowed to access the API.

If you have any questions or problems, please open a support ticket.