* Initial setup page * Cleanup new setup page * Space out options * Fix host providers with templates * Cleanup host provider classes * Fix spacing to make it all look more uniform * Always show setup options and add provider infomation inside an alert * Drop side margin * Add collapsable sidebar * Add build_in host on provider selector (#166) * add buildin host provider support * concat js loop * Cleanup indent for cleaner commit * Move all_providers --------- Co-authored-by: rtm516 <rtm516@users.noreply.github.com> * start on proper setup instructions * Add self-hosting info * Add not listed and fix some other minor issues * - Floodgate setup/FAQ page - Add version warnings/info in FAQ - Merging upstream/master - Replace old setup page with new one; minus videos * Show Self-Host vs Hosting Provider pages * Move to tabs, add icons and structure cleanup * Less repetition, wording * Updated Standalone setup instructions * Show "Not listed" provider option at the top of the hosting provider list --------- Co-authored-by: JensC <jenscollaertyprive@hotmail.com> Co-authored-by: Jens Co <63231928+Jens-Co@users.noreply.github.com> Co-authored-by: onebeastchris <github@onechris.mozmail.com>
39 lines
2.2 KiB
Markdown
39 lines
2.2 KiB
Markdown
|
|
# Proxy setup with server hosting provider
|
|
|
|
<div class="alert alert-info" role="alert">
|
|
NOTE: <br>
|
|
- Install Geyser <b>only</b> on the proxy server! You can install Floodgate on all servers for better skin support &
|
|
network-wide Floodgate API availability for other plugins. <br>
|
|
- All servers on the network must accept {{ site.data.versions.java }} Java clients, as Geyser imitates one.
|
|
</div>
|
|
|
|
1. Select your server hosting provider in the dropdown above.
|
|
2. Download the plugin for your proxy software from [the download page](https://geysermc.org/download).
|
|
3. Place the Geyser jar in the `plugins` folder, and restart the server.
|
|
4. Open your Geyser config, located in `/plugins/Geyser-xyz/config.yml`, and find the following:
|
|
|
|
```yaml
|
|
bedrock:
|
|
# The IP address that will listen for connections.
|
|
# Generally, you should only uncomment and change this if you want to limit what IPs can connect to your server.
|
|
#address: 0.0.0.0
|
|
|
|
# The port that will listen for connections. This is the port that Bedrock players will use to connect to your server.
|
|
port: 19132
|
|
|
|
# Some hosting services change your Java port everytime you start the server and require the same port to be used for Bedrock.
|
|
# This option makes the Bedrock port the same as the Java port every time you start the server.
|
|
# This option is for the plugin version only.
|
|
clone-remote-port: false
|
|
```
|
|
The vital part is the port. This is the port that Bedrock players will use to connect to your server.
|
|
Follow the instructions in the provider selector - change the port, and if necessary, `clone-remote-port` & `address`.
|
|
If `clone-remote-port` is enabled, the bedrock port will be overwritten with the Java port! <br>
|
|
**Important**: Other services/plugins that rely on ports with UDP, such as Voice Chats or Query, cannot share the port with Geyser.
|
|
|
|
5. Verify whether connections are possible by running `geyser connectiontest <ip>:<port>` in the console.
|
|
|
|
<div class="alert alert-info" role="alert">
|
|
To allow Bedrock Edition players to join your server without needing to log in to a paid Java Edition account, you can use <a href="/floodgate/setup/">Floodgate</a>.
|
|
</div> |