Giving out your IP is a lot like giving out your address and your phone number.
Most the time you can trust people with it, but if you aren't careful, some stranger with bad motives could come rob you. Or, he could randomly find you and rob you.
Do you actually got an IDEA of how much a RAM costs?
~40-50 USD for 4gig DDR3.
However, throwing more RAM will not fix this issue. There is a memory leak somewhere that will still appear if you have 4gig or 48gigs of ram.
You say it used to run a lot better? Did anything at all change? Driver update? Windows update? Anything, something had to change as memory leaks don't just appear in a system working normally? Did you add/remove a mod?
looks like you havent set a local ip for the server program.
input your computers local ip into the ip settings in server.properties, that should fix it
You do not *need* to set the ip in server.properties, see my sig for more details on what that setting does and what it's used for.
@OP
Did you setup port forwarding and everything on your router? If no, and you're friends are directly connected to your router, that would be why they couldn't connect.
Don't resort to deleting everything when things go bad, this often solves nothing and is unnecessary.
You'll need to redownload the server.jar or server.exe to fix the crash issue.
Does connection refused:connect show up when you attempt to connect via external IP?
If so, forwarding is working and something else is preventing him from connecting. If forwarding was not working, you wouldn't see anything in the log when attempting to connect via external IP.
*Hopefully someone will sticky this but doubtful*
*typed up quickly, may have some repetitive things in it*
So you're running a server. You've set the server-ip and life is good but you don't really know why you set it.
Here's a working example of how, why, and what should be set in the server.properties file for IP and port settings
Example environment: My Home server
Hardware:
Dual Process, Dual Core, HT Xeon 2.8ghz. (8 total cores)
18gB of ram
Dual 10/100/1000 NIC, 192.168.0.105 set to 10/10/1000, 192.168.0.101 set to 10/100 (this is important later)
2x74gig 15000rpm SAS RAID 1
2x1.5tB 7200rpm SATA RAID 1
Software:
Windows server 2008
Java 7 JDK
Headless server (Remote desktop only)
Server 1: Vanilla
Server 2: Vanilla Creative (Wife hates normal mode)
Server 3: bukkit testing and implementation (will eventually be live to replace the other 2 once mutiverse is working as I want)
1) Basic usage
For the average server operator, operating out of their own house, you can leave server-ip and the server-port at their default settings, blank and 25565.
In fact, putting the wrong IP or wrong port on these lines will cause severe errors and prevent the server from actively binding to the IP address and port needed to run.
For single server, single NIC usage, the two lines should look like this:
server-ip=
server-port=25565 (Unless you need a different port)
2) server-ip and server-port and their errors explained
Server-port:
This is the cause of most unable to bind errors, despite it showing up when the wrong IP is put into the server.properties file. What's happeneing is the server attempts to reserve itself a port on the supplied IP address. If it can't use the IP address, say, the wrong one was put in, it can't bind the port, so it will throw an error.
Also, if two servers are attempting to use the same port number, you will also receive this error. One server has already claimed it and won't give it up to share with another. This is a good thing. You don't want two servers trying to connect on the same port. Confusion would result.
Server-ip:
On the default setting, blank, the minecraft server will listen on all available IP's on the computer. So in my case, a user on my LAN could connect to both .101 and .105 on my server if I left the ip blank.
Incorrectly configuring both settings will give you the same error. Unable to Bind.
3) server-ip and server-port advanced usage.
As you noticed early I have 3 servers running on one computer with two network cards. One of the issues I had running servers, which is important to note why I have it set a certain way, is that there's a driver bug with my NIC chipset that causes buffer issues while running it at 10/100/1000 and running a minecraft server. Users would get disconnected approximately every five to ten minutes for no reason. So I forced one NIC to run only at 10/100, the .101 card.
Each server has it's own directory on the RAID array.
In the server.properties for each, this is what I have (as well as server specific names, seeds, and other settings):
Server 1:
server-ip=192.168.0.101
server-port=25565
Server 2:
server-ip=192.168.0.101
server-port=25566
What I've done here is forced all servers to only listen on .101. This prevents anyone from using .105 to connect. In fact, it will show as unreachable if you try on .105 no matter where you are on the LAN. Also, this doesn't affect port forwarding at all. Port forwarding is setup so that 25565-25567 are all forwarded to .101, where the servers are listening.
Had I set two to the same port or had a used an IP other than 192.168.0.101, .105, I would receive the Unable to Bind Error.
4) Additional information
The server-ip settings is primarily intended for deployng multiple minecraft servers on a single computer through dedicated interfaces. For example, one card may be dedicated to serving files up on the internal network and you don't want to bog down the interface with non-file related data.
The port functionality gives you more control over setting where the server listens as today's computers have so many pieces of software it's entirely possible another piece of software would be running on that port already. Giving you the Unable to Bind error.
Unfortunately a bad setting in either server-ip or server-port throws the same error so it may not always be clear where the problem is.
Opening up /give or creative mode can ruin the gameplay for other people. It's not fun when I bust my ass to build something epic and someone else spends $70 just get access to be able to build what ever they want.
The performance difference between windows and a linux distro won't matter until you really start stressing the hardware to it's limits. Something most home servers won't do unless you've got an insane upload speed.
1
Most the time you can trust people with it, but if you aren't careful, some stranger with bad motives could come rob you. Or, he could randomly find you and rob you.
1
2
1
~40-50 USD for 4gig DDR3.
However, throwing more RAM will not fix this issue. There is a memory leak somewhere that will still appear if you have 4gig or 48gigs of ram.
You say it used to run a lot better? Did anything at all change? Driver update? Windows update? Anything, something had to change as memory leaks don't just appear in a system working normally? Did you add/remove a mod?
1
You do not *need* to set the ip in server.properties, see my sig for more details on what that setting does and what it's used for.
@OP
Did you setup port forwarding and everything on your router? If no, and you're friends are directly connected to your router, that would be why they couldn't connect.
Don't resort to deleting everything when things go bad, this often solves nothing and is unnecessary.
You'll need to redownload the server.jar or server.exe to fix the crash issue.
1
If so, forwarding is working and something else is preventing him from connecting. If forwarding was not working, you wouldn't see anything in the log when attempting to connect via external IP.
1
*typed up quickly, may have some repetitive things in it*
So you're running a server. You've set the server-ip and life is good but you don't really know why you set it.
Here's a working example of how, why, and what should be set in the server.properties file for IP and port settings
Example environment: My Home server
Hardware:
Dual Process, Dual Core, HT Xeon 2.8ghz. (8 total cores)
18gB of ram
Dual 10/100/1000 NIC, 192.168.0.105 set to 10/10/1000, 192.168.0.101 set to 10/100 (this is important later)
2x74gig 15000rpm SAS RAID 1
2x1.5tB 7200rpm SATA RAID 1
Software:
Windows server 2008
Java 7 JDK
Headless server (Remote desktop only)
Server 1: Vanilla
Server 2: Vanilla Creative (Wife hates normal mode)
Server 3: bukkit testing and implementation (will eventually be live to replace the other 2 once mutiverse is working as I want)
1) Basic usage
For the average server operator, operating out of their own house, you can leave server-ip and the server-port at their default settings, blank and 25565.
In fact, putting the wrong IP or wrong port on these lines will cause severe errors and prevent the server from actively binding to the IP address and port needed to run.
For single server, single NIC usage, the two lines should look like this:
server-ip=
server-port=25565 (Unless you need a different port)
2) server-ip and server-port and their errors explained
Server-port:
This is the cause of most unable to bind errors, despite it showing up when the wrong IP is put into the server.properties file. What's happeneing is the server attempts to reserve itself a port on the supplied IP address. If it can't use the IP address, say, the wrong one was put in, it can't bind the port, so it will throw an error.
Also, if two servers are attempting to use the same port number, you will also receive this error. One server has already claimed it and won't give it up to share with another. This is a good thing. You don't want two servers trying to connect on the same port. Confusion would result.
Server-ip:
On the default setting, blank, the minecraft server will listen on all available IP's on the computer. So in my case, a user on my LAN could connect to both .101 and .105 on my server if I left the ip blank.
Incorrectly configuring both settings will give you the same error. Unable to Bind.
3) server-ip and server-port advanced usage.
As you noticed early I have 3 servers running on one computer with two network cards. One of the issues I had running servers, which is important to note why I have it set a certain way, is that there's a driver bug with my NIC chipset that causes buffer issues while running it at 10/100/1000 and running a minecraft server. Users would get disconnected approximately every five to ten minutes for no reason. So I forced one NIC to run only at 10/100, the .101 card.
Each server has it's own directory on the RAID array.
In the server.properties for each, this is what I have (as well as server specific names, seeds, and other settings):
Server 1:
server-ip=192.168.0.101
server-port=25565
Server 2:
server-ip=192.168.0.101
server-port=25566
Bukkit Server:
server-ip=192.168.0.101
server-port=25567
What I've done here is forced all servers to only listen on .101. This prevents anyone from using .105 to connect. In fact, it will show as unreachable if you try on .105 no matter where you are on the LAN. Also, this doesn't affect port forwarding at all. Port forwarding is setup so that 25565-25567 are all forwarded to .101, where the servers are listening.
Had I set two to the same port or had a used an IP other than 192.168.0.101, .105, I would receive the Unable to Bind Error.
4) Additional information
The server-ip settings is primarily intended for deployng multiple minecraft servers on a single computer through dedicated interfaces. For example, one card may be dedicated to serving files up on the internal network and you don't want to bog down the interface with non-file related data.
The port functionality gives you more control over setting where the server listens as today's computers have so many pieces of software it's entirely possible another piece of software would be running on that port already. Giving you the Unable to Bind error.
Unfortunately a bad setting in either server-ip or server-port throws the same error so it may not always be clear where the problem is.
1
Opening up /give or creative mode can ruin the gameplay for other people. It's not fun when I bust my ass to build something epic and someone else spends $70 just get access to be able to build what ever they want.
Might as well just start a creative server.
1
What ever you're comfortable with.
The performance difference between windows and a linux distro won't matter until you really start stressing the hardware to it's limits. Something most home servers won't do unless you've got an insane upload speed.
1
What you're referring to is unauthorized system access. This is illegal unders several federal laws.
Hacking, unfortunately, was a term which was created as evil and negative through media usage.