This section describes some of the common errors you may encounter when
trying to deploy to the Dash Enterprise, and provides information
about how to resolve these errors. If you can’t find the information
you’re looking for, or need help, contact our support team.
A quick note on checking your versions and on upgrading.
These docs are run using the versions listed above and these
versions should be the latest versions available.
To check which version that you have installed, you can run e.g.
`` To see the latest changes of any package, check the GitHub repo's CHANGELOG.md file: - [dash & dash-renderer changelog](https://github.com/plotly/dash/blob/master/CHANGELOG.md) -dash-renderer
is a separate package installed automatically with dash but its updates are included in the main dash changelog. These docs are using dash-renderer==1.8.2. - [dash-core-components changelog](https://github.com/plotly/dash-core-components/blob/master/CHANGELOG.md) - [dash-html-components changelog](https://github.com/plotly/dash-html-components/blob/master/CHANGELOG.md) - [dash-table changelog](https://github.com/plotly/dash-table/blob/master/CHANGELOG.md) - [plotly changelog](https://github.com/plotly/plotly.py/blob/master/CHANGELOG.md) - theplotly` package is also installed automatically with dash. It is
the Python interface to the plotly.js graphing library, so is mainly
used by dash-core-components, but it’s also used by dash itself.
These docs are using plotly==4.8.1.
All of these packages adhere to semver.
We recommend deploying with HTTPS for most of our users.
However, if your Dash Enterprise is using a self-signed
certificate, deploying with HTTPS
requires some extra, challenging configuration.
In these cases, it will be easier to set up deploying with SSH.
If you’re seeing the error above, it is likely that there is an error in
requirements.txt file. To resolve, check the versioning in your
requirements.txt file. For example, the above failed because
dash==29.1 isn’t a version of dash. If you’re working in a virtualenv then
you can check your version with the command:
if it is differs from your
requirements.txt, you can update it with the command:
For more information see Application Structure.
Deployment fails with the above message when you have failed to declare
server in your
app.py file. Check your
app.py file and confirm that
server = app.server.
For more information see
If you’re seeing a request for a password for dokku@your-dash-server, that
means that the ssh authentication has failed. This can be for a variety of
reasons so it is useful to run git push again with ssh debugging enabled by
GIT_SSH_COMMAND='ssh -v' before your
git push command.
Above, you can see the output of the debugging logs where unimportant lines
have been commented out or omitted. Check the first uncommented out line in the sample
output above to ensure that the domain is your Dash server’s domain and that port is 3022.
If it isn’t, you will need to update your
~/.ssh/config file to set the
correct port. You can see how to do that in our ssh chapter
under the “Modify SSH Config” heading.
The next two emphasized lines show the public keys that were offered (and
in this case rejected) by the server. If the RSA key that you added to
Dash Enterprise is not among those offered you will need to add it to your
ssh-add ~/path/to/your/key. More details on
ssh-agent are included in the
If you’re receiving the above user permission error, please
This error might occur if you are trying to push from a branch
that is not your
master branch. Get the name of your current
branch by running
git branch. Then, to push from this branch
to the remote server, run
git push plotly your-branch-name:master.
These applications require using a
process. When using a
worker process in your
you will have to explicitly start it after deploying. To
worker process, provide a
DOKKU_SCALE file with
something like this: