ok, it was the DUMBEST mistake ever, i think. i just missed a line for the server settings somehow. added that and the server runs and shows up as well...

You can rotate the ghost rail and it will hold the assigned direction for the last piece

It's not a Docker container tho. It's a VM in my ProxMox machine. Running the binary without systemd i can see the server and connect to it through LAN at least. but it could still be some port misalignment. the VM doesnt have a firewall on its own, i have a higher order firewall and that should ...

SIGTERM is sent by me, because it doesn't show up on the LAN network, so i killed it.

ok, well, i need to keep testing then. still a mystery why it doesnt show up started with a daemon.

also, is there a way, that it could keep writing logs? would feel better, if i could check the logs too, if ...

So let me start with that I'm new to home labbing and I'm trying to set up my own headless server in a Proxmox machine.

Until now i have tried to run the server in a ssh shell and with a bash script. i have a config file that lets the game read the main installation but write to a separate users ...

absolutely wild

could you perhaps share what you did, if you can remember? im also having trouble with a server connection

Hello!

have you found a solution for this? im also struggiling to see my headless server that ive set up on a seperate machine. i can connect to it directly, but the server doesnt show on browser list

yea, this is quite annoying. i cant use the numpad for calculations and numbers, because i have to use the period as a decimal

i am encountering the same problem. i had a parametrized blueprint that worked. i wanted to improve the numbers and parameters. accidentally deleted it but i cannot remake it, the 'p0_s' already throws an error "unknown variable" @ 'p'. but im at 2.0.47, so... an older issue?

I'm not a fast player and I've yet to reach other planets (mostly because I'm taking it slow, I have the technology), but I have not been bothered by the cliffs. Don't know, if they are more forgiving, but they look better and actually offer some strategic advantages now, compared to 1.1. I suggest ...