Chrome Cache disabled and history/data cleared and still does not show new site





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I updated a reactjs site and put up a static site instead.



The react site was created with create-react-app and was compiled and served with ngnix, as is the static site.



I can see the new site with Safari and Firefox and Chrome on my phone. The issue is that Chrome on my laptop still shows the old React site.



If I open incognito mode it shows the new site. I have:




  • Cleared all cache/cookies/etc in chrome

  • Opened developer tabs and made sure "Disable Cache" is checked

  • Done the "Emtpy Cache and Hard Reload" thing with the dev tools open


Why is it still caching? How can I make chrome forget this domain?










share|improve this question























  • Since this is one of those problems that really don't make sense can I make a few questions? If you run your link with a querystring does it still show the cached site? Did you clear localstorage?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:17











  • Querystring still shows the cached site (example.com?asdf=true) and I did localStorage.clear() in the console`

    – mikeb
    Nov 26 '18 at 20:30











  • Is this by any chance running from Azure? I had a similar issue in the past... Fixed it with a app service restart. Have you tried that?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:34






  • 1





    Have you also checked github.com/facebook/create-react-app/issues/1910?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:42











  • It's running on an Ubuntu Linode that has an HAProxy reverse proxy in front of NGINX. It has been restarted, and as a matter of fact the haproxy is newer than the site, it used to just be directly into nginx...

    – mikeb
    Nov 26 '18 at 22:52


















1















I updated a reactjs site and put up a static site instead.



The react site was created with create-react-app and was compiled and served with ngnix, as is the static site.



I can see the new site with Safari and Firefox and Chrome on my phone. The issue is that Chrome on my laptop still shows the old React site.



If I open incognito mode it shows the new site. I have:




  • Cleared all cache/cookies/etc in chrome

  • Opened developer tabs and made sure "Disable Cache" is checked

  • Done the "Emtpy Cache and Hard Reload" thing with the dev tools open


Why is it still caching? How can I make chrome forget this domain?










share|improve this question























  • Since this is one of those problems that really don't make sense can I make a few questions? If you run your link with a querystring does it still show the cached site? Did you clear localstorage?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:17











  • Querystring still shows the cached site (example.com?asdf=true) and I did localStorage.clear() in the console`

    – mikeb
    Nov 26 '18 at 20:30











  • Is this by any chance running from Azure? I had a similar issue in the past... Fixed it with a app service restart. Have you tried that?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:34






  • 1





    Have you also checked github.com/facebook/create-react-app/issues/1910?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:42











  • It's running on an Ubuntu Linode that has an HAProxy reverse proxy in front of NGINX. It has been restarted, and as a matter of fact the haproxy is newer than the site, it used to just be directly into nginx...

    – mikeb
    Nov 26 '18 at 22:52














1












1








1








I updated a reactjs site and put up a static site instead.



The react site was created with create-react-app and was compiled and served with ngnix, as is the static site.



I can see the new site with Safari and Firefox and Chrome on my phone. The issue is that Chrome on my laptop still shows the old React site.



If I open incognito mode it shows the new site. I have:




  • Cleared all cache/cookies/etc in chrome

  • Opened developer tabs and made sure "Disable Cache" is checked

  • Done the "Emtpy Cache and Hard Reload" thing with the dev tools open


Why is it still caching? How can I make chrome forget this domain?










share|improve this question














I updated a reactjs site and put up a static site instead.



The react site was created with create-react-app and was compiled and served with ngnix, as is the static site.



I can see the new site with Safari and Firefox and Chrome on my phone. The issue is that Chrome on my laptop still shows the old React site.



If I open incognito mode it shows the new site. I have:




  • Cleared all cache/cookies/etc in chrome

  • Opened developer tabs and made sure "Disable Cache" is checked

  • Done the "Emtpy Cache and Hard Reload" thing with the dev tools open


Why is it still caching? How can I make chrome forget this domain?







html5 reactjs google-chrome






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 26 '18 at 19:21









mikebmikeb

5,49622766




5,49622766













  • Since this is one of those problems that really don't make sense can I make a few questions? If you run your link with a querystring does it still show the cached site? Did you clear localstorage?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:17











  • Querystring still shows the cached site (example.com?asdf=true) and I did localStorage.clear() in the console`

    – mikeb
    Nov 26 '18 at 20:30











  • Is this by any chance running from Azure? I had a similar issue in the past... Fixed it with a app service restart. Have you tried that?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:34






  • 1





    Have you also checked github.com/facebook/create-react-app/issues/1910?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:42











  • It's running on an Ubuntu Linode that has an HAProxy reverse proxy in front of NGINX. It has been restarted, and as a matter of fact the haproxy is newer than the site, it used to just be directly into nginx...

    – mikeb
    Nov 26 '18 at 22:52



















  • Since this is one of those problems that really don't make sense can I make a few questions? If you run your link with a querystring does it still show the cached site? Did you clear localstorage?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:17











  • Querystring still shows the cached site (example.com?asdf=true) and I did localStorage.clear() in the console`

    – mikeb
    Nov 26 '18 at 20:30











  • Is this by any chance running from Azure? I had a similar issue in the past... Fixed it with a app service restart. Have you tried that?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:34






  • 1





    Have you also checked github.com/facebook/create-react-app/issues/1910?

    – Carlos Alves Jorge
    Nov 26 '18 at 20:42











  • It's running on an Ubuntu Linode that has an HAProxy reverse proxy in front of NGINX. It has been restarted, and as a matter of fact the haproxy is newer than the site, it used to just be directly into nginx...

    – mikeb
    Nov 26 '18 at 22:52

















Since this is one of those problems that really don't make sense can I make a few questions? If you run your link with a querystring does it still show the cached site? Did you clear localstorage?

– Carlos Alves Jorge
Nov 26 '18 at 20:17





Since this is one of those problems that really don't make sense can I make a few questions? If you run your link with a querystring does it still show the cached site? Did you clear localstorage?

– Carlos Alves Jorge
Nov 26 '18 at 20:17













Querystring still shows the cached site (example.com?asdf=true) and I did localStorage.clear() in the console`

– mikeb
Nov 26 '18 at 20:30





Querystring still shows the cached site (example.com?asdf=true) and I did localStorage.clear() in the console`

– mikeb
Nov 26 '18 at 20:30













Is this by any chance running from Azure? I had a similar issue in the past... Fixed it with a app service restart. Have you tried that?

– Carlos Alves Jorge
Nov 26 '18 at 20:34





Is this by any chance running from Azure? I had a similar issue in the past... Fixed it with a app service restart. Have you tried that?

– Carlos Alves Jorge
Nov 26 '18 at 20:34




1




1





Have you also checked github.com/facebook/create-react-app/issues/1910?

– Carlos Alves Jorge
Nov 26 '18 at 20:42





Have you also checked github.com/facebook/create-react-app/issues/1910?

– Carlos Alves Jorge
Nov 26 '18 at 20:42













It's running on an Ubuntu Linode that has an HAProxy reverse proxy in front of NGINX. It has been restarted, and as a matter of fact the haproxy is newer than the site, it used to just be directly into nginx...

– mikeb
Nov 26 '18 at 22:52





It's running on an Ubuntu Linode that has an HAProxy reverse proxy in front of NGINX. It has been restarted, and as a matter of fact the haproxy is newer than the site, it used to just be directly into nginx...

– mikeb
Nov 26 '18 at 22:52












1 Answer
1






active

oldest

votes


















0














OK, based on Carlos Alves Jorge's link above:



navigator.serviceWorker.ready.then(registration => {
registration.unregister();
});


I ran that in the javascript console and it worked!



Thank you!






share|improve this answer
























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53487707%2fchrome-cache-disabled-and-history-data-cleared-and-still-does-not-show-new-site%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    OK, based on Carlos Alves Jorge's link above:



    navigator.serviceWorker.ready.then(registration => {
    registration.unregister();
    });


    I ran that in the javascript console and it worked!



    Thank you!






    share|improve this answer




























      0














      OK, based on Carlos Alves Jorge's link above:



      navigator.serviceWorker.ready.then(registration => {
      registration.unregister();
      });


      I ran that in the javascript console and it worked!



      Thank you!






      share|improve this answer


























        0












        0








        0







        OK, based on Carlos Alves Jorge's link above:



        navigator.serviceWorker.ready.then(registration => {
        registration.unregister();
        });


        I ran that in the javascript console and it worked!



        Thank you!






        share|improve this answer













        OK, based on Carlos Alves Jorge's link above:



        navigator.serviceWorker.ready.then(registration => {
        registration.unregister();
        });


        I ran that in the javascript console and it worked!



        Thank you!







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 27 '18 at 0:34









        mikebmikeb

        5,49622766




        5,49622766
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53487707%2fchrome-cache-disabled-and-history-data-cleared-and-still-does-not-show-new-site%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Wiesbaden

            Marschland

            Dieringhausen