Last updated:

|Edit this page

App server is offline

If the server is offline, you need to update your PostHog deployment and/or manually start the server.


When you update to the latest version of PostHog, the app server should start automatically.

If it doesn't you need to make sure that a worker dyno is running. You have the choice to enable any of the following dyno types:

  • celeryworker - runs celery, the default background worker
  • pluginworker - runs posthog-plugin-server
  • worker - contains both celeryworker and pluginworker inside one dyno

You must have both the celery and app workers running for PostHog to function properly. You can either launch and scale them in separate dynos or run the default worker dyno, which includes both of them.

AWS CloudFormation

Please upgrade to the latest CloudFormation config that combines all background workers into one task and activates the server.

Previously we had separate tasks for worker-beat and worker-celery. In the latest version there is just one worker that starts all three services: celery, celery-beat and apps.


Please upgrade to at least version 1.4.0 of the PostHog helm chart to add the apps deployment.


You must run the bin/plugin-server script to start the plugin server.

In case your deployment runs bin/docker-worker, the plugin server is started automatically.


Was this page useful?

Next article

Apps developer reference

Note: It's worth reading the Building apps overview for a quick introduction to how to build your own app. plugin.json file A plugin.json file is structured as follows: Here's an example plugin.json file from our 'Hello world app' : Most options in this file are self-explanatory, but there are a few worth exploring further: main main determines the entry point for your app, where your setupPlugin and processEvent functions are. More on these later. config config consists of an…

Read next article