VIAaaS/README.md at b1e742e2a1847b8d54b4481953baaab3b3299baa

mirror of https://github.com/ViaVersion/VIAaaS.git synced 2024-09-16 02:56:43 +02:00

creeper123123321 420ae111d7

2021-02-09 11:09:15 -03:00

VIAaaS

VIAaaS - ViaVersion ~~acetylsalicylic acid~~ as a Service - Standalone ViaVersion proxy

How to use: server.example.com._p25565._v1_12_2._ofalse._uBACKUSERNAME.viaaas.example.com (similar to tor to web proxies)

Parts:

server.example.com: backend server address
_p: backend port
_v: backend version (protocol id https://wiki.vg/Protocol_version_numbers or name with underline instead of dots)
_o: true to force online mode in frontend, false to disable online mode in frontend. if not set, it will be based on backend online mode.
_u: username to use in backend connection
viaaas.example.com: hostname suffix (defined in config)

Default Minecraft: viaaas.localhost with port 25565

Default WS URL: wss://localhost:25543/ws

VIAaaS auth page is designed for storing accounts in the player's browser local storage. It requires a CORS Proxy for calling Mojang APIs, which may make Mojang see that as suspicious and reset/block your account password if the IP address is suspect.
There are some information about Mojang password resetting: https://github.com/GeyserMC/Geyser/wiki/Common-Issues#mojang-resetting-account-credentials and https://mobile.twitter.com/MojangSupport/status/863697596350517248
VIAaaS may have security vulnerabilities, make sure to block the ports in firewall and take care of browser local storage.

Requires Java 11

How to start VIAaaS server:

Usage for offline mode:

Usage for online mode:

You can use two accounts (avoids Bad Login error), the same account for front-end and back-end connections or use _ofalse (offline mode in frontend, not encrypted).
You should set up a CORS Proxy (something like https://www.npmjs.com/package/cors-anywhere, git clone https://github.com/Rob--W/cors-anywhere && cd cors-anywhere && npm install && node server.js) on the machine you are using the VIAaaS authenticator webpage. You can use my CORS Anywhere instance https://crp123-cors.herokuapp.com/ when using https://viaversion.github.io/VIAaaS/ but Mojang may look it as suspect.
Go to VIAaaS auth webpage (https://localhost:25543/), configure the CORS Proxy URL (something like http://localhost:8080/, note the ending slash) and listen to the username A that you're using to connect to the proxy.
Add the account B you'll use in _u parameter to browser auth page.
Connect to mc.example.com._v1_8._u(account B).viaaas.localhost (_u(account B) parameter can be removed if you are using the same account)
Approve the login in auth webpage
Minecraft client will give Bad Login after you approve the login in your browser if you are using the same account. You can use https://www.curseforge.com/minecraft/mc-mods/auth-me for reauthenticate the client.

VIAaaS may trigger anti-cheats, due to block, item, movement and other differences between versions. USE AT OWN RISK

VIAaaS is stuck when connecting with online mode: