2 hours ago, ich777 said:

So the issue is solved now?

Yup! I was just backing up the save files which took forever to transfer through Windows, I removed the entry for the RCON because I don't use it and now everything works correctly. Sorry for the confusion

1 hour ago, FrozenGamer said:

Ark survival evolved server will not show on the internet.

First of all I would try to connect through the Steam Server browser if you can see the game, please do the following:

Open up Steam and click on "View" -> "Server":

 

Then click on "Favorites" and in the bottom right on "Add Server":

 

In the next dialogue enter UNRAIDIP:27015 (of course please replace "UNRAIDIP" with the IP from your unRAID server) and on "Add to Favorites":

 

After you have done that you have to click one more time the "Refresh" button in the lower right corner and you should hopefully see your server.

 

If you see your server you can go to the next step and try the exact same thing as mentioned above with the only difference that you have to enter your Public IP instead of you unRAID IP.

 

1 hour ago, FrozenGamer said:

I also changed the following setting in my router "Respond to Ping on Internet Port" to enable it.

Please disable this immediately, this will change nothing and should not be enabled anyways!

 

1 hour ago, FrozenGamer said:

or data that i might provide to help see what's going on?

Your server is running just fine but there is somewhere a miss configuration or another little thing that prevents your server from showing up in the list but keep in mind that this doesn't mean that it isn't reachable from outside your network.

 

1 hour ago, FrozenGamer said:

I tried Bridged and Host network, but not sure how to try the specific IP:br0 option.

Set it back to what it was, if Valheim works this container will also work if you've forwarded the ports properly.

1 hour ago, FrozenGamer said:

I am at a loss as to why my single (not cluster) Ark survival evolved server will not show on the internet.

I will reiterate and add a few things from my previous post which starts here. 

To be clear i am asking about Ark, but reference Valheim as it has been working fine.

 

Valheim container is working and has always worked from external connections. Yet Ark just won't be seen or connect via external connections, just on my local network. Every other game server i have used from this repository/thread works perfectly.  I understand port forwarding on my router

 

At this point,  I have the following ports mapped on my router 7777,7778,27015 udp only, 27020 tcip.

Testing with a cell phone tethered laptop, I am able to connect to valheim which uses udp ports via typing the IP address in   But i do not see my valheim server in the steam server favorites.  I tried 2 udp port scanners. one has an error writing to my port on all udp ports i tried to test, 2456 etc for valheim, and 27015 for the following udp port scanner. https://openport.net/udp-port-checker/ (this one doesn't work)

But https://www.ipvoid.com/udp-port-scan/ does connect to all the udp ports as open/filtered.  it lists the service for 7777 as cbt, 7778 as interwise, and 27015 as halflife.

 

I was asked the following question from Ich777

Are you sure that your ISP is not blocking any ports or you are behind a NAT from your ISP? -I have called my isp to ask if they are blocking udp ports or specific udp ports. They said they don't block much, just a few russian military IP's that have been trying to hack them.  Also I don't believe they are because if i can connect to valheim externally and the above port scanner shows all the ports as open/filtered. 

 

I cannot see my server at https://arkbrowser.com/ 

I cannot seem to find it when i download all the servers with the boxes checked on my compute (this one is on the same network as unraid/ark server)

I cannot see the game via tethered laptop and the ark server browser.

 

Do you have other services exposed to the internet? - i have many computers on the network and i have a few other services exposed for sure, but none on 27015 to the best of my knowledge.. Or 7777,7778 (if that matters or should i forget about those ports for my connection issue?). 

 

Any more suggestions? or data that i might provide to help see what's going on?

I would make sure you know what ports are currently open and what service is attached to them. Don't open ports for things you don't intend to use/connect to externally. If you're not using RCON you shouldn't have to open port 27020. As an example for the RCON I'm hosting a Left 4 Dead 2 server, but I don't use the RCON externally. If I need to use it I would remote into the Unraid machine and send it RCON commands through the terminal, so the only port that needs to be exposed is the SSH connection to the machine. 27015 is common for steam services and I believe its used to broadcast the connection to the server on steam, but shouldn't break it if it isn't configured right. 7777 looks like the main gameport, so I would start your troubleshooting there. Hopefully my two cents helps more than hurting

1 hour ago, ich777 said:

If you see your server you can go to the next step and try the exact same thing as mentioned above with the only difference that you have to enter your Public IP instead of you unRAID IP.

I can see it at 192.168.1.154:7777 only - and i can connect. Not on external Ip:27015, internal ip:7777, internal ip:27015 or any other combination.

 

1 hour ago, ich777 said:

Please disable this immediately, this will change nothing and should not be enabled anyways!

fixed- thank your for letting me know it is not necessary.

 

1 hour ago, ich777 said:

Set it back to what it was, if Valheim works this container will also work if you've forwarded the ports properly.

 

Back to bridged.

 

In addition i shut down and rebooted the unraid server, with all other dockers and my one VM set to not autorun. This did not seem to help. I tried Privileged, that didn't solve it.

Also i eliminated the RCon port as suggested by Mushroom.

 

 

17 hours ago, FrozenGamer said:

I can see it at 192.168.1.154:7777 only - and i can connect. Not on external Ip:27015, internal ip:7777, internal ip:27015 or any other combination.

Sounds like your port 7777 isn't configured correctly somewhere, preventing external connections.

Hi, 

 

I did a search on here for the term "Wreckfest" but could not find any relevant hits. 

I saw that you have created a Wreckfest container. This is awesome! I was running a VM specifically for this game, but a Docker would be much better. 

 

Anyway, I am having issues getting a server to run on different ports. 

 

I downloaded the container and gave it a different name:

Then I copied the server.config from my VM to the container. None of the ports have changed for this server. It starts and I can connect in game to this server. Everything works fine. 

 

But I also want to run a second server with a few added track mods. I got that to work on the VM but not the container. 

Here is the second container:

 

I have changed the server.config accordingly;

 

This server does not seem to come online. I can't find it in game. Not online and not in the lan section. 

Both servers use the same ports (that are forwarded) as the servers running in the VM. 

I tried only running the modded server only, but it doesn't come online. 

 

Do you know why a server with changed ports won't come online?

 

Keep up the good work! I love your containers. 

4 minutes ago, workermaster said:

Hi, 

 

I did a search on here for the term "Wreckfest" but could not find any relevant hits. 

I saw that you have created a Wreckfest container. This is awesome! I was running a VM specifically for this game, but a Docker would be much better. 

 

Anyway, I am having issues getting a server to run on different ports. 

 

I downloaded the container and gave it a different name:

Then I copied the server.config from my VM to the container. None of the ports have changed for this server. It starts and I can connect in game to this server. Everything works fine. 

 

But I also want to run a second server with a few added track mods. I got that to work on the VM but not the container. 

Here is the second container:

 

I have changed the server.config accordingly;

 

This server does not seem to come online. I can't find it in game. Not online and not in the lan section. 

Both servers use the same ports (that are forwarded) as the servers running in the VM. 

I tried only running the modded server only, but it doesn't come online. 

 

Do you know why a server with changed ports won't come online?

 

Keep up the good work! I love your containers. 

I think that when you change the UDP port you have to delete the entry and make a new UDP port with the new port number.

25 minutes ago, Minimushroomman said:

I think that when you change the UDP port you have to delete the entry and make a new UDP port with the new port number.

That's it! I thought that I only needed to change the port, but you have to delete the whole line and then add it again. I assumed that deleting the entry meant that I had to delete the port that was already there and just put another port in there. 

 

Both servers now show up in LAN. Not online. I will try a few things and see if I can get it working. Most likely something wrong with the ports. I also can't connect to the modded server because it keeps telling me that it is a different version, but I had the same issues in the VM. I will ask for help again if I can't get it working. 

I just tested a few more things. The non modded server is online and can be played on. 

The modded one only works when I disable the mods and rename the mod folder. Just disableing the mods in the server.config does not work since Wreckfest keeps telling me that there are still mods active. 

 

Could it be that mods are not working because the container is in beta?

 

Here is a screenshot that shows where the mod folder is placed, how it is named, that mods are turned off in the server.config and that the game still says that the server has active mods;

 

Turning on the mods in the server.config and trying to connect;

 

Both the mods folder and server.config are copied from the VM that hosted the servers before. I know this combination works. 

 

Edited January 14, 20224 yr by workermaster

4 hours ago, workermaster said:

That's it! I thought that I only needed to change the port, but you have to delete the whole line and then add it again.

Exactly like the description of the ports tells you to.

9 hours ago, workermaster said:

Could it be that mods are not working because the container is in beta?

I don't think so.

I'm not familiar with modding wreckfest servers, maybe there is another issue, maybe some mods are not compatible with WINE?

Amazing that you have Wreckfest added!
I previously ran this internally when we wanted to play so I would just load the game up and start a server. Because of this I already had all the ports forwarded.

 

All I have done is go through my rules and updated the IP to the Unraid server. I downloaded the Wrekfest docker and set up the server config. I have all the ports I previously had forwarded plus the ones the docker settings specify. Yet I am unable to find the server when I load up on my laptop and browse LAN servers. I can see the server is running as the logs say so and the webgui shows AI have joined:

 

 

The webgui also shows this though:

Repeated about 10 times, before it shows the AI joined.

 

Now, being a little on the stupid side can someone clarify something. My server is on port 192.0168.0.37 but the container shows another IP on the port mappings.

All my forwarding rule still point to the server, the server should move all that traffic to the 172 IP correct? 

 

Other than that I am at a loss as to what is wrong with the setup.

 

Surely even without all the port forwarding I should be able to at least see the server on LAN servers right?

1 hour ago, LFFPicard said:

Amazing that you have Wreckfest added!
I previously ran this internally when we wanted to play so I would just load the game up and start a server. Because of this I already had all the ports forwarded.

 

All I have done is go through my rules and updated the IP to the Unraid server. I downloaded the Wrekfest docker and set up the server config. I have all the ports I previously had forwarded plus the ones the docker settings specify. Yet I am unable to find the server when I load up on my laptop and browse LAN servers. I can see the server is running as the logs say so and the webgui shows AI have joined:

 

 

The webgui also shows this though:

Repeated about 10 times, before it shows the AI joined.

 

Now, being a little on the stupid side can someone clarify something. My server is on port 192.0168.0.37 but the container shows another IP on the port mappings.

All my forwarding rule still point to the server, the server should move all that traffic to the 172 IP correct? 

 

Other than that I am at a loss as to what is wrong with the setup.

 

Surely even without all the port forwarding I should be able to at least see the server on LAN servers right?

Have you forwarded the ports to the correct IP address?

I made that mistake once. Had the ports forwarded to my VM that hosted the servers before, but forgot to change the forwarding rules to the IP of Unraid itself. 

15 hours ago, ich777 said:

Exactly like the description of the ports tells you to.

I feel like an idiot but to my defense, I never had to do anything like that before and assumed that I had to do something else. I will never make that mistake again. 

 

I am now trying to get the mods to work. You suggested that some mods might not be compatible with WINE. I have managed to get 1 of my 6 mods to work and am now trying multiple things to get the others to work as well. Mods are a bit weird though. Sometimes the container suddenly downloads a lot of extra stuff or takes a long time to come online. I will report back here with my findings. 

1 hour ago, workermaster said:

I feel like an idiot but to my defense, I never had to do anything like that before and assumed that I had to do something else. I will never make that mistake again.

No worries!

Just saying...

 

1 hour ago, workermaster said:

Mods are a bit weird though. Sometimes the container suddenly downloads a lot of extra stuff or takes a long time to come online. I will report back here with my findings. 

I'm not really into mods...

But I apprechiate everything you post here that will help others.

 

My best guess is that some mods need Windows libraries that are not or at least not fully supported in WINE.

3 hours ago, LFFPicard said:

The webgui also shows this though

Nothing to worry about, his is just a warning from WINE qnd appeats on every instance from the container.

 

3 hours ago, LFFPicard said:

Now, being a little on the stupid side can someone clarify something. My server is on port 192.0168.0.37 but the container shows another IP on the port mappings.

This is the Docker network when the container is on bridge mode, also nothing to worry about.

 

3 hours ago, LFFPicard said:

Surely even without all the port forwarding I should be able to at least see the server on LAN servers right?

Yes.

 

3 hours ago, LFFPicard said:

Other than that I am at a loss as to what is wrong with the setup.

I would suggest that you start over again, delete the container, delete the wreckfest folder that is located in your appdata directory and pull a fresh copy from the CA App.

 

One question about your settings file, have you specified somewhere you LAN IP?

If yes, don't do that, always specify 0.0.0.0

On 12/30/2021 at 11:36 AM, icepik said:

Thanks ich777!  That was fast.  I'm seeing this now after following your instructions:

 

 

Not seeing any BepInEx in the output_log.txt in 7DaysToDie_Data folder either.  The screenshot above says it's hooking into UnityPlayer instead.  Is that possibly why?

 

 

 

*edit* - I am seeing some BepInEx in the log file...was just further into the log than I thought it would be :D.  Looks like it's working!  Thanks for the quick update on this!  You're awesome!

 

 

Would it be possible to get the container updated for 7dtd again so that when the BepInEx value = true it will call run_bepinex_server.sh instead of run_bepinex.sh ?  The mod author updated BepInEx to 5.4.18 for his mod and now it's not hooking it in before the server launches.

1 hour ago, icepik said:

it will call run_bepinex_server.sh instead of run_bepinex.sh

The container doesn't run run_bepinex_server.sh or run_bepinex.sh anyways, it runs the required commands on start.

Can you please post your log?

4 hours ago, ich777 said:

No worries!

Just saying...

 

I'm not really into mods...

But I apprechiate everything you post here that will help others.

 

My best guess is that some mods need Windows libraries that are not or at least not fully supported in WINE.

I got everything working!

 

Took more time and effort than I want to admit, but that is not because of the Docker container, but because Wreckfest is picky about when it decides to work. 

 

I won't post all the troubleshooting I did that didn't work, but I tried reinstalling the container multiple times (sometimes it would find a mod and run fine after a reinstall where I didn't delete the old container), trying every mod just one at a time (got only 1 of my 6 mods to run, and when I disabled all mods, the server kept saying that mods were still active), tried a combination of the above, and eventually gave up. Then I wanted to just get the server running again and decided to boot the VM that I used to host the servers before I found your container. The modded server in the VM also wouldn't start.

 

That made me believe that the conainter not working, might just be Wreckfest itself being picky. I also thought that maybe there is something wrong with the mods themselves. I download the mods again in Steam and then copied them to the container. Still no working server. 

 

I then rebooted the container by shutting it down first. Still nothing. Then I tried restarting the container and that worked! I had something similar with the VM once, where rebooting the Wreckfest server with a command would work, but not by shutting it down first. 

 

So now the server is running. I am not 100% sure what fixed it, but everytime I reboot it, it works. 

 

 

To anyone wanting to run mods on this container;

1. Download the container
2. Run the container and let it run for a few minutes. It will download some data. I found that if the CPU usage is higher than 1%, then it is busy doing something. Just wait. 
3. While you wait, you should forward the ports that you need. The ports are by default 27015-27016 and 33540. The protocol used is UDP but you could set it to "both". 
4. Stop the container
5. Create a mods folder in the Wreckfest container. The container is located in you appdata share. Name the mods folder "mods" 
6. Find a mod you like on the Steam workshop
7. Subscribe to that mod and let Steam download it
8. (Optional) play with that mod in your game to see if you still like it. 
9. Navigate to your Steam workshop folder. Default in Windows is at; C:\Program Files (x86)\Steam\steamapps\workshop\content. I am not sure if the folders in there are the same for everybody, but my Wreckfest mods are in the folder called "228380"
10. Copy the mods that you want on the server from this folder to your mods folder in the Wreckfest container(those folders also consist of number, but if you open one, there tends to be an image in there that shows you what mod it is.
    What it looks like; 
    
    Identifying a mod by looking at the image in the workshop mod folder and comparing it to Steam:
    
11. (Optional) rename the mod folder in the container. I shorted mine to just a few letters. "The very track pack" becomes "tvtp" etc;
    
12. Go to the root directory of the container and open the server_config
13. Scroll down until you the mods section
14. Remove the "#" and put the names of the mods you want to run on your server there:
    
15. Save the changes to this file and close it
16. Start the container. Wait a few minutes. Basically repeat step 2
17. Start the game.
18. Enable the mods you have running on your server in the game as well
19. Restart the game
20. Navigate to the multiplayer section
21. Select "Server browser"
22. Search for the server. The fastest way to test if you can connect to it, would be to search for it in the LAN section
23. The server with mods should show up. If you can connect to it, then the server will show an image in color and a lock sign in the "Ping" column. If not then it will be a grey image and an X in the "Ping" column. 
24. If you can connect, then go to the next step. If not then restart the container by using the restart option, not stopping it first and then starting it again. This should get your server up and running 
    
25. Search for the server in the ONLINE section. Add it to your favorites to connect faster in te future.

    If your server does not show up in the LAN section in Wreckfest, then there is something wrong. Even wrong ports should show you a server here. If this happens, then I have no idea why. 

    If your server does shop up in the LAN section but not in the INTERNET section, then there is a problem with your ports. 

 

Note:

The containers show some information and errors in the Webui. I don't know why but it doesn't seem to be a problem. Maybe @ich777 can explain them: 

 

Please keep in mind that mods can be updated. If this happens, then your game will have the latest version, but the server will not. This can cause the message in game that tells you that the server and client data do not match. 

You could also try not renaming the mod folders and have a synchronisation program sync the workshop mod folders with the ones in the container. Then your mods will always be up to date. But this is not a valid option for everyone. 

 

Even with all of the above, keep in mind that Wreckfest can be very troublesome to run modded. This isn't the first time where I had a hard time getting it to run, and even a server that had been running for weeks just stopped working. But in the end, I am very happy to have this container. 

Edited January 15, 20224 yr by workermaster

4 hours ago, workermaster said:

Maybe @ich777 can explain them

These are warnings from WINE because there is no dbus in the container installed to keep the size as small as possible and also it isn't needed anyways  (this container is running using WINE and it isn't small in any way).

5 hours ago, ich777 said:

The container doesn't run run_bepinex_server.sh or run_bepinex.sh anyways, it runs the required commands on start.

Can you please post your log?

Here's my log below when I start the container.  The 7dtd server log doesn't show BepInEx getting loaded though when the server starts and the mods fail to load.

 

---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1639697740
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
---Update Server---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
[ 0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1639697740
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
Success! App '294420' already up to date.
---Prepare Server---
---SaveGameFolder location correct---
---Savegame location found---
---UserDataFolder location correct---
---UserDataFolder location found---
---BepInEx enabled!---
---BepInEx Version Check---

---https://github.com/BepInEx/BepInEx---

---BepInEx v5.4.18 up-to-date---
---Server ready---
---Start Server---
---with BepInEx---

---https://github.com/BepInEx/BepInEx---

Found UnityPlayer, hooking into it instead
Found path: /serverdata/serverfiles/7DaysToDieServer.x86_64

14 minutes ago, icepik said:

The 7dtd server log doesn't show BepInEx getting loaded

It does, this line tells you that BepInEx is loaded:

14 minutes ago, icepik said:

Found UnityPlayer, hooking into it instead

(and of course also the log tells you that it's loaded)

 

15 minutes ago, icepik said:

mods fail to load.

Which mods? Please remember if you use mods (like the Electricity Overhaul Mod) you have to also replace the default BepInEx that the container downloads with the ones from the mod itself.

 

I only ship the default BepInEx with this container because it's up to the user to replace this version with a custom version for 7DtD.

 

The main problem is that there is no custom BepInEx for 7DtD like it exists for Valheim, at least not one unified that everyone uses, when I added support for BepInEx I did this on purpose because I found already three different custom versions for BepInEx for 7DtD.

1 hour ago, ich777 said:

It does, this line tells you that BepInEx is loaded:

(and of course also the log tells you that it's loaded)

 

Which mods? Please remember if you use mods (like the Electricity Overhaul Mod) you have to also replace the default BepInEx that the container downloads with the ones from the mod itself.

 

I only ship the default BepInEx with this container because it's up to the user to replace this version with a custom version for 7DtD.

 

The main problem is that there is no custom BepInEx for 7DtD like it exists for Valheim, at least not one unified that everyone uses, when I added support for BepInEx I did this on purpose because I found already three different custom versions for BepInEx for 7DtD.

It's just one mod, Undead Legacy.  ul.subquake.com.  Here's what's included with the mod when you download it:

 

All the required files to run the server with Undead Legacy are included in the archive:

BepInEx

Mods

doorstop_libs

doorstop_config.ini

run_bepinex_server.sh (used to launch the server)

 

It works perfectly fine launching it with a full Linux distro when you launch the 7d2d server using run_bepinex_server.sh, just doesn't work from the docker instance.  The only thing I can think of is something in the that sh file is causing issues maybe.

 

 

10 hours ago, ich777 said:

I would suggest that you start over again, delete the container, delete the wreckfest folder that is located in your appdata directory and pull a fresh copy from the CA App.

 

One question about your settings file, have you specified somewhere you LAN IP?

If yes, don't do that, always specify 0.0.0.0

 

Right, deleted docker, went to CA Cleanup Appdata and deleted the Wrekfest folders. manually checked the folders were deleted.

 

Grabbed a fresh docker, no settings changed at all just grabbed it as it is. Checked log and waited for it to finish downloading. Webgui says it is connected to steam. Logs says server is started.

 

 

Still nothing. Banging my head a little so going to go to bed and try another fresh install tomorrow.

 

The server config file has no section about LAN IP so that has not been changed.

8 hours ago, icepik said:

It works perfectly fine launching it with a full Linux distro when you launch the 7d2d server using run_bepinex_server.sh, just doesn't work from the docker instance.  The only thing I can think of is something in the that sh file is causing issues maybe.

I found the cause of the issue and that is because this developer uses doorstep differntly from everything else and that is the issue, as said in my previous comments this is a nightmare if there is no unified build from BepInEx for 7DtD like it exists for Valheim.

 

The developer from the mod uses this DOORSTOP_CORLIB_OVERRIDE_PATH:

BepInEx/core

but I use this in my container:

${SERVER_DIR}/unstripped_corlib

 

 

Anyways, I've updated the container so that you can create a variable like this:

 

 

Please do the following:

1. Stop the container
2. Do a from the container on the Docker page
3. Edit the template
4. Add a variable with the Key: DOORSTOP_CORLIB_OVERRIDE_PATH and the Value: /serverdata/serverfiles/BepInEx/core
5. Click Apply