How to portforward for minecraft votifier using UFW

Technical Support
,
1

OS Name/Version: Debian 12

Product Name/Version: (Always use the full version number - not ‘Latest’) Temurin 21

Problem Description: I do not know how to “port forward” a selected port using UFW on a VPS, purchased by Hostinger. I am attempting to use votifier for my minecraft server, but cannot figure out how to do so. I have attempted to search for tutorials, but mostly finding ones that don’t work or aren’t attempting the same end goal that votifier requires (Im not sure about that part)

Steps to reproduce:

  • Step 1 Purchase Debian 12 server on Hostinger
  • Step 2 Obtain Plugins necessary, and connect a server to a minecraft server list such a planet minecraft that has a tester for it.
  • Step 3 Test server with chosen number that has been put into config, with no response.

Actions taken to resolve so far: Attempted several fixes such as : Setting Up a Port Forwarding Using UFW (Uncomplicated Firewall) , How to install UFW and use it to set up a basic firewall - LinuxConfig , Hostinger AI Helper, Videos on Votifier Installation and Configuration

2

Note, this isn’t Hostinger support, just the forum for AMP.
You can use the edit “pen”/“pencil” icon in the main panel to add a port to an instance (under networking), and that is automatically added to the firewall.

1 Like
3

Hostinger would only take me so far as to access my VPS via PuTTy, sadly. About the pen/pencil icon, I am a bit confused. The main panel of what?

4

The main AMP interface where (I’m assuming) you’re managing your Minecraft server(s).
Unless you aren’t using Hostinger’s pre-installed AMP VPS, then that would would all sound like mumbo-jumbo (in which case you’d want to ask Hostinger’s support for further assistance)

1 Like
5

I found it, Im guessing I just label the Port as TCP ?

6

If that’s the protocol that Votifier uses. You can select “both” if you want to play it safe, or double check Votifier’s documentation to see if they have a note in there

7

That does not seem to have done the job. For extra info, I am using 5555 as the port

8

You can run ampinstmgr dumpfirewall and ampinstmgr updatefirewall as root to double check and force-apply the firewall rules

1 Like
9

Should I have “Exclude from firewall” enabled for the ports? The double check and force-apply did not work. The 5555 port doesn’t pop up in the instance menu, unlike the regular unlike the 25565 and 2224, but is in the ports menu

10

Excluding the instance from the firewall will prevent the ports from being added (be sure to press the add (plus) and save buttons when adding the port)

1 Like
11

I made sure to do both of those, and have restarted the instance a few times. Do I need to reboot the VPS entirely?

12

You shouldn’t need to, did the port show up when you dumped the firewall rules? Also note, the server must be running and votifier must be loaded for that test of yours to work (check the log to see if it loads correctly)

13

I ran the commands again just to double check, it was there and there was no updates. I attempted the test again and it did not work.

14

No, I meant run the first command to see if the port you added shows in AMP’s list of firewall rules

15

Oh, when I run the first command, ampinstmgr dumpfirewall , it lists it. Should I not be running ampinstmgr updatefirewall?

16

Running updatefirewall when there’s nothing to update just won’t do anything.
From AMP’s side of things the port should be good to go, so it may be down to configuring Votifier.

1 Like
17

Found out the issue. Perhaps it is because my connection IP has numbers and letters, but setting the IP to 0.0.0.0 to listen to all IPs worked in configs. Thanks.

18

Ah, that might’ve been the IPv6 address, I’ll remember to tell people to check that if they come across a similar issue

19

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.