Django/Mysql/502 error.

@bdave

That’d be the issue :-). Gunicorn has failed, thus the socket file doesn’t exist, so when NGINX tries to proxy the request, there’s nothing for it to proxy to and you end up with the failure to connect.

So looking back over the configuration, if the issue is with the MySQL configuration that you are using, you need to double-check that the username, password, and database name are correct and that the user you’ve created has the ability to access the database.

Generally, you’d want to use something such as:

grant all on database.* to 'username'@'localhost' identified by 'password';

… to create your database using the MySQL CLI. You’d then import any data using (if needed):

mysql -u username -p database < data.sql

… or upon successful connection, if your application is supposed to populate the database, then allow it to do so.

The above tells MySQL to use the user username, requests that a password be entered using the -p argument, and tells it to restore the data to the database database. You really don’t want or need to use root as the user as it’s a global user and can do pretty much anything – so if someone does get past any security measures in place, and access is gained, it’d be relatively easy to wipe all data with that user (i.e a simple drop database dbname would be all it takes).

You may want to take a look at:

https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-16-04

Since you’re using MySQL, simply skip the Postgres details.

The issue that is being experienced with Django and MySQL on your Droplet seems to be related to either the configuration or the environment setup for your production server. Here’s a step-by-step guide to troubleshoot and resolve it:

Verify MySQL Credentials

Ensure the credentials in settings.py match those in your MySQL server. Test them with the MySQL command-line client:

mysql -u root -p

Then try connecting to the specific database:

USE ueba;
SHOW TABLES;

If you encounter access issues:

• Grant the necessary privileges to the root user for localhost:

GRANT ALL PRIVILEGES ON ueba.* TO 'root'@'localhost' IDENTIFIED BY 'password';
FLUSH PRIVILEGES;

Verify Django Database Configuration

Ensure your settings.py is correctly configured:

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'ueba',
        'USER': 'root',
        'PASSWORD': 'password',
        'HOST': 'localhost',  # Or IP address if remote
        'PORT': '3306',
    }
}