Common Errors

This documentation is for Dash Enterprise,
Plotly’s commercial platform for managing and improving
Dash applications in your organization.
View the docs or
request a trial.

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.


Package Versioning

Are you using the latest versions?
dash==1.16.1
dash-html-components==1.1.1
dash-core-components==1.12.1
dash-table==4.10.1

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.
```

import dash_core_components
print(dash_core_components.version)
`` 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-rendereris 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.1. - [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.


Deploying with Self-Signed Certificates?

SSL certificate problem: self signed certificate
fatal: unable to access 'https://<your-dash-enterprise>/GIT/your-dash-app-name/': SSL certificate problem: self signed certificate

 

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.


Deployment Failing?

Could not find a version that satisfies the requirement

shell ... remote: -----> Cleaning up... remote: -----> Building my-dash-app from herokuish... remote: -----> Injecting apt repositories and packages ... remote: -----> Adding BUILD_ENV to build environment... remote: -----> Python app detected remote: ! The latest version of Python 2 is python-2.7.15 (you are using python-2.7.13, which is unsupported). remote: ! We recommend upgrading by specifying the latest version (python-2.7.15). remote: Learn More: <a href="https://devcenter.heroku.com/articles/python-runtimes">https://devcenter.heroku.com/articles/python-runtimes</a> remote: -----> Installing python-2.7.13 remote: -----> Installing pip remote: -----> Installing requirements with pip remote: Collecting dash==0.29.1 (from -r /tmp/build/requirements.txt (line 1)) remote: Could not find a version that satisfies the requirement dash==0.29.1 (from -r /tmp/build/requirements.txt (line 1)) (from versions: 0.17.4, 0.17.5, 0.17.7, 0.17.8rc1, 0.17.8rc2, 0.17.8rc3, 0.18.0, 0.18.1, 0.18.2, 0.18.3rc1, 0.18.3, 0.19.0, 0.20.0, 0.21.0, 0.21.1, 0.22.0rc1, 0.22.0rc2, 0.22.0, 0.23.1, 0.24.0, 0.24.1rc1, 0.24.1, 0.24.2, 0.25.0) remote: No matching distribution found for dash==0.29.1 (from -r /tmp/build/requirements.txt (line 1))

 

If you’re seeing the error above, it is likely that there is an error in
your 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:

$ pip list

 

if it is differs from your requirements.txt, you can update it with the command:

$ pip freeze > requirements.txt

 

For more information see Application Structure.

 

Failed to find application object 'server' in 'app

shell ... remote: Failed to find application object 'server' in 'app' remote: [2018-08-16 16:00:49 +0000] [181] [INFO] Worker exiting (pid: 181) remote: [2018-08-16 16:00:49 +0000] [12] [INFO] Shutting down: Master remote: [2018-08-16 16:00:49 +0000] [12] [INFO] Reason: App failed to load. remote: [2018-08-16 16:00:51 +0000] [12] [INFO] Starting gunicorn 19.9.0 remote: [2018-08-16 16:00:51 +0000] [12] [INFO] Listening at: <a href="http://0.0.0.0:5000">http://0.0.0.0:5000</a> (12) remote: [2018-08-16 16:00:51 +0000] [12] [INFO] Using worker: sync remote: [2018-08-16 16:00:51 +0000] [179] [INFO] Booting worker with pid: 179 remote: [2018-08-16 16:00:51 +0000] [180] [INFO] Booting worker with pid: 180

 

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
you have server = app.server.

 

For more information see
Application Structure.

 

SSH deploy: git push is asking for password.
$ git push multipage master
dokku@dash.local's password:

 

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
adding GIT_SSH_COMMAND='ssh -v' before your git push command.

$ GIT_SSH_COMMAND='ssh -v' git push plotly master

# OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n  7 Dec 2017
# debug1: Reading configuration data /home/michael/.ssh/config
# debug1: /home/michael/.ssh/config line 1: Applying options for dash.local
# debug1: Reading configuration data /etc/ssh/ssh_config
# debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to dash.local [192.168.233.240] port 3022.
# debug1: Connection established.
# ...
# ...
# debug1: Authentications that can continue: publickey,password
# debug1: Next authentication method: publickey
debug1: Offering public key: RSA SHA256:NWVDKQ /home/michael/.ssh/test
# debug1: Authentications that can continue: publickey,password
debug1: Offering public key: RSA SHA256:zessB4 /home/michael/.ssh/google_compute_engine
# debug1: Authentications that can continue: publickey,password
# debug1: Trying private key: /home/michael/.ssh/id_rsa
# debug1: Trying private key: /home/michael/.ssh/id_dsa
# debug1: Trying private key: /home/michael/.ssh/id_ecdsa
# debug1: Trying private key: /home/michael/.ssh/id_ed25519
# debug1: Next authentication method: password
dokku@dash.local's password:

 

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-agent
with ssh-add ~/path/to/your/key. More details on ssh-agent are included in the
ssh chapter.

Got permission denied while trying to connect to the Docker daemon socket
$ Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get <a href="http://%2Fvar%2Frun%2Fdocker.sock/v1.38/containers/json?all=1&filters=%7B%22label%22%3A%7B%22dokku%22%3Atrue%7D%2C%22status%22%3A%7B%22exited%22%3Atrue%7D%7D:">http://%2Fvar%2Frun%2Fdocker.sock/v1.38/containers/json?all=1&filters=%7B%22label%22%3A%7B%22dokku%22%3Atrue%7D%2C%22status%22%3A%7B%22exited%22%3Atrue%7D%7D:</a> dial unix /var/run/docker.sock: connect: permission denied

 

If you’re receiving the above user permission error, please
contact support.

Unable to select a buildpack
...
remote:            Adding BUILD_ENV to build environment...
remote:            Unable to select a buildpack

 

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.

 


Problems Using a Celery Process?

Callbacks using async processes aren't running and `Celery` is not present in app logs

These applications require using a worker
process. When using a worker process in your Procfile,
you will have to explicitly start it after deploying. To
scale a worker process, provide a DOKKU_SCALE file with
something like this:

$web=1 worker=1