Troubleshooting sync and images

Check that your server address is correct and your device can reach it.

• If your Mealie server is on your local network, make sure your iPhone is on the same Wi-Fi network. Allow Forked to access your local network when prompted.
• If you are connecting remotely, use HTTPS.
• If your local HTTPS proxy uses mkcert or another self-signed certificate, enable the Trust local self-signed HTTPS option.
• Plain HTTP fallback is only for private IPs, localhost, or .local names, so a custom LAN hostname such as mealie.lab still needs HTTPS.

Forked does not support public plain HTTP or Mealie hosted under a path like /mealie. See Connect Forked to Mealie for the addresses that work.

Forked only sends the API token to the configured server origin (scheme, hostname, and port). If your Mealie images resolve to a different origin, the image requests may fail. Keep Mealie API and media routes on the same origin.

If Mealie stops accepting Forked’s sign-in, for example because its API token was deleted, a banner at the top says “Mealie didn’t accept your sign-in. Recipes aren’t updating.” Tap Sign In to connect again. Saved recipes, plans, and Shopping keep working in the meantime.

Forked keeps working from saved data when your server is slow or unreachable. See Offline use and saved data for what works offline and what waits for your server.

Use Profile → Settings → About → Report a Bug to contact us with what happened. It opens an email you can review before sending. Attach diagnostics adds recent app logs and settings, with API tokens and server addresses redacted; turn it off if you prefer to send only your description. You can also email support@knownframe.com.