Hi, so this is the basics of my issue: I can't connect to my multicraft server in Minecraft (even after setting everything up correctly as far as I can tell) but I can run the default multiplayer software just fine and everyone can connect.
Long and kind of boring explanation (but you should take a look anyway)
I've been running the default 1.12 server software for a while now. I've setup port forwarding correctly (however on a different port than the default: 26565) and everyone can connect without any troubles. Easy. What doesn't make sense is after setting up Multicraft and it having no issues with the server loading, or the daemon is that no-one (even on another computer in the same house on the same network) can connect. The only person who can connect is me (and that's most likely because I can just connect with localhost).
I have tried multiple versions of the same IP (and yes, I do have a static ip) and different ports, and people have tried connecting with the external IP as well as pretty much any other method we could think of. I have spent a couple days now and have had no luck. I have tried restarting, restarting the daemon, and reinstalling multicraft, and nope.
Some weird things that I've noticed:
When going on this website which I have seen mentioned sometimes, it tells me that the only port that is open is 80, which doesn't make sense as people have connected to multiple ports that have been port forwarded (26565, 25656, 26566) and they have all worked with the default multiplayer software with the same ip used in that website.
Didn't realise that the program using the port had to be open and running, but this leaves me with more questions, because now I have no idea how to get the router to forward the port if it's different to my computers ip or whatever.
As mentioned before, another computer sitting literally right next to my computer wired to the same router on the same network can't access the Multicraft server, and even when accessing the default software server, it has to use my external ip, which I'm pretty sure is not right.
Even though there will probably be something so obvious and stupidly simple that I haven't done, I can't think of anything else, so if there is any suggestions I will try. Thanks
Well, just as I thought, it was an obvious fix. And if anyone has the same issue, I'll explain how I fixed it:
Turns out that the issue was just a firewall issue, and I'm not completely stupid, so I did check it. HOWEVER, turns out a lot of the open port checker sites lie. Two of them both said that port 26566 was closed, even though I port forwarded. Then I checked another website, and it said "filtered". That means that the port is in fact open but a firewall is blocking my local ip address from being able to listen. I have disabled the firewall on my router, so that meant it was my computer blocking it.
To fix it I went to advanced settings in firewall and did the following steps:
Right click on Inbound Rules and select New rule...
Select port and click next
Select tcp and enter the port (in my case it was 26566) and click next
Click allow the connection and click next
Name it and click next
And it works!
Rollback Post to RevisionRollBack
This post will be yet another source of data that people may possibly look back on when I inevitably die. Better make it good then