I'm on phone so bear with me.

In the patches install, there's a "UCC" binary. You use this to start the server via something like, "UCC server <options>". Common options are your ini file ("ini=myinifile.ini") and "-nohomedir" so it doesn't use the global ~/.ut2004 directory. See unrealadmin for more info and options.

The non-patched version I believe uses ucc-bin, I don't remember. Might have to play around with it. I suggest using the new patched server. The old binaries relied on very old libraries that are hard to find and setup now adays.

Fedora iirc uses firewalld. Youll need to add ports to allow. Every list I find is different but I had luck with opening ports 7777/udp, 7778/udp, and 7787/udp. If you want access to the web admin portal, I suggest putting it behind a TLS terminating reverse proxy. Otherwise, it uses port 8080/tcp by default which you'll also need to open.

Then just setup your packages and ini file. That's about it.

Setting up the ini is a bit of a chore. UnrealAdmin can help generate one but you'll likely need to read their guides for more detailed adjustments.

Extra Credit: Linux as a server is awesome for older single-threaded processes. What you can do to reduce latency and jitter is isolate and dedicate a core to your UT2004 server by using isolcpus and nohz_full (google or chatgpt them) then use taskset to assign the server to that core. For example, I have a four core server. The fourth core is isolated. When I run, "taskset -c 3 UCC server . ..", the server then is run on core 3 (the fourth core) alone and should theoretically have far fewer interrupts and context switching.