All Mods Resource Packs Data Packs Shaders Modpacks Plugins
e4mc Retro
Projects / Mods

e4mc Retro

by xhyrom • Downloads: 0 • Followers: 0
Install / Download
Description
Gallery
Changelog
Versions

e4mc thumbnail

e4mc Retro is a backport of e4mc mod, allowing you to open your Minecraft LAN world to anyone over the internet — even on older Minecraft versions.

What is e4mc?

e4mc is a reverse tunneling reverse proxy for Minecraft. In simpler terms, it's a software that allows you to temporarily expose a local Minecraft server to the internet.

How do I use it?

Simply install the mod, and Open to LAN as normal. A public domain will appear alongside the local port. Others can simply connect to the public domain to connect to your LAN server.

All Versions

+ Add Version
Name Game version Platforms Published Downloads Actions
1.12.x 1.11.x 1.10.x +1
Ornithe
17h ago 1
1.12.x 1.11.x 1.10.x +1
Forge
17h ago 1
1.12.x 1.11.x 1.10.x +1
Fabric Legacy-fabric
17h ago 1
1.6.4
Ornithe
17h ago 1
1.6.4
Legacy-fabric
17h ago 1
1.6.4
Forge
17h ago 1
1.12.x 1.11.x 1.10.x +1
Fabric Legacy-fabric
17h ago 1
1.12.x 1.11.x 1.10.x +1
Ornithe
17h ago 1
1.12.x 1.11.x 1.10.x +1
Forge
17h ago 1
1.6.4
Ornithe
17h ago 1
1.6.4
Forge
17h ago 1
1.6.4
Legacy-fabric
17h ago 1
1.16.x
Fabric
17h ago 1
1.16.x
Forge
17h ago 1
1.16.x
Quilt
17h ago 1
1.15.x
Fabric
17h ago 1
1.15.x
Quilt
17h ago 1
1.15.x
Forge
17h ago 1
1.14.x
Fabric
17h ago 1
1.14.x
Quilt
17h ago 1
1.14.x
Ornithe
17h ago 1
1.14.x
Forge
17h ago 1
1.13.x
Ornithe
17h ago 1
1.13.x
Rift
17h ago 1
1.13.x
Fabric Legacy-fabric
17h ago 1
1.13.x
Forge
17h ago 1
1.8.x
Ornithe
17h ago 1
1.8.x
Fabric Legacy-fabric
17h ago 1
1.8.x
Forge
17h ago 1
1.7.x
Ornithe
17h ago 1
1.7.x
Forge
17h ago 1
1.7.x
Fabric Legacy-fabric
17h ago 1
1.12.x 1.11.x 1.10.x +1
Ornithe
17h ago 1
1.12.x 1.11.x 1.10.x +1
Fabric Legacy-fabric
17h ago 1
1.12.x 1.11.x 1.10.x +1
Forge
17h ago 1
1.16.x
Forge
17h ago 1
1.16.x
Fabric
17h ago 1
1.16.x
Quilt
17h ago 1
1.14.x
Forge
17h ago 1
1.15.x
Forge
17h ago 1
1.15.x
Fabric
17h ago 1
1.15.x
Quilt
17h ago 1
1.14.x
Quilt
17h ago 1
1.14.x
Fabric
17h ago 1
1.14.x
Ornithe
17h ago 1
1.13.x
Forge
17h ago 1
1.13.x
Ornithe
17h ago 1
1.13.x
Rift
17h ago 1
1.13.x
Fabric Legacy-fabric
17h ago 1
1.8.x
Ornithe
17h ago 1
1.8.x
Forge
17h ago 1
1.8.x
Fabric Legacy-fabric
17h ago 1
1.7.x
Ornithe
17h ago 1
1.7.x
Forge
17h ago 1
1.7.x
Fabric Legacy-fabric
17h ago 1
1.12.x 1.11.x 1.10.x +1
Ornithe
17h ago 1
1.12.x 1.11.x 1.10.x +1
Fabric Legacy-fabric
17h ago 1
1.12.x 1.11.x 1.10.x +1
Forge
17h ago 1
1.12.2
Ornithe
17h ago 1
1.12.2
Fabric Legacy-fabric
17h ago 1
1.12.2
Forge
17h ago 1
🖼️

No gallery images uploaded.

## 1.1.0

  • Added** new backend implementation for connections using cloudflared.
## 1.1.0

  • Added** new backend implementation for connections using cloudflared.
## 1.1.0

  • Added** new backend implementation for connections using cloudflared.
## 1.1.0

  • Added** new backend implementation for connections using cloudflared.
## 1.1.0

  • Added** new backend implementation for connections using cloudflared.
## 1.1.0

  • Added** new backend implementation for connections using cloudflared.
## 1.0.3

  • Fixed** translations for versions <=1.10.2 where the language files were not properly loaded.
## 1.0.3

  • Fixed** translations for versions <=1.10.2 where the language files were not properly loaded.
## 1.0.3

  • Fixed** translations for versions <=1.10.2 where the language files were not properly loaded.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.
## 1.0.2

  • Added** a new configuration option: useInsecureTLS
This allows disabling TLS certificate validation for relay connections.
⚠️ **Warning:** This is insecure and not recommended. It is strongly advised to install the Azul Zulu 8 JDK or manually import the relay certificate instead.
See [this comment](https://github.com/xhyrom/e4mc-retro/issues/2#issuecomment-3102506009) for detailed instructions and rationale.
  • Improved TLS handling** for broker HTTP connections:
  • If useInsecureTLS is enabled, the client uses an insecure trust manager that disables certificate validation.
  • If disabled (default), the client first attempts to use the system-default TLS validation. If that fails, it falls back to a bundled custom trust manager using /certs/broker.e4mc.link.cert.

🌟 Related Projects

Similar modifications and resources you might like

View all →
Skin Restorer
S

Skin Restorer

by Lionarius

A server-side mod for managing and restoring player skins.

0
mod
AutoModpack
A

AutoModpack

by Skidam

Enjoy a seamless modpack installation process and effortless updates with a user-friendly solution that simplifies management, making your gaming experience a breeze.

0
mod
First Join Message
F

First Join Message

by Serilum

💬 Sends players who join a world for the first time a configurable message.

0
mod
e4all
e

e4all

by JustPixel

The e4mc fork that lets anyone join your LAN world from anywhere, even with offline accounts. Supports Simple Voice Chat, Android, and more!

0
mod
e4mc Retro Icon
Download e4mc Retro
Select game version
Select platform