We are doing the best we can so you do not have to read this section.

That said, we have included solutions (or at least explanations) for some common problems below.

If you do not find a solution to your problem here, please ask for help!

Module object has no attribute ‘register_json’

Kinto uses the JSONBin feature of PostgreSQL, which is used to store native JSON objects efficiently. Support for this feature was added in PostgreSQL 9.4.

This is a hard requirement for postgresql backends, therefore you will either need to use PostgreSQL 9.4 (or greater), or use a different backend entirely.

No module named functools

With some old version of pip, the jsonschema package does not install properly because one if its dependencies is missing.

To fix this, you can either install it locally or upgrade your version of pip:

$ pip install --upgrade pip

socket.error: [Errno 48] Address already in use

Another process has occupied Kinto’s default port 8888.

To fix this, see which service is running on port 8888:

$ sudo lsof -i :8888

and kill the process using PID from output:

$ kill -kill [PID] OperationalError [Postgres Service]

Make sure that postgres server is running properly.

bind(): No such file or directory [uwsgi error]

Make sure that the path you defined for the socket parameter of the uwsgi configuration exists.

To fix this:

socket = /var/run/uwsgi/kinto.sock

Make repository:

sudo mkdir -p /var/run/uwsgi

Also, make sure the user that runs uwsgi can access /var/run/uwsgi and can write in the uwsgi directory.

AssertionError: Unexpected database encoding sql_ascii

On some configuration, the default encoding is SQL_ASCII instead of UTF-8. This can also happen with other database encoding. The encoding expected by kinto is “UTF-8”.

To remediate this, you can issue the following command, once pgsql open:

update pg_database set encoding = pg_char_to_encoding('UTF8') where datname = '<your db name>';