|
| 1 | +--- |
| 2 | +title: Custom Anisette Server |
| 3 | +description: A guide on anisette servers. |
| 4 | +--- |
| 5 | + |
| 6 | +:::note |
| 7 | +Using any SideStore version after 0.4.0 is unlikely to lock your account as this is when support for v3 anisette servers was added. |
| 8 | + |
| 9 | +With this, it is **highly recommended** to use a v3 server for normal use of SideStore, if your version supports it. |
| 10 | +::: |
| 11 | + |
| 12 | +Anisette data is information used in the app signing process that needs to be generated each time you install or refresh apps. SideStore gets this information from a server that spoofs a Mac and sends you back the anisette data. No account info is sent to the server ever in this process. |
| 13 | + |
| 14 | +When many people use the same Anisette server (specifically a v1 server), it trips Apple's security, and locks the accounts that were using that machine. This is why we recommend using a separate burner Apple ID instead of your main one. |
| 15 | + |
| 16 | +Our team has worked on better approaches to avoid locked accounts (in the form of _anisette-v3_). However, if you are using an older version of SideStore, hosting your own anisette server is a great way to avoid locked accounts. This is made incredibly easy thanks to our current server being open source and made for docker environments. This means we can deploy a server with nothing more than the GitHub link. |
| 17 | + |
| 18 | +## Deploy on Render |
| 19 | + |
| 20 | +[Render](https://render.com/) is a service for easily creating servers. It supports loading server sources from GitHub. The free tier is quite limited in terms of resources, but the server can run comfortably on it without issue. |
| 21 | + |
| 22 | +Due to too many people using the same GitHub URL, you will have to fork the Git repository yourself. |
| 23 | + |
| 24 | +1. [Register](https://github.com/signup) for a GitHub account, if you do not already have one. |
| 25 | +2. [Open](https://github.com/Dadoum/anisette-v3-server) the Git repository. |
| 26 | +3. Click "Fork" in the top right, and fork the repository to your account. |
| 27 | +4. Once the forked repository is created, click the green "Code" dropdown in the top right, and copy the .git URL. |
| 28 | + |
| 29 | +* Save this for later. |
| 30 | + |
| 31 | +Once this is done, the Render server can be made. |
| 32 | + |
| 33 | +1. [Register](https://dashboard.render.com/register/) for an account. |
| 34 | +2. Create a [New Web Service](https://dashboard.render.com/select-repo?type=web). |
| 35 | +3. Scroll down to **Public Git repository** and enter the URL you copied earlier. |
| 36 | +4. Click "Continue" and fill in the form: |
| 37 | + * **Name** - Does not matter |
| 38 | + * **Region** - Closest to you |
| 39 | + * **Branch** - main (default) |
| 40 | + * **Root Directory** - blank (default) |
| 41 | + * **Environment** - Docker (default) |
| 42 | + * **Instance Type** - Free |
| 43 | + |
| 44 | +5. Wait for the server to build. You will see the following when it's done: |
| 45 | + |
| 46 | +``` |
| 47 | +Machine requires provisioning... done ! |
| 48 | +Your service is live 🎉 |
| 49 | +``` |
| 50 | + |
| 51 | +*If the build fails for any reason, click **Manual Deploy**, then **Deploy latest commit**.* |
| 52 | + |
| 53 | +6. Find the link for your new server at the top of the page: |
| 54 | + |
| 55 | +``` |
| 56 | +https://[your-server-name].onrender.com |
| 57 | +``` |
| 58 | + |
| 59 | +## Creating a custom anisette server list |
| 60 | + |
| 61 | +Since the release of version 0.5.8, SideStore uses an anisette server list system so officially endorsed anisette servers can be added more easily. This means that there is a little bit of extra work to be done in order to use your own server without requesting to have yours added to the official list. |
| 62 | + |
| 63 | +If you want to keep the option of using included servers, follow the steps below: |
| 64 | +1. Go [here](https://servers.sidestore.io/servers.json) to obtain the current server list. |
| 65 | +2. Head to a file hosting service of your choice to host the file on the internet. We recommend using GitHub Pages to do so as it's easier to edit in future, and will be the service used as example for this guide. If you have your own way of hosting, adapt the following to your setup. |
| 66 | +3. If you have a Github Pages site set up already, skip to the sixth sub-step. Otherwise, do the following: |
| 67 | +* Create a new GitHub repository via either the plus (+) button on the top right on desktop, profile icon > Create new on mobile, or [this page](https://github.com/new). |
| 68 | +* Set the name to be [your GitHub username].github.io, check 'Initialize this repository with a README', and set the remaining settings to how you wish. |
| 69 | +* Once created, go to the Settings tab and navigate to the Pages section under Code and automation. |
| 70 | +* Set Build and deployment under Source to 'Deploy from branch' |
| 71 | +* If not auto-selected, set Branch to 'main' |
| 72 | +* Return to the code tab and hit 'Add files', then 'Upload files', then select the 'servers.json' file you downloaded earlier. |
| 73 | +* Once uploaded, click on the file and hit the Edit button. |
| 74 | +* Scroll down to the last server on the list and add a comma after the last server's closing curly bracket ('}'), then add your own server afterwards in the following format: |
| 75 | +``` |
| 76 | +{ |
| 77 | + "name": "[something identifiable like a username]", //doesn't really matter unless you're sharing this server list with someone else |
| 78 | + "address": "[your server's url]" |
| 79 | +} |
| 80 | +``` |
| 81 | +* Commit the changes, then head to https://[your GitHub username].github.io/[where you placed the file]/servers.json. If the file loads, you are ready to move on to the next section. Otherwise, you may need to wait up to 10 mins for your site to be properly set up for use before you try again. |
| 82 | + |
| 83 | +If you want to only use your own server, follow the steps above, but instead of getting the official server.json, create your own using this formatting; |
| 84 | +``` |
| 85 | +{ |
| 86 | + "servers": [ |
| 87 | + { |
| 88 | + "name": "[as above]", |
| 89 | + "address": "[also as above]" |
| 90 | + } |
| 91 | + ] |
| 92 | +} |
| 93 | +``` |
| 94 | +and continue as normal. |
| 95 | + |
| 96 | +## Use your server with SideStore |
| 97 | + |
| 98 | +To use your newly created server list in the SideStore app, do the following: |
| 99 | + |
| 100 | +1. Open the Settings tab in SideStore. |
| 101 | +2. Scroll down to the bottom and tap on 'Anisette Servers'. |
| 102 | +3. Tap on the list URL and replace it with the URL of your server list. |
| 103 | +4. Hit 'Refresh Servers', and select your own server from the updated list. |
| 104 | + |
| 105 | +## Done! |
| 106 | + |
| 107 | +SideStore will now use your new custom anisette server. |
| 108 | + |
| 109 | + |
| 110 | +## Links: |
| 111 | +[<img src="https://uptime.sidestore.io/api/badge/4/uptime/48" />](https://uptime.sidestore.io/status/all) |
| 112 | +[All Official Anisette Servers Uptime](https://uptime.sidestore.io/status/all) |
| 113 | + |
| 114 | +[<img src="https://uptime.sidestore.io/api/badge/1/uptime/48" />](https://uptime.sidestore.io/status/ss) |
| 115 | +[Our Official Anisette Server's Uptime](https://uptime.sidestore.io/status/ss) |
0 commit comments