Skip to content

Deadlock: Common Issues

Find out how to troubleshoot and fix common Deadlock server issues for a smooth gaming experience → Learn more now

10 November 20266 min read0 Views0 helpful

Introduction

Setting up and running your own Deadlock game server can be really exciting and a lot of fun. It's a great way to build a custom gaming environment and community, but it also means taking responsibility when something goes wrong. Crashes, lag, and configuration issues are common challenges every server owner encounters at some point.

To spend less time troubleshooting and more time gaming, this section covers the most common issues server owners face and provides solutions to help you fix them quickly and effectively.

FAQ

Frequently asked questions

Your Deadlock server doesn't appear in an in-game server list. Connect directly through the console using connect [IP:Port] and the exact port shown in your server's Overview.
It's usually because of a Valve patch: a server running an outdated version shuts itself down, even if no one is playing. ZapX automatically restarts it with the new version as soon as it's available. You can check whether this was the cause in the Console and under Activity.
Check the Console and the log files in the Files tab. Common causes include incorrect entries in server.cfg, Additional Startup Parameters, or an invalid map (the default is dl_midtown). Try removing your custom entries and adding them back one at a time.

Feedback

Was this article helpful?

Your feedback helps us prioritize and improve content.

0 of 0 Users found this article helpful.

Personal support

Need more help than the guide provides?

Our ZAP support team knows your product — briefly describe your issue and we'll help you personally.