400 Error, Bad Request when visiting domain name, IP address loads fine

Hi, My website has been down for 2 months, I’ve basically given up resolving this issue, I have been talking with DO support as well as posting on stackoverflow and nobody seems to be able to help me.

Setup: 1-click install of django, ubuntu, nginx

Issue: After setting up a domain, visiting that domain results in a 400 error. visiting the IP works with no problem. I purchased the domain using Google Domains and used the custom name server option and put:

In etc/nginx/sites-available/django I have:

upstream app_server { 
server fail_timeout=0; 

server { 
listen 80 default_server; 
listen [::]:80 default_server ipv6only=on;

root /usr/share/nginx/html; 
index index.html index.htm;

client_max_body_size 4G; 

keepalive_timeout 5;

# Your Django project's media files - amend as required 
location /media { 
alias /home/django/django/dealr/dealr/media; 

# your Django project's static files - amend as required 
location /static { 
alias /home/django/django/dealr/dealr/static; 

location /favicon.ico { 
alias /home/django/django/dealr/favicon.ico; 

location / { 
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
proxy_set_header Host $http_host; 
proxy_redirect off; 
proxy_pass http://app_server; 

I have this file symlinked inside etc/nginx/sites-enabled.

Another thing that may be worth noting is even though I get a 400 error when visiting the domain, it still loads the favicon.

Any ideas or help would be appreciated.
Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This has to do with getting ALLOWED_HOSTS correct. ALLOWED_HOSTS: A list of strings representing the host/domain names that this Django site can serve Ref: ALLOWED_HOSTS Correct this in your setting file. e.g. Django One-click app has settings location: /home/django/django_project/django_project/

  1. Add your domain to ALLOWED_HOSTS
  1. At the end of file, one more entry exists for ALLOWED_HOSTS to allow sites to be accessed by DO ip addresses.
# Discover our IP address
ALLOWED_HOSTS = ip_addresses()

Change “=” operator to “+=”, so that it will append ip addresses rather than overwriting ALLOWED_HOSTS setting.

# Discover our IP address
ALLOWED_HOSTS += ip_addresses()
  1. If you don’t want your Webapp to be accessed by ip address, simply comment/remove second entry.

I believe I may have a solution. I was experiencing the same issue. I checked my file and at the very bottom I found

ALLOWED_HOSTS = ip_addresses()

I commented it out and everything appears to be working fine.
It seems that digital ocean has added this and the ip_addressses() function to the file but I do not have a clue as to why yet.

i had the same problem but after following this instruction, …Change “=” operator to “+=”, so that it will append ip addresses rather than overwriting ALLOWED_HOSTS setting…, its stopped overwriting as explained …thanks alot MeghaBodke