Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
Tue Nov 7 05:26:12 PM EST 2023
as requested, results from running 'data' on my host machine
Like it waits about 30 seconds and then spits out "Connection Timed Out", or does it almost immediately blurt out a long string that starts with "UNETConnection::Tick..."?
a delayed "Connection Timed Out" is genuine lack of being able to speak and for me it was my failing to properly enable port forwarding on my Router for UDP for the 7777 port to the host's internal IP.
That fast fail about UNETConnection is a mix of potential problems, for me its my router's lack of being able to correct redirect UDP traffic back into the network if its fired from within the network at the WAN IP that then tries to direct it back at my host via the port forwarding rules.
You can try running a Tcpdump on your host and then try to connect to the server through the ark client server browser, if you don't see any UDP attempts hitting it then you need to double check your router's port forwarding.
In the end due to my router and how we don't care about non-local people connecting I just opted to use the console 'open IP:Port' to reach the server until I replace my router at some point.
I'm going to try adding -NoBattlEye to the GameUserSettings.ini next
I didn't realize I had to re-initialize it with docker-compose up -d, I will try that now.
Understood, and thank you. I managed to get it running with the -NoBattlEye enabled and confirmed. I was unable to join the session directly (Connection Timed out) but I was able to join via direct IP.
TLDR, nothing changed.
Just let me know whether this is the IP you are using to connect or whether it's your local one.
You can verify that by going to that path where the volumes are stored. It should be: /var/lib/docker/volumes/ark-asa-server-deployment_server-files-1/_data
It sounds more like the server wasn't installed properly for some reason. Did you try to spin it up for the first time in its vanilla state, then shut it down and add the mods back again?
You can do a clean install by removing the volumes (careful, this deletes your server files + saved arks right away):
docker volume rm ark-survival-ascended-container_server-files-1
docker volume rm ark-survival-ascended-container_steamcmd-1
docker volume rm ark-survival-ascended-container_steam-1
And then run `docker-compose up -d` again. You might need to stop and delete the container though: `docker stop asa-server-1` and `docker-compose rm asa-server-1`.
I have some points/questions:
Why are you using iptables, when iptables is basically dead?
The installed iptables is just a wrapper/redirector for nftables and there shouldn't be even a need for persistency solutions :)
2nd: why are you installing it in /var/lib/docker/? Isn't it possible to define a specific path (for example on a SSD/NVME mount) ..where even root rights aren't needed?
3rd: is the natting really the only solution for multiple physical IPs? Is there no "simple" way, as it was with ASE, just to bind the IP address within the command line?