I'm sure things like this are on the Minecraft Forum all the time. My problem is quite a bit more specific. I'm running the Server on a Cent OS Machine and testing it from another computer on the same network.
I know that "Can't connect to server." is usually referring to a port or ip issue. I will tell you what I have tried so far.
I am using noip to get the ip to be "blahblah.zapto.org"
I have tried connecting using "blahblah.zapto.org" with failure.
I have tried looking up "my ip address" and using that, which also failed.
I have tried the computer's port which is "192.168.1.14" with failure.
I have tried "localhost" from the host machine, this works.
I have double checked that noip is running, which it is.
I have double checked that the ports are forwarded on the router, which they are (and to the correct ip address).
canyouseeme doesn't see me.
I have checked the iptables to make sure linux is not blocking the ports, which it isn't.
All suggestions are appreciated, it's very likely that I'm just forgetting one of the things you are supposed to double check when doing this (I've done this a lot).
when your setting up the server, you need to specify the port the server will use, normally people will use 25565, the default port. You need to set he port to 25566 (something other than the default port). Also how are you finding your computers ipv4 address? using a website or command promp?
Using Command Prompt type ipconfig /all and find your computers Ipv4 address under your Network adapter.
Example:
yeah so make sure you got the right computer ip address.
Next make sure your firewalls have exceptions made so minecraft can access the internet.
Also concerning your domain pointing. You can do it that way, OR
set Up hosting through https://www.hostgator.com/coupons Only 1 cent for the first month, this will allow you to connect a domain to the service which you can get a FREE domain a freenom.com. I'm happy to pay the 1 cent if you can't.
After you have set that up all you have to do then is set up an A record so basically will do this 190.12.567.2 -> mc.Hotbling.tk But you'll have to add the ip at the end of the domain so mc.hotbling.tk:25566
All done!
Cheers,
DivineMadness | OrbitalGamingAU | Manager
Rollback Post to RevisionRollBack
Proud Owner of TrinxMC! An epic community with epic people such as you!
Port forwarding has nothing to do with your problem. Don't use your noip domain to connect. Most home routers do not support NAT reflection, which means using externally facing services from inside the LAN. Using the server's private/internal IP is what you want to do (the 192 one). As to why it's not working, that's usually a lack of a firewall exception. When you try to connect with the 192 IP, does the console show the attempt?
1st of all, I'm not using Windows so "Command Prompt" does not exist, and neither does "ipconfig".
2nd of all, why should I set the port of the server to anything other than default.
3rd of all, I've been using noip forever, that is not the problem.
4th of all, don't tell me to try a different ip address. In the original post I listed all of the addresses I have already tried using.
So please, either reread my post and try to help me again or someone else can do it.
@Tundral
Attached is my port forwarding.
I assume the part directed at me is #3, as I mentioned that. Yes, I read your post, otherwise I wouldn't have recommended not using an external interface address internally. Did YOU not read MY post at all? Lemme help you:
-->> Most <<-- home routers do not support NAT reflection
Most. Not all. If you were using a no-ip domain internally before and it worked, then obviously your router supports NAT reflection and it's not relevant. That said, I'm not psychic. In your original post, you said "I have tried connecting using "blahblah.zapto.org" with failure" and you never said it worked before. You said the DUC is running, but that has no bearing on connectivity.
Oh, and you also said "All suggestions are appreciated". Apparently you lied since you got snarky when I made a suggestion. I can't mention the word I have for an attitude like that toward people trying to help you as I don't want another profanity warning.
I would disagree with the fact that you made any suggestions. What you said was to try using the "192" ip. But if you had read my post, you would know that I have tried that. I can guarantee that the issue is something to do with ports being blocked or something. Which is why I'm confused and coming here. Because I had already made sure "iptables" was not blocking the port and the port is forwarded on the router. I'm not looking for help troubleshooting the problem, I have already given all of the troubleshooting that is necessary (As far as I know). I need help fixing the problem.
If you want any information ask for it, I either already know it, or I can quickly figure it out.
My suggestion was to try to connect and tell us what the console said. The troubleshooting stuff you posted that you've done isn't enough. How do you expect us to tell you how to fix it if we don't know what is going on? You like keeping on with the accusations of me not reading your post (though I did and you just keep misinterpreting what I'm saying), well, I can say the same of you because didn't apparently read why I said that:
When you try to connect with the 192 IP, does the console show the attempt?
Whether or not the console is reacting will help narrow down at what stage the connection is failing. I said to use the 192 IP since you were trying all sorts of different things to connect before. At that time, I wasn't sure if you had a NAT reflection enabled router or not so I said the 192 to prevent you trying with an external interface.
You know what? Nevermind. I don't even care at this point; trying to assist someone like you is too mentally exhausting to deal with.
Well, I apologize for being snappy. I just feel that often people don't read posts well enough on forums and I saw someone making a suggestion related to Windows and my mind quickly said that all other suggestions would also be bad.
To answer your question, no, attempting to connect does not give any output in the console.
I'm sure things like this are on the Minecraft Forum all the time. My problem is quite a bit more specific. I'm running the Server on a Cent OS Machine and testing it from another computer on the same network.
I know that "Can't connect to server." is usually referring to a port or ip issue. I will tell you what I have tried so far.
I am using noip to get the ip to be "blahblah.zapto.org"
I have tried connecting using "blahblah.zapto.org" with failure.
I have tried looking up "my ip address" and using that, which also failed.
I have tried the computer's port which is "192.168.1.14" with failure.
I have tried "localhost" from the host machine, this works.
I have double checked that noip is running, which it is.
I have double checked that the ports are forwarded on the router, which they are (and to the correct ip address).
canyouseeme doesn't see me.
I have checked the iptables to make sure linux is not blocking the ports, which it isn't.
All suggestions are appreciated, it's very likely that I'm just forgetting one of the things you are supposed to double check when doing this (I've done this a lot).
Thanks in advance,
CyberSoul
Could you post a screenshot of the portfowards?
Tundral, Founder and head manager of the Apex Land minecraft server.
IP: apex.land
hello,
when your setting up the server, you need to specify the port the server will use, normally people will use 25565, the default port. You need to set he port to 25566 (something other than the default port). Also how are you finding your computers ipv4 address? using a website or command promp?
Using Command Prompt type ipconfig /all and find your computers Ipv4 address under your Network adapter.
Example:
yeah so make sure you got the right computer ip address.
Next make sure your firewalls have exceptions made so minecraft can access the internet.
Also concerning your domain pointing. You can do it that way, OR
set Up hosting through https://www.hostgator.com/coupons Only 1 cent for the first month, this will allow you to connect a domain to the service which you can get a FREE domain a freenom.com. I'm happy to pay the 1 cent if you can't.
After you have set that up all you have to do then is set up an A record so basically will do this 190.12.567.2 -> mc.Hotbling.tk But you'll have to add the ip at the end of the domain so mc.hotbling.tk:25566
All done!
Cheers,
DivineMadness | OrbitalGamingAU | Manager
Proud Owner of TrinxMC! An epic community with epic people such as you!
Website: Coming Soon!
Discord: Here!
Port forwarding has nothing to do with your problem. Don't use your noip domain to connect. Most home routers do not support NAT reflection, which means using externally facing services from inside the LAN. Using the server's private/internal IP is what you want to do (the 192 one). As to why it's not working, that's usually a lack of a firewall exception. When you try to connect with the 192 IP, does the console show the attempt?
@Verinity
@Strahan202
Did either of you read my post at all.
1st of all, I'm not using Windows so "Command Prompt" does not exist, and neither does "ipconfig".
2nd of all, why should I set the port of the server to anything other than default.
3rd of all, I've been using noip forever, that is not the problem.
4th of all, don't tell me to try a different ip address. In the original post I listed all of the addresses I have already tried using.
So please, either reread my post and try to help me again or someone else can do it.
@Tundral
Attached is my port forwarding.
I assume the part directed at me is #3, as I mentioned that. Yes, I read your post, otherwise I wouldn't have recommended not using an external interface address internally. Did YOU not read MY post at all? Lemme help you:
-->> Most <<-- home routers do not support NAT reflection
Most. Not all. If you were using a no-ip domain internally before and it worked, then obviously your router supports NAT reflection and it's not relevant. That said, I'm not psychic. In your original post, you said "I have tried connecting using "blahblah.zapto.org" with failure" and you never said it worked before. You said the DUC is running, but that has no bearing on connectivity.
Oh, and you also said "All suggestions are appreciated". Apparently you lied since you got snarky when I made a suggestion. I can't mention the word I have for an attitude like that toward people trying to help you as I don't want another profanity warning.
I would disagree with the fact that you made any suggestions. What you said was to try using the "192" ip. But if you had read my post, you would know that I have tried that. I can guarantee that the issue is something to do with ports being blocked or something. Which is why I'm confused and coming here. Because I had already made sure "iptables" was not blocking the port and the port is forwarded on the router. I'm not looking for help troubleshooting the problem, I have already given all of the troubleshooting that is necessary (As far as I know). I need help fixing the problem.
If you want any information ask for it, I either already know it, or I can quickly figure it out.
*sigh*
My suggestion was to try to connect and tell us what the console said. The troubleshooting stuff you posted that you've done isn't enough. How do you expect us to tell you how to fix it if we don't know what is going on? You like keeping on with the accusations of me not reading your post (though I did and you just keep misinterpreting what I'm saying), well, I can say the same of you because didn't apparently read why I said that:
Whether or not the console is reacting will help narrow down at what stage the connection is failing. I said to use the 192 IP since you were trying all sorts of different things to connect before. At that time, I wasn't sure if you had a NAT reflection enabled router or not so I said the 192 to prevent you trying with an external interface.
You know what? Nevermind. I don't even care at this point; trying to assist someone like you is too mentally exhausting to deal with.
Well, I apologize for being snappy. I just feel that often people don't read posts well enough on forums and I saw someone making a suggestion related to Windows and my mind quickly said that all other suggestions would also be bad.
To answer your question, no, attempting to connect does not give any output in the console.