The Saving Advice Forums - A classic personal finance community.

Website Issues Apology

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Originally posted by humandraydel View Post
    Originally posted by PauletteGoddard
    I now know why nothing I have tried on my end (e.g. ipconfig /flushdns, nslookup savingadvice.com, erasing the cache, using a different proxy) has worked. Thanks for all that you do and for your efforts in getting this resolved. We love our blogs!
    Did you ever try a DIFFERENT website? If SA is the only website that doesn't work, it's not you, it's SA.
    Not necessarily. Just because you only notice one web site that is down doesn't mean the problem can't be fixed by changing something on your computer.

    I tried using flushdns too. Sometimes a computer keeps looking for a particular website in the wrong place, and sometimes flushdns will fix that. Granted, this only helps when a web site moves to another IP address, which doesn't happen often. But, it is possible for a website to be working perfectly fine and for certain computers to just not know where to find it. Of course, those computer will find it on their own eventually.

    Trying a different proxy makes sense too. It is always possible that a website is blocking your particular IP address because someone pegged it as being used in a malicious manner, and changing proxies could get around that.

    Comment


    • #17
      Thanks for all you do Jeffrey and Nate, we love Saving Advice!
      My other blog is Your Organized Friend.

      Comment


      • #18
        Originally posted by disneysteve View Post
        I do wonder why when SA was down, we were being taken to another website rather than just a 404 error screen.
        Well there were 2 issues. Both are hard to explain.

        1) The blogs went to another website because that other website is hosted on this server and it was a problem in the web server configuration. Basically the blogs were configured to go to the same IP address as is assigned to that other website.

        2) A lot of people can probably attest to seeing a weird super micro login page when they'd go to savingadvice. It weirded me out too. I never really got a good explanation of what that page is exactly but it had to do with when our web host moved us to the new web server, the ip on this new web server was being hijacked (just means another server on their network was trying to use it at the same time as us). So sometimes if you refreshed savingadivice, it would show the site as normal, and sometimes it would show that login page.

        What a nightmare, so glad its over with!

        Comment


        • #19
          Originally posted by nate View Post
          Well there were 2 issues. Both are hard to explain.

          1) The blogs went to another website because that other website is hosted on this server and it was a problem in the web server configuration. Basically the blogs were configured to go to the same IP address as is assigned to that other website.
          Makes sense. Thanks for the info.
          Steve

          * Despite the high cost of living, it remains very popular.
          * Why should I pay for my daughter's education when she already knows everything?
          * There are no shortcuts to anywhere worth going.

          Comment


          • #20
            Thanks so much, Nate and Jeffrey, for fixing the problem. Don't know what I'd do without the SA blogs!

            I didn't lose any entries, but I'm still having one problem with mine. Whenever I click "My Blog," or go to All Blogs and try to click on mine from there, I still get an error page. I can get to everyone else's blogs, and I can get to my control panel to change settings and write new entries. But if I try to go to my main blog page, same error message no matter which way I go at it.

            The error page is blue green and starts:
            Great Success !
            Apache is working on your cPanel® and WHM™ Server
            If you can see this page, then the people who manage this server have installed cPanel and WebHost Manager (WHM) which use the Apache Web server software and the Apache Interface to OpenSSL (mod_ssl) successfully. They now have to add content to this directory and replace this placeholder page, or else point the server at their real content.

            Comment


            • #21
              Originally posted by ceejay74 View Post
              Thanks so much, Nate and Jeffrey, for fixing the problem. Don't know what I'd do without the SA blogs!

              I didn't lose any entries, but I'm still having one problem with mine. Whenever I click "My Blog," or go to All Blogs and try to click on mine from there, I still get an error page. I can get to everyone else's blogs, and I can get to my control panel to change settings and write new entries. But if I try to go to my main blog page, same error message no matter which way I go at it.

              The error page is blue green and starts:
              Great Success !
              Apache is working on your cPanel® and WHM™ Server
              If you can see this page, then the people who manage this server have installed cPanel and WebHost Manager (WHM) which use the Apache Web server software and the Apache Interface to OpenSSL (mod_ssl) successfully. They now have to add content to this directory and replace this placeholder page, or else point the server at their real content.
              That is strange... I would suggest clearing your cache. Here is a page that describes how to do that no matter which web browser you use:

              Easily clear the cache on Windows, Mac, Android, iPhone, & iPad While your browser cache usually helps websites load faster, it can sometimes prevent you from seeing the most up-to-date version of a webpage. In some cases, an old or...


              Let me know if you still problems. One thing to note, after you clear cache, be sure to close all browser windows after you clear cache, then reopen a browser and try again.

              Comment


              • #22
                Yup, that fixed it. Awesome, thanks for the help!

                Comment

                Working...
                X