Jump to content

Site Down? Unavailable?


Recommended Posts

Posted

If you've been using more than one DNS server, which is often the case, and if one or more of them hasn't been updated, they will point you to the old IP and you will have issues connecting to the site, you'll go back and forth between the old IP and the new. Getting a 503 error means that you've connected to the old IP.

 

You may temporarily switch to Google's public DNS servers or OpenDNS until your original DNS servers get updated. Don't forget to use "ipconfig /flushdns" after you've changed your DNS servers. Also, if you use Chrome, go to chrome://net-internals/#dns and click on "Clear Host Cache".

Posted

If you've been using more than one DNS server, which is often the case, and if one or more of them hasn't been updated, they will point you to the old IP and you will have issues connecting to the site, you'll go back and forth between the old IP and the new. Getting a 503 error means that you've connected to the old IP.

 

You may temporarily switch to Google's public DNS servers or OpenDNS until your original DNS servers get updated. Don't forget to use "ipconfig /flushdns" after you've changed your DNS servers. Also, if you use Chrome, go to chrome://net-internals/#dns and click on "Clear Host Cache".

And how do you do what your talking about?

Guest Plastrader
Posted

So why does LL switch IP-number?
I've tried to switch DNS but to no avail, been reading the 503 message too much today(or yesterday depending how you look at things)
 

503: Service Unavailable
Site is down temporarily for upgrades and mainteance. Will be back up soon as possible.

-hal

BTW: maintenance

Posted

happened again this was the message it gave

 

 

503: Service Unavailable
Site is down temporarily for upgrades and mainteance. Will be back up soon as possible.

-hal

Posted

Flushing dns worked perfect so far and gave me immediate access back to the site lets hope it stays that way thanks guys.

Guest tomm434
Posted

Same thing. Tried to flush DNS for Mozilla and it didn't work.

Posted

A few tips for people having problems accessing to the site. If you've been getting a 503 error, it means that you connect to the old IP address for LL.

  • Press Win + R
  • Type "cmd" and press ENTER
  • Type "ipconfig /all" to get the list of DNS servers you've been using. (Look for the addresses in the Local Area Connection or Wireless Network Connection sections depending on how you are connected to Internet)
  • Type "nslookup www.loverslab.com <Your DNS Server IP which you've found out above>" for example, "nslookup www.loverslab.com 8.8.8.8" etc.
  • Make sure that you do this for all your DNS server IPs.
It should list two IP addresses instead of one. My DNS server gives me these addressess for LL...

 

 

 

141.101.124.103

108.162.207.103

 

 

 

Again, make sure that you get these addresses for *all* the DNS servers you use. If one of them shows a different address then you'll have problems connecting the site. Remove that server temporarily or replace your DNS servers completely with the ones of Google or OpenDNS.

 

If you've changed your DNS servers to Google's or OpenDNS make sure that you reset Windows' and your browsers DNS cache. Close and restart your browser.

 

Also try to connect the site using a different browser which you don't normally use to connect to this site.

 

--------------------------------------------------------------------------------------

 

If you don't want to change your DNS servers just for this site then add these lines to your Windows hosts file. In case you have problems connecting the site later on delete these lines from the file.

 

 

 

141.101.124.103 loverslab.com

108.162.207.103 loverslab.com

 

141.101.124.103 www.loverslab.com

108.162.207.103 www.loverslab.com

 

 

 

--------------------------------------------------------------------------------------

 

I recommend that you learn how to diagnose simple network problems like this, as it may happen again in the future.

 

I also recommend that you bookmark this site. Whenever you have problems accessing LL, go there and check if the site is up or down. Also, check the site's availability from worldwide locations. It'll list the IP addresses used to access LL, compare those IP addresses with the ones you get from *your* DNS servers. If they don't match then find a public DNS server that gives you the IPs you actually need to connect the site.

Posted

ITT: Instructions on how to access a site posted on the site people can't access -- to read the instructions. ;)

 

That said, note that for the ipconfig /flushdns to work, you must have your browser closed. If any copies are open, they are maintaining their own DNS cache; at least, FF does. Close your browsers before following those instructions.

 

If your broadband router is caching DNS responses, and it may be, restart it.

Posted

ITT: Instructions on how to access a site posted on the site people can't access -- to read the instructions. ;)

 

 

There are many ways to access a site indirectly. Even a simple web proxy may allow you to read these instructions, but I posted those mainly for future reference. As far as I'm aware of, this is at least the third time the site has changed its IPs, and the same thing will probably happen again. It would be a good idea to learn how to find your way to LL when it happened.

Posted

I just gave up after using a proxy to read bjornk's post and came back today and it works just fine. Cleared all the histories etc, rebooted the computer, net etc. and all is good... On the note of changing locations and such.. each time so far it has been an improvement.. I can deal with a day or so of issues for this. I just wish there was a notice that informed members of this big of a change. If there was one .. I didn't see it and was shocked and frustrated when it was difficult to get to this site.

Posted

There is really is no magic solution to suggest here when it comes to DNS problems. Either wait it out and let it fix itself without requiring any work from you or as already suggested; flush your DNS cache and/or swap between DNS servers every so often until it does work.

 

DNS problems like this are nothing more than a waiting game. If flushing your DNS cache or swapping your DNS provider around doesn't help, than you have something else being incredibly overzealous with it's caching at this point.

 

 

ITT: Instructions on how to access a site posted on the site people can't access -- to read the instructions. ;)
 

 

There are many ways to access a site indirectly. Even a simple web proxy may allow you to read these instructions, but I posted those mainly for future reference. As far as I'm aware of, this is at least the third time the site has changed its IPs, and the same thing will probably happen again. It would be a good idea to learn how to find your way to LL when it happened.

 

 

To be fair, while the site has changed IP's 3 or 4 times in the past few months, it has been between the same 2 IPs.

 

It shouldn't happen again however. Hopefully.

 

I originally planned to combat the increasing server bandwidth cost for the site by setting up an FTP mirror for all downloads off LoversLab, so I could easily switch the site to download from itself or from the ftp mirror site depending on bandwidth usage between the two.

 

Unfortunately I'm stupidly busy, and not to mention stupidly lazy when I'm not busy being stupidly busy.

 

So for the past few months instead of a simple "Hey the sites reaching the bandwidth usage cap, lets spend a couple easy seconds to switch the site from using the mirror to the primary server."

It has instead been "Oh god, the sites passed the bandwidth usage cap and I now owe the hosting company a bunch of money, but I still haven't setup the download mirror! I should hurry and transfer the site over to the mirror and use that instead so the current bandwidth overages don't anally rape me any more than they already have!"

 

I think after repeating that process 4 times now though I've finally maybe started to learn my lesson and will get around to setting up the originally planned download mirror before it's too late and I end up needing to swap between the two servers again. 

 

Regrettably though I find myself significantly more fond of the hostname on the previous server compared to the server the site is currently on now, and as a result would greatly prefer the other server be considered the "primary", and the one the site is currently on the "mirror". I could fix this nitpick by just swapping the hostnames on the servers - but a paranoid/superstitious part of me is convinced that doing so would be bad luck, like renaming a boat...

 

Posted

 

Unfortunately I'm stupidly busy, and not to mention stupidly lazy when I'm not busy being stupidly busy.

Me too. I know what you are going through...

 

So for the past few months instead of a simple "Hey the sites reaching the bandwidth usage cap, lets spend a couple easy seconds to switch the site from using the mirror to the primary server."

It has instead been "Oh god, the sites passed the bandwidth usage cap and I now owe the hosting company a bunch of money, but I still haven't setup the download mirror! I should hurry and transfer the site over to the mirror and use that instead so the current bandwidth overages don't anally rape me any more than they already have!"

 

I think after repeating that process 4 times now though I've finally maybe started to learn my lesson and will get around to setting up the originally planned download mirror before it's too late and I end up needing to swap between the two servers again.

I do hope you learn your lesson and get the download mirror set up before it's too late... that is unless you like getting for the company to "anally rape" you for the bandwidth overages.. then by all means .. keep going.. ;).

 

Regrettably though I find myself significantly more fond of the hostname on the previous server compared to the server the site is currently on now, and as a result would greatly prefer the other server be considered the "primary", and the one the site is currently on the "mirror". I could fix this nitpick by just swapping the hostnames on the servers - but a paranoid/superstitious part of me is convinced that doing so would be bad luck, like renaming a boat...

A agree with you on that as well. I really don't like messing with something that I need to run when it is running and feel if I do I will mess something up.. So set up the mirror ( easier and quicker) and then if you manage to get an abundance of energy.. change the name. Likely if you are prepared for problems and have energy to fix it ... there won't be any problems. .. at least that is normally how it works.. lol.

 

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...