Troubleshooting#
Bugs#
If you find any bugs or issues, please report them directly to the GitHub Issue Tracker.
Common Solutions#
Running into issues? Outlined below are common errors and solutions.
Please make sure you are running the latest version of dash-tools: python -m pip install --upgrade dash-tools first. If you do not find an answer below, please Submit an Issue Ticket.
Command 'dashtools' is not recognized (windows)
Problem: You encounter an error “The term ‘dashtools’ is not recognized as the name of a cmdlet, function, script file, or operable program” when trying to run the dashtools command on Windows.
Solution: Run the command with .\dashtools instead. You may need to add dashtools to your system path variables.
Common heroku --deploy Issues
Error when creating requirements.txt file
Problem: You encounter an error when generating a requirements.txt file
Solution: Verify that you are running the dashtools heroku --deploy command from a valid plotly dash app directory. E.g. there is a src/app.py file.
No webpage displayed after Heroku deployment, no error messages
Problem: You are able to deploy your project online to Heroku, but nothing is displayed on the page
Solution1: This may be due to missing libraries that your app needs to run successfully. Check the requirements.txt. file.
Solution2: This may due to the fact that you forgot to add server = app.server to you main app.py file
Procfile is incorrect
Problem: When deploying, you get an error “Procfile is incorrect”
Solution: When deploying an app, the Procfile is checked for validity. Make sure that your Procfile points to the correct server entrypoint, e.g. server = app.server.
No solution found
Solution: Try typing into the terminal or command prompt heroku logs --tail. This will give you access to the official heroku logs of your app that enable monitoring your stack error troubleshooting
Common heroku --update Issues
Your account has reached its concurrent build limit.
Problem: When you try to update and redeploy your app to Heroku too many times within 10 minutes, you will get the above error message
Solution: First, wait a few minutes and try again. If that doesn’t work, check out a few possible solutions in this thread.
Unable to update heroku app
Problem: When you try to update your app, you get an error “Unable to update heroku app. Is the project already deployed?”
Solution: Make sure you have already run git init in the project root directory, and that you have already followed steps to deploy your project to heroku with dashtools heroku --deploy
If both of these steps do not work, verify that the heroku remote was added by running git remote. If you do not see it, try re-deploying your app or manually push to the correct remote with the dashtools heroku --update <remote> option, where <remote> is replaced with the correct remote.
Common init Issues
No write permission
Problem: You receive a ‘write permission’ error while trying to init a new app
Solution: Please check your write permissions for the current directory. Try the init command from a different directory.
Common run Issues
No valid python command found for your system
Problem: You encounter an error: No valid python command found for your system when trying to run your app
Solution: Set the python shell command with “dashtools run –set-python-shell-cmd
No such file or directory
Problem: You encounter an error: ‘No such file or directory’ when trying to dashtools run your app
Solution: Verify that you are running the dashtools run command from within a valid project root directory. Your app must be named app.py, or have a valid Procfile pointing to the app file.
Invalid Procfile
Problem: When you try to run, you get an error “Invalid Procfile”
Solution: When you run an app, the Procfile is checked for validity. Make sure that your Procfile points to the correct server entrypoint, e.g. server = app.server.