# Connecting mysql db failed

**URL:** <https://support.prodi.gy/t/connecting-mysql-db-failed/248>\
**Category:** Uncategorized\
**Tags:** database, solved\
**Created:** [January 24, 2018, 3:40pm UTC](https://support.prodi.gy/t/connecting-mysql-db-failed/248 "2018-01-24T15:40:48Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [January 24, 2018, 3:55pm UTC](https://support.prodi.gy/t/connecting-mysql-db-failed/248/2 "2018-01-24T15:55:06Z")

</div>

Thanks for the report! This is strange – your config definitely looks okay. The good news is, under the hood, Prodigy uses [peewee](http://docs.peewee-orm.com/en/latest/), so you can debug the database connection by calling into peewee directly. If peewee can connect to your DB, Prodigy should, too. The database setup also allows more advanced usage – [see here for an example](https://support.prodi.gy/t/how-to-connect-to-a-remote-postgres-server-using-db-connect/109/7).

I had a look online and found [this issue on the peewee tracker](https://github.com/coleifer/peewee/issues/984) describing the same error message. The solution suggested was the following:

> So this error indicates that the mysql Python driver is not installed or is not import-able. [...] You've triggered the "mysql=None" bit, meaning peewee could not import either driver.

Maybe the MySQL driver is not available in the Python environment you're using to run Prodigy?

---

_[View the full topic](https://support.prodi.gy/t/connecting-mysql-db-failed/248)._