Hot Summer Deals are Here!
Celebrate with up to 99% off on 17,700 resources
02
Days
01
Hours
45
Mins
59
Secs

IP Forwarding / BungeeCord

Status
This thread has been locked.

Wauk

Feedback score
0
Posts
71
Reactions
6
Resources
0
Hey so I currently own a server that is partnered on UHC.gg (A UHC hosting website where a bunch of players see).

The website advisors want a direct IP to the uhc server, which I have setup already (uhc.ourdmain), but I also want to allow players to connect to our hub using (ourdomain) without the subdomain.

I tried setting up the IP forwarding, but this happens to the hub server (The first LeagueMC on player list):
https://gyazo.com/9b3e479c75b09cd717b9dd1077ccbc33
 
PebbleHost
High performance, consistent uptime and fast support. Minecraft hosting that just works.

Wauk

Feedback score
0
Posts
71
Reactions
6
Resources
0
So what's the problem? The MOTD example line thing?
Not really. Whenever the server list shows the 120 slots and messed up MOTD, it says "IF you wish to enable IP Forwarding, enable in bungee". But if it shows the normal MOTD, you can join the hub fine.
 

Wauk

Feedback score
0
Posts
71
Reactions
6
Resources
0
You forgot to uppercase the h in hub1 for the priorities option:
Code:
priorities:
  - hub1
Change it to this
Code:
priorities:
  - Hub1

Not sure if it'll fix it since there seems to be other plugins as well, which bungee plugins are you using?
The only bungee plugin i am using is EzQueueServer so I can have a queue in the hub
 

amit177

Aquatis LLC | aquatis.host
Supreme
Feedback score
4
Posts
32
Reactions
11
Resources
0
Repaste the config (it expired) and your DNS records
 

amit177

Aquatis LLC | aquatis.host
Supreme
Feedback score
4
Posts
32
Reactions
11
Resources
0
Something is wrong with your configuration.
One address points to port 25576 (uhc) while the other one points to 25565 (proxy)?
The UHC server is not supposed to be joinable, you are supposed to join it from the proxy (unless its not connected to the proxy meaning online-mode is true on that server), otherwise attackers can use the "bungee exploit".
If it was me, I would have exposed only 25565 to the public and kept the server ports as internal (best security).

Basically, you are supposed to have 2 records,
TYPE NAME HOST
A @ server_ip (no port)
A uhc1 server_ip (no port)

Theres no need for an SRV record when your bungeecord is on 25565.
After fixing that, make sure all of servers have "bungeecord" as true in spigot.yml and try joining.

Again, make sure to firewall the actual server ports except 25565, otherwise you could end up in a bad situation.
 
Status
This thread has been locked.
Top