F5F Stay Refreshed Power Users Networks Connect your cloud host to your home server for the Minecraft network.

Connect your cloud host to your home server for the Minecraft network.

Connect your cloud host to your home server for the Minecraft network.

P
PlexiYT
Junior Member
14
06-02-2016, 11:52 AM
#1
Hey everyone, I'm facing a tricky issue with my Minecraft setup. I have a cloud server at Kinetic Hosting running a proxy for a lobby and a vanilla server. I need to connect that proxy back to my home server so players can join too, especially since RAM costs are high there. The server is reachable from the internet via my phone hotspot, but when using the proxy, the proxy logs a timeout and no connection appears on the home server. The hoster said nothing should block the connection. I'm not sure what to do next. Any suggestions?
P
PlexiYT
06-02-2016, 11:52 AM #1

Hey everyone, I'm facing a tricky issue with my Minecraft setup. I have a cloud server at Kinetic Hosting running a proxy for a lobby and a vanilla server. I need to connect that proxy back to my home server so players can join too, especially since RAM costs are high there. The server is reachable from the internet via my phone hotspot, but when using the proxy, the proxy logs a timeout and no connection appears on the home server. The hoster said nothing should block the connection. I'm not sure what to do next. Any suggestions?

S
SparkingFires
Member
53
06-02-2016, 04:59 PM
#2
forge servers dont like going trough proxies like waterfall. there's some level of support on the waterfall side of things, but if any of the mods messes with the netcode (which a large portion of them do) it's gonna get caught up on that and you're SOL. if you want to do this, there's two options: - bite the bullet and host your modded server in the cloud - use a TCP proxy instead of waterfall, so the server can be at home, but the public address is somewhere with decent infrastructure.
S
SparkingFires
06-02-2016, 04:59 PM #2

forge servers dont like going trough proxies like waterfall. there's some level of support on the waterfall side of things, but if any of the mods messes with the netcode (which a large portion of them do) it's gonna get caught up on that and you're SOL. if you want to do this, there's two options: - bite the bullet and host your modded server in the cloud - use a TCP proxy instead of waterfall, so the server can be at home, but the public address is somewhere with decent infrastructure.

T
thebjmax1
Senior Member
395
06-02-2016, 06:02 PM
#3
Thanks for the update! The setup is confirmed to function well in your home network, so waterfall issues aren’t present. Once the forge option was activated, everything operated smoothly without any hiccups.

The extra cost of $22 per month would be due to the server you already have running, and you’d prefer to avoid additional charges. This also presents a challenge because you aim to connect to both the vanilla cloud-hosted server and your home-hosted modded servers from a single address.

Any suggestions? It’s possible the issue lies on the Kinetics side. I’ve had similar problems before with certain internet connections preventing my IPv6-only server from being recognized. Could this be the root cause here?
T
thebjmax1
06-02-2016, 06:02 PM #3

Thanks for the update! The setup is confirmed to function well in your home network, so waterfall issues aren’t present. Once the forge option was activated, everything operated smoothly without any hiccups.

The extra cost of $22 per month would be due to the server you already have running, and you’d prefer to avoid additional charges. This also presents a challenge because you aim to connect to both the vanilla cloud-hosted server and your home-hosted modded servers from a single address.

Any suggestions? It’s possible the issue lies on the Kinetics side. I’ve had similar problems before with certain internet connections preventing my IPv6-only server from being recognized. Could this be the root cause here?

C
Conrarr
Junior Member
4
06-02-2016, 07:12 PM
#4
The configurations in both testing and host setups aren't exactly the same—only the IP addresses differ. As for the extra configuration, it seems to be applied to servers on separate machines, not all tests running from a single machine.
C
Conrarr
06-02-2016, 07:12 PM #4

The configurations in both testing and host setups aren't exactly the same—only the IP addresses differ. As for the extra configuration, it seems to be applied to servers on separate machines, not all tests running from a single machine.

M
Mihnea_X
Member
63
06-06-2016, 02:54 PM
#5
They match exactly, apart from IP addresses and BungeeGuard tokens. The test was executed on Debian Linux via the frontend Pterodactly; my host uses its own frontend built around Pterodactyl, making it probable they’re identical. All local network tests ran on the server I’m connecting to the proxy on right now, though I also verified linking to another device in my home network succeeded.
M
Mihnea_X
06-06-2016, 02:54 PM #5

They match exactly, apart from IP addresses and BungeeGuard tokens. The test was executed on Debian Linux via the frontend Pterodactly; my host uses its own frontend built around Pterodactyl, making it probable they’re identical. All local network tests ran on the server I’m connecting to the proxy on right now, though I also verified linking to another device in my home network succeeded.