- use dig to check name resolution. nslookup isn't using the OS resolver libraries, it's using its own internal ones.
- the name resolution inside a systemd unit is not necessarily the same as directly from the shell
- you need to check dns resolution in the vm trying to run Factorio, not on the ...

Can you show the full log? journalctl -u factorio.service




Looking there I see:
Error HttpSharedState.cpp:175: CURL failed: code:6, 6; Could not resolve host: auth.factorio.com

Error ServerMultiplayerManager.cpp:84: MultiplayerManager failed: Failed to reach auth server. Code: 520. Error ...

Yeah, looks like you are trying to run your server publicly available, which is the default configuration. That's why game is trying to connect to the host in the first place. If you did not want that, you can disable it in server configuration file (check what flags you need to provide it at ...

Found a related post with a solution. Check it out https://forums.factorio.com/90221


unfortunately it was already enabled, running, and functional


factorio@factorio002:~$ resolvectl query mods.factorio.com
mods.factorio.com: 104.26.14.88 -- link: eth0
172.67.71.197 -- link: eth0
104.26.15 ...

Can you show the full log? journalctl -u factorio.service


Jan 12 00:04:42 factorio002 systemd[1]: Started factorio.service - Factorio Server.
Jan 12 00:04:42 factorio002 factorio[397]: 0.000 2025-01-12 00:04:42; Factorio 2.0.28 (build 81088, linux64, headless, space-age)
Jan 12 00:04:42 ...

Hello,

I am running a headless factorio server on version 2.0.38 (and prior versions) and the factorio server will randomly stop responding. The server is running on a Debian 12 VM on a proxmox host running version 8.3.2.

from systemctl i see:

factorio@factorio002:~$ sudo systemctl status ...