Site access problem

[oca]

On my iphone, it *seeems* that the problem occurs more ofen with chrome then with safari...

[jug]

I have also connection problems (from Germany) since a few days. I open this forum with a direct link to the unread-posts, but it always leads to a page-not-found (also on repeated reloads).
Strangely though is, when I then enter then over the main-page and doing the 2-3 clicks to go from there to the unread-posts it works (auto-login enabled BTW).

Need to observe it more for common patterns (like the aforementioned DNS), so far this feels like a balancer put me on a non-functioning cluster-node, but I guess L19 does not use balancing/clustering, no?
So far this is a tad inconvenient (and a bit annoying).

Have something changed in the architecture / software / infrastructure ?

[HermanHiddema]

I've not had any problems at all.


As to the technology behind it:

The number (50.62.100.1) associated with a domain name is called the IP address. Due to the scarcity of IP addresses (only some 4 billion), there are not enough addresses for all domain names. Therefore, many domains share the same IP address with other domains, and your web browser must tell the web server which of those domains it wants to access. That means that, unless lifein19x19.com has a unique IP address and the web server is configured to serve only that site, approaching L19 by IP address will not work. Uberdude's experience shows that it is indeed not possible.

That also means that google can not, and does not, link to the IP address directly. Therefore the site should not be more available, or faster, when linking via google search results.

To improve the response time for looking up the IP address, you can use kusto's solution. Note, however, that should lifein19x19 ever change IP address, that that solution will mean you cannot reach lifein19x19 at all any more until you remove the entry from your hosts file again.

[Jordus]

The issue is definitely DNS related. Our current setup does not have a dedicated IP. Also it is not accessible by IP alone. More than likely the server IP was changed and DNS's are playing catch up to update their tables. When this happens it can take a few days for all of them to catch up.

We can change the setup to have a dedicated IP if we like. It would change our upkeep costs but would resolve any issues with DNS's lagging behind everytime the IP is changed. Or at least allow access via IP if for some reason the DNS that you are running will not resolve the address correctly.

[Bonobo]

Oh, JUST now (14:00—14:30 German Time) I got the following on this thread and on another one:

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator and inform them of the time the error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Apache Server at http://www.lifein19x19.com Port 80

Greetings, Tom

[skydyr]

I had the same problem recently.
You can fix it by adding this line to your hosts file on whatever device you are accessing the website from.

Code: Select all

50.62.100.1 lifein19x19.com

Example Instructions: http://www.howtogeek.com/howto/27350/be ... osts-file/

Also, if your i-devices are jail-broken then you can do the same. This would be done by accessing /etc/hosts with a program like iFile for example.

This is kind of a band-aid solution but I hope it helps someone none the less.

Please please please don't modify your hosts file unless you really know what you are doing. It can cause a lot of weird and problematic behavior, and may prevent you from getting to the site in the future if the IP address ever changes. This is not entirely unlikely, and by that point, you will likely have forgotten that the file was modified and be tearing your hair out because it works for everyone else.

[betterlife]

Please please please don't modify your hosts file unless you really know what you are doing. It can cause a lot of weird and problematic behavior, and may prevent you from getting to the site in the future if the IP address ever changes. This is not entirely unlikely, and by that point, you will likely have forgotten that the file was modified and be tearing your hair out because it works for everyone else.

Then what is the solution? To answer here costs my about 10 to 15 minutes. I get a time-out 4 out 5. I get 500 Error-Messages all the time.

I read lifein19x19.com mostly through my webbased rss-reader, where all works fine but as soon as i come here to search something or write something i lose a lot of unnecessary time...

Please, please change something. Is it the hoster? Are you using godaddy.com ... ?! Just do something.

[virre]

Please please please don't modify your hosts file unless you really know what you are doing. It can cause a lot of weird and problematic behavior, and may prevent you from getting to the site in the future if the IP address ever changes. This is not entirely unlikely, and by that point, you will likely have forgotten that the file was modified and be tearing your hair out because it works for everyone else.

Then what is the solution? To answer here costs my about 10 to 15 minutes. I get a time-out 4 out 5. I get 500 Error-Messages all the time.

I read lifein19x19.com mostly through my webbased rss-reader, where all works fine but as soon as i come here to search something or write something i lose a lot of unnecessary time...

Please, please change something. Is it the hoster? Are you using godaddy.com ... ?! Just do something.

While it is a risk, especially if the IP is likely to have frequent changes, the risk and problems will be very limited, and as long as you remember that you changed the host file it will not be any big risk.

(As a webbdeveloper in my professional life, my hosts file is filled with rewrites-.)

Although it is always best to avoid doing it. Though the sugested change to a stable IP would be the best solution. (Acctually the best solution, but probably too expensive is a ip to a load balancer, which then routes traffic to app-server(s). As 500 errors also can be code and speed issues. Also the fact that you get a 500 error means you reach the server, and the server logs should say what happened, so depending on what type of hosting, the log should be available))