6 min read Beginner Updated: Agrar Chaoten Team

Short answer

Where do I find the FS25 server log?

On the server in the web interface log viewer or as log.txt via FTP. Locally under C:\Users\YOUR-NAME\Documents\My Games\FarmingSimulator2025\log.txt

Reading the server log — overview

The log.txt is your most important tool for every FS25 problem. Whether it's a crash, a missing mod, a dropped connection or a LUA error — the cause is almost always in the log. In this guide you'll learn where to find the log, how it's structured and how to spot the relevant entry in seconds.

Remember: 90% of "my server doesn't work" cases can be solved just by looking at the log. You don't have to be a programmer — you just need to know what to look for.

Where do I find the log?

  • On the server: The web interface usually has a built-in log viewer. Alternatively, the log.txt sits in the server directory, accessible via FTP.
  • Locally (singleplayer/client): Under C:\Users\YOUR-NAME\Documents\My Games\FarmingSimulator2025\log.txt

Important: The log is overwritten on every start. If an error occurs, back up the log.txt before restarting the server — otherwise the entry is gone.

Structure of the log

The log reads chronologically from top to bottom: first the game start, then mod loading, then regular operation. Every line has a type:

Info: ... → normal status message, no problem Warning: ... → notice, usually harmless Warning (perf): → performance notice, rarely critical Error: ... → a real problem — look here!

Understanding the most important lines

  • Error: Running LUA method ... + "LUA call stack": Script error from a mod. The path names the culprit (see the separate LUA error guide).
  • Error: Can't load resource / file not found: A file is missing or corrupted — usually a mod that wasn't fully uploaded.
  • Warning: ... has invalid ...: A mod or the config contains an invalid value. Often tolerable, but it can break features.
  • Missing mod / mod not found: The savegame needs a mod that's missing on the server — install it before starting.

Finding errors quickly

1

Search for "Error"

Open the log and press Ctrl+F. Search for Error. Jump through every hit — errors are the real problems.

2

Search for "LUA call stack"

This term takes you straight to mod script errors, including the mod name in the path.

3

Check the end

After a crash, the cause is almost always in the last lines before the cutoff. Scroll all the way down.

Support tip: When asking in a forum or contacting your host's support, always attach the relevant log lines (or the whole log.txt). "It doesn't work" without a log just wastes everyone's time — with a log, the cause is often clear within minutes.

Practical tips

Before/after comparison: Something stopped working after a change? Compare the log from before and after — the new error entry shows what the change broke.

Learn to ignore warnings: Many Warning lines are normal and show up even on perfectly running servers. Focus on Error.

Frequently asked questions (FAQ)

Frequently asked questions

Where do I find the FS25 server log?
On the server in the web interface log viewer or as log.txt via FTP. Locally under C:\Users\YOUR-NAME\Documents\My Games\FarmingSimulator2025\log.txt
What's the difference between Warning and Error?
Warning lines are usually harmless and show up even on healthy servers. Error lines — especially with 'LUA call stack' — point to real problems.
Why is my log empty after a restart?
The log gets overwritten on every start. Save the log.txt before restarting after an error.
What should I search for in the log?
Use Ctrl+F to search for 'Error' and 'LUA call stack'. For crashes, the causes are usually in the last lines.

Questions about this guide?

Stuck on a step? Get in touch – we're happy to help.

Discord Ticket Contact form E-Mail

Last updated: 2026-06-21 · Written by the Agrar Chaoten team