AE2 Web Integration

AE2 Web Integration

Get started

Install the server mod, set up access to your ME network and open the terminal in your browser.

1. Choose a download

Download AE2 Web Integration from Modrinth, CurseForge or GitHub Releases. Select the file for your server's exact Minecraft version and mod loader.

  • Minecraft 1.21.1: NeoForge, with AE2.
  • Minecraft 1.20.1: Forge, with AE2.
  • Minecraft 1.12.2: Forge, with AE2 Unofficial Extended Life (AE2 UEL).
  • Minecraft 1.7.10: Forge, with the GT New Horizons fork of AE2.

Keep the AE2 version and dependencies required by your chosen download. Builds for different Minecraft versions or loaders are not interchangeable. The older builds support the matching AE2 Fluid Crafting forks used by AE2 UEL and GTNH.

2. Install the server mod

  1. Stop your Minecraft server.
  2. Put the downloaded server mod JAR in the server's mods/ folder.
  3. Start the server once to generate config/ae2webintegration/config.toml.

On multiplayer, install AE2 Web Integration on the server. Players use their browser to access it. The mod adds no blocks or items. It also works in a single-player instance; use that instance's mods/ and config/ folders.

The separate icon-generator JAR belongs in the Minecraft client used to export optional item icons.

3. Configure access

Open config/ae2webintegration/config.toml in your server directory. These entries are in its [general] section:

port
The web server's TCP port. The default is 2324.
password
The password for the Admin web account. A password is generated for a new configuration. Keep it or replace it with your own secret password.
public_mode
Defaults to true, allowing individual player accounts. Set it to false for a private setup where only the Admin account should be available.
allow_no_password_on_localhost
Defaults to true. Connections from 127.0.0.1 or another loopback address receive admin access without a login. Set it to false to require a login there too.
trusted_proxies
Empty by default. For a reverse proxy on another machine, enter its literal IP address or CIDR range; separate several entries with commas. A proxy on the server's own machine is trusted automatically. Only list proxies you control, because their forwarded client address also affects localhost admin access.

Save the file, then restart the server or run this command as a server operator with permission level 4: 

/ae2webintegration reload

The command reloads the configuration and restarts the built-in web server.

4. Connect a browser

With the default port, open this address using your server's IP address or domain:

http://your-server-address:2324/

On the computer running the server, you can use http://127.0.0.1:2324/. On another device, use the Minecraft server computer's address. Replace 2324 if you changed general.port.

Allow that TCP port through the server firewall. To connect from outside your local network, also forward the port on your router when your server is behind NAT. This is a separate web port from the Minecraft game port.

Using an HTTPS reverse proxy

Point the proxy at the mod's HTTP address. Preserve the public Host header, including any nonstandard port, and set X-Forwarded-Proto to the public http or https protocol. The proxy must overwrite that header with the verified protocol. Forward the client address with X-Forwarded-For or X-Real-IP.

Forwarded headers are accepted only from a local proxy or one listed in general.trusted_proxies. If both address headers are present, X-Forwarded-For takes priority. Use the proxy's public address in your browser.

5. Sign in or register

Admin access

Log in as Admin with the password from general.password. Admin can access every available network on the server, so share this account only with people who should have that access. With public mode disabled, this is the account to use.

Individual accounts in public mode

  1. Join the Minecraft server and stay online while registering.
  2. Choose registration on the web login page. Enter your Minecraft player name and a web password.
  3. Copy the confirmation command shown by the page and run it in Minecraft chat as that player.
  4. After the game confirms registration, return to the web page and log in with those credentials. 
/ae2webintegration auth <token>

Use the complete token supplied by your web page. Registration links the web account to your Minecraft player; access to a network is set up in game as described below.

6. Give your player network access

Keep the ME network loaded and online, and let it finish starting. For a straightforward player setup, place your own Wireless Access Point on the network. Each player who needs web access can place their own.

Minecraft 1.20.1 and 1.21.1

Web access follows the in-game owner of an ME Controller, Wireless Access Point or terminal part connected to the network. A supported part placed by your player grants that player access. This also includes Pattern Access Terminals.

Minecraft 1.7.10 and 1.12.2

Ownership of a connected ME Controller, Wireless Access Point or terminal part grants access here too. A working Security Terminal offers another route: add the player's biometric card with Build, Extract, Inject and Craft permissions all enabled. Unassigned or wild biometric cards grant no web access.

Admin access covers all available networks and does not need a separate per-player access source. Player accounts show only the networks their Minecraft identity can access.

7. Open the terminal

  1. Open the web panel and sign in.
  2. On Home, select Choose a network.
  3. Select a network to open its resources. Use the network chooser to switch between networks.

The terminal works with item names immediately. To add artwork from your modpack and resource packs, follow the icon export guide.

If something is missing

The page does not open

Confirm that the Minecraft server is running and the mod loaded without an error in the server log. Check the configured web port and try the local address on the server computer. If that works, check the address, firewall, router forwarding or reverse proxy used by the other device.

Registration fails

Check that public mode is enabled and that the named player is online. Start registration on the web page, then run its exact confirmation command from that player's game chat. If the server or web server restarted during registration, begin again on the login page.

No accessible networks

Check that the network is loaded, online and finished starting, then refresh the panel. For a player account, check the owner of the connected access block or terminal. On older versions, also check that a Security Terminal used for access is working and that the player's card has all four required permissions.

The terminal shows names without icons

Icons are optional. Export and install an icon pack, then choose an icon display mode in the panel's Web settings.