Troubleshoot a Python Deployment
Python startup problems are often caused by a wrong entry file, an undeclared dependency or a mismatch between the selected Python version and the project. Check one item at a time and use the panel console to verify the result.
The consolex1 custom egg
The Python Universal egg is developed by the consolex1 hosting provider. Its source code is public on GitHub.
1. Verify the Python version and main file
In the Startup tab, confirm the selected supported Python version and the exact main file name, including capitalization. The configured file must exist in the instance root or match its configured path.
2. Declare dependencies
List required packages in requirements.txt, pyproject.toml or uv.lock. Python Universal uses uv to install dependencies from supported manifests; check the console for package resolution errors.
3. Resolve import errors
Confirm that the module is declared, that the import name is correct and that the application files were uploaded to the expected directory. Avoid uploading a local .venv built on another operating system.
4. Check secrets and startup behavior
Read tokens from environment variables configured privately in the panel. Make sure the process stays in the foreground and prints useful startup errors rather than exiting silently.
5. Measure resource use
Monitor memory during startup and normal activity. The Free plan includes 256 MB RAM and 512 MB storage; large dependencies and caches can consume a meaningful share of that allocation.