Why am I seeing a "503 Worker Machine Not Running" error in WebDirect?

This error means the Web Publishing Engine (WPE) — the component that powers WebDirect — has stopped responding. It is the most common WebDirect issue and is almost always resolved with a quick restart.

Why does this happen?

The WPE is the most sensitive component in FileMaker Server. It can stop under memory pressure, after prolonged uptime, or during periods of heavy usage. This is a known FileMaker Server behavior, particularly in older versions.

How to fix it

Option 1 — From your FMPHost dashboard:
Log in to your FMPHost account. A WPE restart is available directly from the dashboard without needing to access the Admin Console.

Option 2 — From the Admin Console:

  1. Log in to your FileMaker Server Admin Console at https://your-hostname.fmphost.com:16000/admin-console
  2. Go to Web Publishing > Overview
  3. Click Stop, wait a few seconds, then click Start on the Web Publishing Engine

WebDirect should be back online within 30–60 seconds of the restart completing.

If it keeps happening

Occasional WPE restarts are normal. If you are seeing crashes multiple times per day or week, there is likely an underlying resource issue (memory pressure, large concurrent session count, or a specific operation stressing the engine). Open a support ticket and we will review your server logs to find and fix the root cause.

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

How do I enable WebDirect on my server?

WebDirect lets your users open FileMaker databases directly in a web browser with no FileMaker...

WebDirect works sometimes but not always — what is happening?

Intermittent WebDirect issues are frustrating, but they almost always have a specific cause. Here...