Just now, Mainfrezzer said:

The log shows that the server has been running for over 1 hour and 45 minutes at that point. You should see it in the LAN section ingame, usually. The online list is, not the best, to put it in the most neutral way.

If you wanna make it externally available, you need to setup port forwarding for 7777/udp, 7778/udp, 27015/udp


But to "quickly" find them, its easier to use the steam server browser and add them with ServerIP:27015 in that case

I have setup the port forwarding, because I want to play with friends. I have the epicgames version of the game, so I think I don't have the "Steam server browser". Also, where is the "Lan-section"?

Just now, KimiLen said:

I have setup the port forwarding, because I want to play with friends. I have the epicgames version of the game, so I think I don't have the "Steam server browser". Also, where is the "Lan-section"?

Ohh Epic, well. That requires some more game parameter

you need to set -PublicIPForEpic=The-Public-IP -crossplay -UseVivox in Extra Game Parameters:

I reinstalled everything now. Before I restart the docker to add the extra parameters you mentioned, does the end of this docker log mean, that the installation has finished successfully or do I have to wait still?
docker.log

Edited January 22Jan 22 by KimiLen

It works! It really were just the extra Game Parameters for me. I think the "FPlatformMisc::RequestExit(1)" was just me closing the docker, but it showed up even after restarting. I don't know, it's weird, if I look at te log, it looks like it would start and then instantly close, but maybe it's just the log of the last try? Idk. But it works, that's all that matters. Thank you! Maybe you could put the Extra Parameters for Epic-Users somewhere, so they are easier to find.

Edited January 22Jan 22 by KimiLen

Looking for help with my Panel install. Everything is secured via SSL and routed through NPM and Cloudflare and has been working without isssue for the better part of the year. I don't tinker with things once they are setup and working. The last two panel updates have completely broken my panel page resulting in mixed media/broken css on the panel page without any changes to my config. Panel Beta 30 was when this first happened and after a while I was able to fix it by running the below commands:

php artisan config:clear

php artisan view:clear

I updated my panel again to 31 a few days ago and forgot to check if the issue happened until just now and the page is broken again. The above commands are not working either. Any ideas would be helpful

edit: also want to mention that I've done the basic troubleshooting, clearing cache/cookies for the site, restarting containers for NPM, Panel and Wings.

Edited January 24Jan 24 by Kazem

56 minutes ago, Kazem said:

Looking for help with my Panel install. Everything is secured via SSL and routed through NPM and Cloudflare and has been working without isssue for the better part of the year. I don't tinker with things once they are setup and working. The last two panel updates have completely broken my panel page resulting in mixed media/broken css on the panel page without any changes to my config. Panel Beta 30 was when this first happened and after a while I was able to fix it by running the below commands:

php artisan config:clear

php artisan view:clear

I updated my panel again to 31 a few days ago and forgot to check if the issue happened until just now and the page is broken again. The above commands are not working either. Any ideas would be helpful

edit: also want to mention that I've done the basic troubleshooting, clearing cache/cookies for the site, restarting containers for NPM, Panel and Wings.

check the app url in the .env file if its really https

https://forums.unraid.net/topic/182778-support-mainfrezzer-docker-repo/page/11/#findComment-1602875

check the app url in the .env file if its really https

https://forums.unraid.net/topic/182778-support-mainfrezzer-docker-repo/page/11/#findComment-1602875

Thanks, that helps point in the right direction. The .env file has an internal address. Any speculation on why this would change after the last two updates, and more specifically why just running the commands I mentioned fixed it last time but not this time?

8 minutes ago, Kazem said:

Thanks, that helps point in the right direction. The .env file has an internal address. Any speculation on why this would change after the last two updates, and more specifically why just running the commands I mentioned fixed it last time but not this time?

because they changed how the panel loads variables a bit 2 patches ago. if you change the address from the ip address to the app url in your template, it should work again. How running the artisan commands circumvented that in the past, no clue.

because they changed how the panel loads variables a bit 2 patches ago. if you change the address from the ip address to the app url in your template, it should work again. How running the artisan commands circumvented that in the past, no clue.

Can confirm, one I changed the URL to the correct one in the .env file my panel is working again. Thank you so much for the assistance!

Would need some help regarding the name of the server images being created on Unraid. I recently setup a Hytale server which is running fine, however when looking at its image in Unraid, I can see that its name corresponds to the Server UUID field of the server.

Looking at the Environment Configuration of the server, I saw a "Container Labels" section under Docker Settings, thinking that it would be for changing the default UUID name, however it didn't do anything.

I also tried the same thing with the "Image Name" field to no avail (both in the Server and the Egg itself). Is there another way to go about this ? Did I miss a step ? Or is this simply not possible ?

Thanks in advance for any help provided.

Edited January 31Jan 31 by Altraum

18 hours ago, Altraum said:

Would need some help regarding the name of the server images being created on Unraid. I recently setup a Hytale server which is running fine, however when looking at its image in Unraid, I can see that its name corresponds to the Server UUID field of the server.

Looking at the Environment Configuration of the server, I saw a "Container Labels" section under Docker Settings, thinking that it would be for changing the default UUID name, however it didn't do anything.

I also tried the same thing with the "Image Name" field to no avail (both in the Server and the Egg itself). Is there another way to go about this ? Did I miss a step ? Or is this simply not possible ?

Thanks in advance for any help provided.

Im pretty sure its not possible, as wings uses the generated docker uuid

I've installed GPTWOL, but when I try to access the webGUI, nothing loads. The log doesn't show any errors. It is set to run as network type: host.

[2026-04-14 10:32:01 -0400] [9] [INFO] Starting gunicorn 25.1.0

[2026-04-14 10:32:01 -0400] [9] [INFO] Listening at: http://0.0.0.0:5000 (9)

[2026-04-14 10:32:01 -0400] [9] [INFO] Using worker: sync

[2026-04-14 10:32:01 -0400] [9] [INFO] Control socket listening at /app/gunicorn.ctl

Launching GPTWOL...

it should be availabe at your unraid-ip:5000 then. Although there is a docker bug that has sneaked in, if youre using the beta version, that lets you start container whichs ports are already unavailable.

I just had a look at it and it work as one would expect.

Although one thing to keep in mind, since the container runs as host, if you change the port its running on, the webui button will still send you to port 5000

I got a bit tripped up when installing Pelican, I think it's possible that they've changed the config structure, leading to errors

In the UnRaid instructions it says in the config.yml

The line under system:

passwd_file: cange it to /tmp/pelican/passwd

Now it's a slightly different layout (or I just didn't understand the instructions) but there are two blocks to update, I set both to false and that fixed it:

passwd:

enable: false

directory: /etc/pelican

You can also set the above from /etc/pelican --> /tmp/pelican

And below from /etc/pelican/machine-id --> /tmp/pelican/machine-id

machine_id:

enable: false

directory: /etc/pelican/machine-id

I'm not sure if this will have any impact, but at least the server launches now.

I haven't actually tried to connect from a client yet, but my network setup is a bit quirky and it tripped me up as well. Once I confirm everythings working I'll try to remember to share.

23 minutes ago, Chunks said:

I got a bit tripped up when installing Pelican, I think it's possible that they've changed the config structure, leading to errors

In the UnRaid instructions it says in the config.yml

Now it's a slightly different layout (or I just didn't understand the instructions) but there are two blocks to update, I set both to false and that fixed it:

You can also set the above from /etc/pelican --> /tmp/pelican

And below from /etc/pelican/machine-id --> /tmp/pelican/machine-id

I'm not sure if this will have any impact, but at least the server launches now.

I haven't actually tried to connect from a client yet, but my network setup is a bit quirky and it tripped me up as well. Once I confirm everythings working I'll try to remember to share.

ah yeah, good that you remind me. I did handle that in my image but didnt update it in the "official" image. although im not sure yet if i update that part yet as they wanted to publish their image themselves

Just in case somebody happens to upgrade to 7.3.1 and experiences some funkyness with the ark container. Im aware of it looping. Im not absolutely certain as to why but i think i narrowed it down.

I currently have a testbuild under the tag :test available. (includes a bump to wine11)
Edit;
Should be sorted via regular update

Edited June 2Jun 2 by Mainfrezzer

For anyone updating to the newest release of the pelican panel (as of the 22nd of june, beta35). you need to add a new mapping to your template to include plugins now

https://github.com/Mainfrezzer/UnRaid-Templates/commit/310b40843ba29f1dbe4b179aefa6b7c8a54676ee

Edited June 22Jun 22 by Mainfrezzer
I think I had a stroke while typing. Fixed lol