License, Updates & Health

Manage your WemX license, keep the installation up to date and monitor the scheduler and queue.

License

WemX needs a valid license key (starting with WMX-) to run. You can get a free Hobby key at app.wemx.net. See Plans & pricing for what each plan includes.

Go to Admin → License to:

  • see your plan, status, licensed domain, expiry date and last validation time,
  • see your plan limits: maximum orders, server connections, gateway configs and staff accounts,
  • enter a new key and Save License, which writes it to .env, or Verify License to re-check the current one.

The license is validated against the domain you're serving WemX on and re-checked every few hours. If no valid key is present, staff are redirected to the license page and customers see a License expired error.

When you reach a plan limit, creating more of that resource (for example a new order at checkout, a server connection or a gateway config) fails with a message explaining the limit.

Updates

See Updating WemX for the full procedure. In short: Admin → Updates shows your installed version, the latest release, a release timeline with changelogs, a one-click database backup, and Install release.

Health checks

The admin dashboard shows alerts when something needs your attention:

AlertMeaning
Queue worker is not runningBackground jobs (provisioning and emails) aren't being processed. Start or restart the worker.
Update availableA newer release is on GitHub.
Pre-release versionYou're running an alpha or beta build.

Schedule logs

Admin → Schedule Logs lists what the scheduler did and when, for example "5 orders were suspended for being past due date by 3 days", with the affected order IDs. Use it to confirm the cron job runs, and to answer questions about automatic suspensions.

Server requirements in production

  • Keep APP_DEBUG=false in production.
  • Run the queue worker under a process manager such as systemd or Supervisor, so it restarts if it crashes.
  • Serve WemX over HTTPS and set APP_URL to the HTTPS URL. Payment gateway callbacks rely on it.
  • Back up the database, the .env file (especially APP_KEY) and storage/ regularly.

On this page