#Linux Guide for hosting the server on an actual server?

1 messages · Page 1 of 1 (latest)

celest moon
#

I would love to be able to run this on my main Proxmox Box

oak valley
celest moon
#

yes i see this

â–¸ Can I run on Linux / headless?
Currently Windows-only, unfortunately.

It was more of a request for compatability.

astral lance
#

Runs just fine on Proton/Wine, it just isnt something their team can provide support for ~

daring portal
balmy flint
daring portal
modest shell
#

fine work good sir, plug and play for me

candid urchin
candid urchin
#

Oh really? I tried proton yolk and had System.PlatformNotSupportedException: Video driver not supported error. How are you running? For StarRupture (another egg I created) it was just proton run path/to/server/exe

untold hull
modest shell
#

the only strange thing i find with the server is that it consumes more processing power wheen no player is connected

errant sable
#

@daring portal Mind contacting me about this in DMs please?

astral lance
candid urchin
blissful wharf
#

I'm building a proton version and running the R5 WindroseServer-Win64-Shipping.exe directly.
It works without xvfb setup. I'm fiddling around a little more and share the repo shortly.

errant sable
blissful wharf
wind furnace
#

I have a server up and running with a friend on it using bog-standard wine with only vcrun2022 winetricked in to the prefix. Server is running Mint 22.3.

gloomy parcel
#

can confirm, headless ubuntu server here, running with screen, xvfb, and wine. winetricks win10, everything else running fine out of box (aside from local connection issue, they know and are working on that)

calm fog
tropic crescent
modest shell
#

hey where can i report server crashes? i have these logs:
[2026.04.15-03.54.25:347][252]LogOutputDevice: Error: === Crash Stack Trace: ===

[2026.04.15-03.54.25:347][252]LogOutputDevice: Error:

[2026.04.15-03.54.25:347][252]LogOutputDevice: Error: [Callstack] 0x000000014ba5bc98 WindroseServer-Win64-Shipping.exe!UnknownFunction []

[2026.04.15-03.54.25:347][252]LogOutputDevice: Error: [Callstack] 0x000000014ba59f6e WindroseServer-Win64-Shipping.exe!UnknownFunction []

[2026.04.15-03.54.25:348][252]LogOutputDevice: Error: [Callstack] 0x000000014bf890ef WindroseServer-Win64-Shipping.exe!UnknownFunction []

[2026.04.15-03.54.25:348][252]LogOutputDevice: Error: [Callstack] 0x000000007b627e49 kernel32.dll!BaseThreadInitThunk() [Z:\home\steam\server-files\R5\Binaries\Win64\dlls\kernel32\thread.c:61]

[2026.04.15-03.54.25:348][252]LogOutputDevice: Error: [Callstack] 0x000000017005dca8 ntdll.dll!RtlUserThreadStart() [Z:\home\steam\server-files\R5\Binaries\Win64\dlls\ntdll\thread.c:285]

[2026.04.15-03.54.25:348][252]LogOutputDevice: Error: [Callstack] 0x0000000000000000 UnknownFunction []

[2026.04.15-03.54.25:348][252]LogOutputDevice: Error: [Callstack] 0x000000014bf89040 WindroseServer-Win64-Shipping.exe!UnknownFunction []

[2026.04.15-03.54.25:348][252]LogOutputDevice: Error: [Callstack] 0x00000000036ebf20 UnknownFunction []

[2026.04.15-03.54.25:348][252]LogOutputDevice: Error: [Callstack] 0x0000000000000000 UnknownFunction []

[2026.04.15-03.54.25:348][252]LogOutputDevice: Error:

swift horizon
daring portal
modest shell
#

so my crashes happen when somebody is connecting to the server and were doing a battle over sea

spring hamlet
#

My server is having the same issue

daring portal
#

Seeing similar issues. @modest shell Are you using our container? We released an update today that should help with stability

modest shell
static egret
bronze horizon
# modest shell hey where can i report server crashes? i have these logs: [2026.04.15-03.54.25:3...

It's likely the few lines above this that will outline the real issue if it was caught before the crash.

If you're using Windrose Dedicated on a Linux box you're likely to get into a networking assert error eventually([b]ASSERTION FAILED: result.bytes_transferred == buffer_->Length()[/b]), upgrade wine to at least 9.18 to fix it.

Here's the bug report and resolution:
Google: winehq show_bug 10648

And how to update to the latest by skipping your distro's version, at least a guide I used. Note, make /sure/ you get rid of all pieces parts of wine from your distro before upgrading.
Google: gitlab winehq debian-ubuntu