Why The changes of my development server, are not reflected in the production server (views and urls)??

Hi, I am writing to see if you can help me with this: I happen is that I make changes in the development server and they work me well, but when I want to see them in production, I do not recognize them and I throw the error:

Page not found (404) Request Method: GET Request URL:

I have tried all sorts of views, and called in urls, (all of them work in development, but nothing works for me in production) last clone a class definition that makes the same call and uses the same template but only change the name of the Definition to see if it works, and it happens to me the same everything works well in development, but when I want to see it in production, I throw the error mentioned at the beginning (404).

I have also tried, reloading nginx with several commands for me to take the changes, but the negative result even, these are the commands I tried:

Sudo systemctl daemon-reload Sudo systemctl start gunicorn Sudo systemctl restart nginx Sudo systemctl start nginx Sudo ufw allow ‘Nginx Full’

Thank you for the help, I do not know what else to try.


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

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.

Try rebooting the droplet by typing following command in the command prompt

sudo reboot

@jtittle Finally succeed in solving !!!

Was what I suspected, finally managed to find the right command that generated a borron and new account in my drop and so take into account the changes made. The solution in case you ever come across a similar problem is:

“Sudo reboot”

Thank God, and I can go ahead with my project.



Please, this is below I send it to support, but they did not give me any specific answer but I am responsible for what I do on my server,

Now please read it and tell me if this throws you some previous experience or I forget the subject ??

this to support ----->

After doing a thousand things with my code and try it and re-test it on my local machine and on the development server in my droplet, I make changes to my code and I incorporate new pages, and everything works well for me on both sides My home and the environment of development of the droplet).

But when I want to see the changes in my domain, these are not reflected and after making queries in the community and investigate by other means the conclusion is that “there are no programming errors, or configuration”

So I did a last test and delete several urls from my file and after that I completely deleted my file and of course I can not enter my application because it gives me error, but in the domain everything follows such As if nothing has happened, then I stopped the server with all the commands to stop and restore and my site keeps pointing everything as it is without changes (like glue stick) no matter what I do, it does not reflect my urls changes.

These are the commands I tried to take off my nginx:

Sudo systemctl start nginx Sudo systemctl stop nginx Sudo systemctl restart nginx Sudo service nginx start Sudo service nginx stop Sudo service nginx restart Sudo /etc/init.d/nginx start Sudo /etc/init.d/nginx stop Sudo /etc/init.d/nginx restart

Can you check what happens in my droplet ??? Or give me some command to reset nginx and take what I do in development ??

@jtittle Comparing a good request with one that does not respond and that is the case of my problem, I see that the first one returns a string

“GET / houses / rental_list / HTTP / 1.1” "

But in which I call the page that I can not see, it returns the empty string “GET / houses / mipagina HTTP / 1.1” 404 1164 “-”

Does this give you any clue? - - [19/May/2017:12:47:19 +0000] “GET /casas/lista_casas_ventas/ HTTP/1.1” 200 2068 “” "Mozilla/5.0 (X11; Linux… - - [19/May/2017:12:47:21 +0000] “GET /casas/lista_casas_arriendos/ HTTP/1.1” 2$ - - [19/May/2017:12:47:24 +0000] “GET /send/ HTTP/1.1” 200 2619 "http://www.max$ - - [19/May/2017:12:47:24 +0000] “GET /media/photo/logo.png HTTP/1.1” 200 10317$ - - [19/May/2017:12:47:24 +0000] “GET /media/photo/max8-ot88.png HTTP/1.1” 200 $ - - [19/May/2017:12:47:26 +0000] “GET /admin/ HTTP/1.1” 200 1196 "$ - - [19/May/2017:12:47:29 +0000] “GET / HTTP/1.1” 200 1520 "http://www.maxsiste$ - - [19/May/2017:12:47:31 +0000] “GET / HTTP/1.1” 200 1520 "http://www.maxsiste$ - - [19/May/2017:12:53:45 +0000] “GET /casas/mipagina HTTP/1.1” 404 1164 “-” "Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 …


Sorry that I did not answer you last night, but here in the end of South America it was late and I had to go to sleep. Today I greet you with a few “good morning” and I send you this one to strike down here; However, tell me if you can see any obvious flaws or suddenly recommend that I re-do the site completely again, but I’d like you to find out what it might be, because otherwise, it’s going to be a factor of uncertainty regarding python and django .

I will be waiting for your answer to see what to do, if you insist on discovering the fault or on the contrary redo everything again, although I prefer the first option.

user www-data; worker_processes auto; pid /run/;

events { worker_connections 768; # multi_accept on; }

http {

    # Basic Settings

    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 65;
    types_hash_max_size 2048;
    # server_tokens off;

types_hash_max_size 2048; # server_tokens off;

    # server_names_hash_bucket_size 64;
    # server_name_in_redirect off;

    include /etc/nginx/mime.types;
    default_type application/octet-stream;

    # SSL Settings

    ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
    ssl_prefer_server_ciphers on;

    # Logging Settings

    access_log /var/log/nginx/access.log;

access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; error_log /var/log/nginx/error.log debug;

    # Gzip Settings

    gzip on;
    gzip_disable "msie6";

    # gzip_vary on;
    # gzip_proxied any;
    # gzip_comp_level 6;
    # gzip_buffers 16 8k;
    # gzip_http_version 1.1;
    # gzip_types text/plain text/css application/json application/javascript text/xml appli$

    # Virtual Host Configs
    # Virtual Host Configs

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;


#mail {

# See sample authentication script at:


# auth_http localhost/auth.php;

# pop3_capabilities “TOP” “USER”;

# imap_capabilities “IMAP4rev1” “UIDPLUS”;

server {

listen localhost:110;

protocol pop3;

proxy on;

   #               protocol   pop3;

proxy on;


server {

listen localhost:143;

protocol imap;

proxy on;




What does your server block for NGINX look like?


Hmmm, well.

I am intrigued that I do not have any separate development and production configurations, since what I run with python3 runserver and it works, I assume that when I exit the development environment and run the nginx start, it should work same. That is why I am worried about this, since it is taking away time and I can not get out of the trap.

In case of any idea in specific, please let me know and anyway, thank you very much for your inconvenience and for everything that always helps me.

thanks take care


Nothing seems to really look out of ordinary to me, so the issue, based on what I’m seeing, would be somewhere in the production environment.

There’s something, somewhere, that differs between your development and productions servers. It’s, unfortunately, not something that you’ll find within NGINX because all NGINX is really doing is taking the request and proxying it over to your app.

What I’d recommend doing is retracing your steps and make sure that everything you setup for the development server is identical to what you’re running for production. When it comes to detailed setups and configurations, it’s easy to miss a step here or there and ultimately, that can lead to an application not working as expected or completely failing.


2017/05/18 23:04:40 [debug] 19267#19267: *21 writev: 1441 of 1441 2017/05/18 23:04:40 [debug] 19267#19267: *21 http write filter 0000000000000000 *2017/05/18 23:04:40 [debug] 19267#19267: 21 http copy filter: 0 “/casas/mipagina?” 2017/05/18 23:04:40 [debug] 19267#19267: *21 http finalize request: 0, “/casas/mipagina?” a:1, c:1 2017/05/18 23:04:40 [debug] 19267#19267: *21 set http keepalive handler