Instance failes to resolve hostname after crash

So, yesterday my physical server crashed, after resolving this issue and everything was running again, i started up AMP and the V-Rising instance, everything running on Linux. V-Rising requieres wine and therefor runs in docker. Since that crash, when i first click on start the startup process tries to connect to steam via the steamcmd. That fails with this error:

09:03:38 Connecting anonymously to Steam Public...Retrying. . .
09:04:40 Retrying. . .

When i trie to restart the server it beginns to Bootloop with the following final error (this time it skips the SteamCMD step and tries to start V-Rising:

00007A51AEFB6850: request failed, libcurl error: 6 (Couldn't resolve host name)6EOS -
SteamCMD Log

SteamCMD09:02:25
Redirecting stderr to ‘/home/amp/Steam/logs/stderr.txt’
Logging directory: ‘/home/amp/Steam/logs’
Looks like steam didn’t shutdown cleanly, scheduling immediate update check
[ 0%] Checking for available updates…
09:02:36
[----] Verifying installation…
09:02:37
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1714855729
– type ‘quit’ to exit –
Loading Steam API…OK
force_install_dir “1829350”
09:03:38
Connecting anonymously to Steam Public…Retrying. . .
09:04:40
Retrying. . .
09:05:23
Retrying. . .

V-Rising-Log

Console09:06:25

[Server] Startup Completed - Disabling Scene Loading Systems
[Server] Shutting down Asynchronous Streaming
Registered WarEventMapNode in Chunk: 16,14
Registered WarEventMapNode in Chunk: 16,15
Registered WarEventMapNode in Chunk: 15,16
Registered WarEventMapNode in Chunk: 18,16
Registered WarEventMapNode in Chunk: 16,17
Registered WarEventMapNode in Chunk: 17,17
Registered WarEventMapNode in Chunk: 15,18
09:07:45
Unity.Entities.SystemBase:Update()
Unity.Entities.ComponentSystemGroup:UpdateAllSystems()
Unity.Entities.InitializationSystemGroup:OnUpdate()
Unity.Entities.SystemBase:Update()
00007A51AEFB6850: request failed, libcurl error: 6 (Couldn’t resolve host name)6EOS -
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogWarning(Object)
ProjectM.EOS.EosImpl:LogCallback(LogMessage&)
Epic.OnlineServices.Bindings:EOS_Platform_Tick(IntPtr)
Unity.Entities.SystemBase:Update()
Unity.Entities.ComponentSystemGroup:UpdateAllSystems()
Unity.Entities.InitializationSystemGroup:OnUpdate()
Unity.Entities.SystemBase:Update()
00007A51AEFB6850: libcurl info message cache 0 (Could not resolve host: api.epicgames.dev)6EOS -
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogWarning(Object)
ProjectM.EOS.EosImpl:LogCallback(LogMessage&)
Epic.OnlineServices.Bindings:EOS_Platform_Tick(IntPtr)
Unity.Entities.SystemBase:Update()
Unity.Entities.ComponentSystemGroup:UpdateAllSystems()
Unity.Entities.InitializationSystemGroup:OnUpdate()
Unity.Entities.SystemBase:Update()
00007A51AEFB6850: libcurl info message cache 1 (Closing connection 0)6EOS -
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogWarning(Object)
ProjectM.EOS.EosImpl:LogCallback(LogMessage&)
Epic.OnlineServices.Bindings:EOS_Platform_Tick(IntPtr)
Unity.Entities.SystemBase:Update()
Unity.Entities.ComponentSystemGroup:UpdateAllSystems()
Unity.Entities.InitializationSystemGroup:OnUpdate()
Unity.Entities.SystemBase:Update()
Retry exhausted on https://api.epicgames.dev/sdk/v1/default?platformId=WIN6EOS -
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogWarning(Object)
ProjectM.EOS.EosImpl:LogCallback(LogMessage&)
Epic.OnlineServices.Bindings:EOS_Platform_Tick(IntPtr)
Unity.Entities.SystemBase:Update()
Unity.Entities.ComponentSystemGroup:UpdateAllSystems()
Unity.Entities.InitializationSystemGroup:OnUpdate()
Unity.Entities.SystemBase:Update()
Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak
To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations.
09:07:54
Curl error 6: Could not resolve host: cdp.cloud.unity3d.com

Looks like you have network issues

yep, already fixed it, forgot to clarify that here, i´m sorry, Issue was on the physical server, wrong network internal dns server was used