Garry's Mod Workshop Download Troubleshooting
When a player sees “ERROR” models, missing materials, or a join that stops during download, first identify which layer failed. The server collection, client Workshop cache, and custom content delivery are separate. A reinstall rarely fixes a collection that is private or a server that never tells the client about its content.
Last verified: September 1, 2026. Facepunch's Workshop guide covers collection startup; its content-serving guide distinguishes WorkshopDL, FastDL, legacy ServerDL, and Lua delivery.
Symptom-to-layer map
| Symptom | Likely layer | First check |
|---|---|---|
| Server starts without the collection | Server Workshop fetch | Collection is public/unlisted and the ID is passed with +host_workshop_collection. |
| Client stuck at downloading | Client delivery/cache | Test one clean client and inspect the server console for the requested content. |
| “ERROR” models or purple textures | Missing mounted/custom content | Check the addon documentation and whether resource.AddWorkshop or FastDL is required. |
| Join works with flags disabled | Addon or Workshop conflict | Re-enable the collection one item at a time and keep the last known-good ID. |
1. Check the collection
- Open the collection in Steam Workshop and confirm it is public or unlisted.
- Copy the numeric collection ID from the URL, not an individual addon ID.
- Start the server with:
./srcds_run -game garrysmod -console \
+host_workshop_collection COLLECTION_ID \
+gamemode sandbox +map gm_constructRead the startup console for fetch, dependency, or permission errors. The server installs/updates the collection at startup; it does not make a private collection public for you.
2. Separate server files from client delivery
Facepunch documents WorkshopDL as the preferred fast path for Workshop content. For a custom addon that requires Lua, follow its current instructions and use resource.AddWorkshop in a server-side autorun file. FastDL requires a correctly configured HTTP server. Legacy ServerDL is slow and should generally be avoided.
Do not add sv_allowdownload, net_maxfilesize, or arbitrary paths as a universal fix. Those settings do not replace a missing Workshop collection or a bad content manifest.
3. Isolate one variable
- Start with a stock map and
-noaddons -noworkshop. - Confirm a clean client can connect.
- Enable the Workshop collection, restart, and test again.
- Remove or update only the addon that changes the result; keep the last known-good collection manifest.
4. Client-side checks
- Let the Workshop download finish before joining again; do not launch multiple stale server sessions.
- Verify the client is subscribed to the collection when the addon author requires client subscription.
- Test a second client profile or a clean machine to distinguish a local cache issue from server delivery.
- Record the missing Workshop ID, map, gamemode, and the exact console error.
A recent community report describes specific addons refusing to download after previously working. Treat it as a useful symptom pattern, then use the official delivery paths above to identify whether the server or client is failing.
Related Garry's Mod guides
- Workshop collections and addons
- Dedicated-server setup
- Configuration and isolation flags
- Connection troubleshooting
- Server cost and sizing
Need collection updates, disk space, and backups handled for you? Use managed Garry's Mod hosting.