Network requirements for Kitchen Display
Most kitchens need nothing special here — a normal internet connection is enough. This page is for sites with a managed or restricted network, where a firewall or guest Wi-Fi only allows approved addresses.
What the Kitchen Display connects to
| What it is | Address | Port |
|---|---|---|
| Orders and status updates | api.myfoodfast.com | 443 (HTTPS) |
| Live order feed | api.myfoodfast.com | 443 (secure WebSocket) |
| The Kitchen Display web app | myfoodfast-kds.web.app | 443 (HTTPS) |
The live order feed uses a WebSocket connection that stays open all the time. Some business firewalls close long-running connections or block WebSockets outright. If yours does, ask for WebSocket traffic to api.myfoodfast.com to be allowed — without it, new orders will not appear until someone taps Refresh.
Note: If you use the Kitchen Display app installed on a Sunmi terminal, you only need the first two rows. The third row applies to the browser version.
If you are on an older Kitchen Display
Screens set up before September 2026 may still use the previous address, go.myorderboxhq.com. That address continues to work, so there is nothing you need to do. If your network allows only approved addresses, allow both api.myfoodfast.com and go.myorderboxhq.com so screens keep working whether or not they have been updated.
Signs the network is the problem
- The toolbar shows a disconnected indicator, or orders only appear after you tap Refresh.
- A new Kitchen Display cannot register — entering the 6-digit PIN fails or times out.
- Orders appear on one screen in the kitchen but not another on a different Wi-Fi network.
If you see these, check that the addresses above are reachable from the kitchen's network before raising a support ticket — and let us know the result when you do, as it saves a round trip.