lotus_blossom__
Experienced
- Joined
- Dec 11, 2019
- Posts
- 68
Woohoo it's back
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
the problem is not DNS, the problem is piss poor planning. They went live and clearly didn't test and note issues. there is another IP for them 216.150.65.190 and same issues. the chat.literotica.com is a sub domain and you can not access them direct by IP. Looks like the same issue as the profiles which was somebody moved them to another folder and failed to update the links. Looks like same kind of issue here. we techs refer to this as P.I.C.N.I.C. Problem In Chair Not In Computer. or a failure of the interface between the chair and keyboard. I would never leave a site crippled this way. I would and do test first. The one time a problem came up after test I just restored the backup and postponed the roll out until it was fixed. Solution takes a couple minutes.For those of you who are able to access the site, are there any of you tech savvy enough to be able to provide the IP address of the chat.literotica.com server? When I look this up I get
216.150.65.200 however this only seems to resolve to the main Lit menu page. When I click on Erotic Chat link I get the site can't be found error.
Thanks for providing that explanation. Any ideas why chat now seems to be back up for some users and not others?the problem is not DNS, the problem is piss poor planning. They went live and clearly didn't test and note issues. there is another IP for them 216.150.65.190 and same issues. the chat.literotica.com is a sub domain and you can not access them direct by IP. Looks like the same issue as the profiles which was somebody moved them to another folder and failed to update the links. Looks like same kind of issue here. we techs refer to this as P.I.C.N.I.C. Problem In Chair Not In Computer. or a failure of the interface between the chair and keyboard. I would never leave a site crippled this way. I would and do test first. The one time a problem came up after test I just restored the backup and postponed the roll out until it was fixed. Solution takes a couple minutes.