[SOLVED] Create a server on DigitalOcean

Hello, I have a droplet on DigitalOcean and I want to know if it's possible to creare a Xonotic server there, and what are the steps to do that.

I tried running the server_linux.sh script, I configured the server.cfg file and it appears to be working, but when I try to connect from my client, I can't find my server.

Does anyone have a server running on DigitalOcean or any other VPS?

Hello, I have a droplet on DigitalOcean and I want to know if it's possible to creare a Xonotic server there, and what are the steps to do that.

I tried running the server_linux.sh script, I configured the server.cfg file and it appears to be working, but when I try to connect from my client, I can't find my server.

Does anyone have a server running on DigitalOcean or any other VPS?

Did you set ?

sv_public 1

What port did you select?

port 27000

Did you try to connect manually by typing in the IP and port into the Address field in the game?

Any errors in console when you start the server?

Did you set ?

sv_public 1

What port did you select?

port 27000

Did you try to connect manually by typing in the IP and port into the Address field in the game?

Any errors in console when you start the server?

Yes, I set `sv_public 1` on server.cfg file, by default the port is 27000.
I see I have to copy de server.cfg file to data/ directory in order to make it work, I just did that and my Server is up un running now.

Now I have to start digging on the server.cfg file to see what other things I can do
(for example to set a password to connect and other stuff)

Passworded servers don't exist, sorry!

Well if you have a firewall on the vps I guess you could allow only certain IP's to access the port. Wonder if there are any automated scripts where you enter a password and the script modifies the firewall rules to allow the IP from where the password is sent.

Talked to Melano and he says he can mplement an allowed IP feature controlled by rcon. Will repost then ready.

Hm. Unless it's on the engine or IP stack level, I doubt it will work. As far as I know, connections have to be fully established before QC can access the client's info.

EDIT: I can't find traces of it, but I'm pretty sure I've discussed or seen a discussion with engine devs related to this. Anyway, can Melanosuchus discuss this in public perhaps, so we can see and discuss the idea before the implementation?

Hm. Unless it's on the engine or IP stack level, I doubt it will work. As far as I know, connections have to be fully established before QC can access the client's info.

EDIT: I can't find traces of it, but I'm pretty sure I've discussed or seen a discussion with engine devs related to this. Anyway, can Melanosuchus discuss this in public perhaps, so we can see and discuss the idea before the implementation?

its part of the ESK modpack https://github.com/mbasaglia/esk-modpack..._whitelist

I'll have to set up a test server tomorrow to mess around too late now to do it.

Hm. I wouldn't expect much privacy from a QC-based whitelist then, because of the window of time between connection and kick.

A protection on the server should rather be a mechanism that disallows connection, rather than allowing it and only kicking after the client has fully connected to the server.

If you're going to use this whitelist, I suggest you set sv_public to -1 when everyone's on the server.

EDIT: Is there any reason this modpack is coded in parallel to "official" development without any communication between the two? Do the developers feel that their changes can't get into our master branch? I think this should be discussed.