Connectivity Problem with American Truck Simulator - ATS is not listening on port 27015

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Phobos’ v2.6.0.6 (Mainline)
Virtualization QEMU_KVM
Application American Truck Simulator
Module GenericModule
Running in Container No
Current State Ready

Problem Description

Issue

After starting American Truck Simulator, the server appears to start up just fine, however I notice that it errors out attempting to listen on port 27015. Checking the server, it doesn’t appear to be listening on either 27015 or 27016

Reproduction Steps

  • Stopped and started the instance
  • Rebooted the entire server
  • Changed the port number
  • Toggled the firewall option on/off
  • Checked to see whether the port was listening locally via netstat -ant (don’t see either 27015 or 27016 listening. I do however see that 2224 (SFTP) and 8081 (Webserver) are listening.

Used nmap to try and connect to the ports:

❯ sudo nmap -sU -p 27016 192.168.XXX.209
Starting Nmap 7.95 ( https://nmap.org ) at 2024-11-25 21:39 EST
Nmap scan report for amp (192.168.XXX.209)
Host is up (0.0070s latency).

PORT STATE SERVICE
27016/udp open|filtered unknown

Nmap done: 1 IP address (1 host up) scanned in 0.32 seconds
❯ sudo nmap -sU -p 27015 192.168.XXX.209
Starting Nmap 7.95 ( https://nmap.org ) at 2024-11-25 21:41 EST
Nmap scan report for amp (192.168.XXX.209)
Host is up (0.0077s latency).

PORT STATE SERVICE
27015/udp closed halflife

Nmap done: 1 IP address (1 host up) scanned in 0.10 seconds

Manually spun up a listener on port 27015 using netcat. Confirmed that I could connect remotely to that port and send a string to it with the following commands:
nc -u -l -p 27015
echo “test” | nc -u 192.168.XXX.209 27015

Any help is much appreciated.

I also seem to be having this same exact issue.

I ended up just rolling a M$ Windows VM to install and host the ATS server. Definitely not my preference and don’t consider it an acceptable resolution, but one I’m willing to live with in the short term.

FWIW I had the same issue spanning multiple Linux distros whether using amp, linuxgsm or nothing at all.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.