
e4mc Retro
Open a LAN server to anyone, anywhere, anytime even on older Minecraft versions.
152.4K
47
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:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1.0.2
- Added a new configuration option:
useInsecureTLSThis 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 for detailed instructions and rationale. - Improved TLS handling for broker HTTP connections:
- If
useInsecureTLSis 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.
- If
- Added a new configuration option:
1
...