To connect with other players and for the servers to securely identify a player’s identity, you need to enable IP forwarding. ![]() How To Setup IP Forwarding In BungeeCord? To see who is online on any of the BungeeCord servers that you’ve linked, run: /glist Switching Between Servers Without ReconnectingĬonnect to the BungeeCord address in Minecraft, and run /server name where name is the name you configured in the BungeeCord config.yml file. Save and exit.Ĭhange online-mode=true to online-mode=false. On the Spigot servers, navigate to the Spigot directory and open spigot.yml.Ĭhange bungeecord: false to bungeecord: true. Whenever you want to detach from the console, press Control-a followed by dĬonfiguring your Spigot servers for BungeeCord To connect to the server console, run: screen -r bungeecord Run chmod +x bungeestart.sh, to make the file executable. Screen -dmS "bungeecord" java -jar BungeeCord.jar You can do this by replacing the lobby in the line that says default_server: lobby with the label for your server. To allow for UUIDs to be correct in the Spigot servers, you should also ensure that you set ip_forward to true.įinally, you need to set the default server for players who connect. Change the line that reads motd: 'Just another Bungeecord - Forced Host' and put your custom message between the quotes. So that players can recognize your server more easily in their server list, you can set a custom message. These can be any word you want, but it’s important that they are descriptive, because they are used by the players to change servers. Servers : lobby : address : 203.0.113.112 : 25565 restricted : false motd : 'Just another BungeeCord - Forced Host' games : address : 203.0.113.198 : 25565 restricted : false motd : 'Just another BungeeCord - Forced Host'Įach server block has a label: In the case of the example, lobby or games. To prevent this, you can set up iptables to limit connections to only the BungeeCord server. This can make the servers vulnerable to people connecting directly, as they can connect with any username, potentially allowing for connection as a user with administrative permissions. To permit TCP on port 25565 run: sudo iptables -A INPUT -p tcp -dport 25565 -j ACCEPTĬonfiguring the Firewall on the Spigot Server Linodesįor BungeeCord, the Spigot servers need to be in offline mode, as the BungeeCord proxy handles the authentication. If you’re using iptables or ufw to act as a firewall, you’ll need to make a rule on the Linode running BungeeCord. sudo adduser bungeecordĬonfiguring the Firewall on the BungeeCord Node You need to save this password for future reference. ![]() sudo apt-get install screenĬreate another user for the BungeeCord proxy, so that it doesn’t have the same privileges as the user. This allows BungeeCord to run in the background, even when you are not connected to SSH. If not previously installed, you need to install OpenJDK JRE, an open source Java environment: sudo apt-get install openjdk-7-jre-headless Update the system: sudo apt-get update & sudo apt-get upgrade On the Linode that you plan to host BungeeCord: Updating and Installing Prerequisite Software This helps to keep it separate from other servers, and allows you to hide the IP of any back-end services.Īssume that the IP of the Linode you’re going to install BungeeCord on is 203.0.113.0, and there are two Spigot servers, with the IP addresses 203.0.113.112 and 203.0.113.198. Setting Up Your Linodeįor the purposes of this tutorial, you create another Debian or Ubuntu Linode to run BungeeCord. If you are not familiar with the sudo command, you can check the Users and Groups guide. Commands that require elevated privileges are prefixed with sudo. This guide is written for a non-root user.
0 Comments
Leave a Reply. |