Question
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:
ns1.digitalocean.com ns2.digitalocean.com ns3.digitalocean.com
In etc/nginx/sites-available/django I have:
upstream app_server {
server 127.0.0.1:9000 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;
server_name cannablr.com www.cannablr.com;
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.
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.
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/settings.py
- Add your domain to ALLOWED_HOSTS
ALLOWED_HOSTS = ['example.com']
- 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()
- 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 settings.py 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 settings.py 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
You need to add your domain name to "ALLOWED_HOSTS’ inside of “settings.py” of the django project
For me, the issue was simply that the ALLOWED_HOSTS was set incorrectly. I had http://site.com instead of simply site.com
Also make sure that even though you may change this value, then it gets picked up as an environment variable (because you might need to unset it and set it again).
Thanks a lot everyone - helped a lot!
This is actually helpful , i was trying for a month , thanks man :')
thank you !! that last line of code in the settings file that shipped with the one click install killed me.
This was EXTREMELY helpful, thank you so much! Great explanation.
Have you found an update to this problem? I have the exact same thing happening to me now.
Try DigitalOcean for free
Click below to sign up and get $100 of credit to try our products over 60 days!
Hi, did you find out the solution to this? I’m having the same problem.
OK, I think I’ve confirmed what I was hinting at.
here’s the headers when I curl by domain:
Now, when I go by IP:
These 2 look similar, but very different when you realize the Content-Type is different and the IP-based one sets a cookie.
The short answer is that you have 2 separate sites running on this thing.
Let’s run this to see if my theory pans out:
This comment has been deleted