Troubleshooting
If you encounter an error that isn’t included on this page or if the solution provided doesn’t work, please reach out to us on Discord, email us at contact@qbraid.com, or open a bug report.
Error launching Lab
If you get one of the following errors while launching Lab,
400: Bad Request
500: Internal Server Error
503: Service Unavailable
Spawn failed
your qBraid Lab server failed to start. Follow the prompts on the screen, or if none are given, return to https://account.qbraid.com, and click Launch Lab to try again.
Lab server errors
If you get one of the following errors from inside Lab,
Service unavailable or unreachable
File Save Error
you need to restart your qBraid Lab server. For these types of errors, refreshing the page won’t work. Instead, you need to pull down a new Lab image, which can only be done from the qBraid Hub Control Panel:
Go to File > Hub Control Panel, or type https://lab.qbraid.com/hub/home directly into your browser. From there, click Stop My Server > Start My Server > Launch Server, and wait for Lab to reload.
ModuleNotFoundError
While running a notebook, if you get a ModuleNotFoundError
after an import statement:
- Check to make sure you are using the correct notebook kernel for your environment, see Switch notebook kernel.
- If you are using the correct kernel, the package you are trying to import may not be installed in that environment. See Install new package.
NoRegionError
If you are running an Amazon Braket notebook and get a NoRegionError
, it’s likely that you have not enabled Quantum Jobs. Run
and restart your kernel, and try running the notebook again.
UnrecognizedClientException
If you are trying to submit an AWS task and get the following exception,
it most likely means that you have not enabled Quantum Jobs. Run
and restart your kernel, and try running the notebook again.
OpenSSL AttributeError
Depending on the environment you’re using, executing
may raise AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms'
. If this happens to you, don’t worry!
This is simply a result of an outdated pyOpenSSL
version. Upgrade to the latest version and the problem should be resolved: