lds.org will not open

I use Chrome browser and up to about three days ago I had no problem accessing lds.org ... but recently, lds.org goes into a lengthy (couple of minutes) loading phase ultimately culminating in a window popping up with a header "Page(s) Unresponsive" and futher notes "The following page(s) are unresponsive. You can wait for them to become responsive or kill them." The Church lds.org icon is shown followed by the website name "The Church of Jesus Christ of Latter-day Saints". There are two button options below: "Kill Files" or "Wait". Neither button option leads to my being able to access the site; however, if I go back to my Chrome icon and select "new incognito window", I am then able to access lds.org without any problem. I have uninstalled/reinstalled Chrome and deleted back data. Can you help?

I'm having a similar problem in Chrome on a Mac. CPU goes to 95% on Google Chrome Renderer. Mostly the problem is on the lds.org home page.

I'm not having any problems with Chrome on a PC. I've even tried Incognito mode. Are you running some kind of security software that might interfere with the webpage?

Is your problem that the zoom is not set at 100% for lds.org? See Can't zoom lds.org homepage in Chrome; breaks it

This also happened to my page becoming unresponsive, it just would not open. I use chrome as my browser. I phoned a friend who suggested to click the top right box to customize things, then go to 'tools' in the drop down menu and then clear browsing data. click all the boxes and start it from'the beginning of time'. I did this, and now lds.org opens fine.

We have confirmed that this is the zoom issue mentioned. We had sporadic reports of chrome crashes but couldn't reproduce it. Whoda thunk that zooming would be the reason (apparently not us).

No clue what it is (as I've never seen a zoom related crash issue before) but we have something to go on and can start digging into it.

I think we have fixed this, although there may be a bit of a lag in getting the file cleared from our caches.

Make sure to clear your cache (don't need to worry about cookies) before going back to the page otherwise you will get locked up again before your browser has a chance to look for the updated file.

Give it a try and let me know.

BarkerAJ wrote:Give it a try and let me know.

Yes, that seems to have fixed it. I could reproduce the problem at will previously, and now it works fine.

Working straight for me as of right now (I came to the forum to check on this issue). Comes as a relief to someone who runs her browser with 110% zoom (middle-aged eyes, plus need to update my glasses).

Great job. Zoom in Chrome works fine for me now.

My browsers Chrome & Firefox will not load lds.org correctly. The only site I am having trouble with, this is on multiple devises. laptop, pc, tablet. When signing in it opens but not in a normal way. I can still function but it is not a good experience. It is all text with links with no or very little pictures. The text are all links. I made an effort to clear cache, permission for cookies, and reset the browser. I do not understand what you are saying about the zoom.

Any help or ideas I should try? Thank You.

1968leocomeeatabite wrote:I do not understand what you are saying about the zoom.

With the browser open there is an icon on the far right on the same line as the web page address line. It looks like three horizontal lines vertically stacked. That is the browser options menu link. In the third group of options is the zoom control option. If it is not showing 100% then users were experiencing the issues described in this thread. This issue has been fixed.

Since you said both the Chrome and Firefox browsers were experiencing loading issues for LDS.org then it most likely is not the browsers but something on the server side. There were issues with LDS.org earlier in the week with delayed loading. Those issues have also been fixed.

If you are still having problems then provide some more detail as to what your are experiencing. You can also try clearing your cache and then try loading LDS.org again.

I have been having troubles loading LDS.ORG
On my PC it seems to be getting little bite worse as time goes on.
I assume that it is a problem with something in my home. 2 PC, 1 Laptop, 1 tablet will not load lds.org correctly. I have cleared my cache, cookies, history, etc, on my one PC. It did not help. I cleared it on both firefox and chrome. I tried loading lds.org with three browsers including internet explorer. lds.org is only site that I am having troubles with. I can access al may other sites.

I have Firebug on my laptop and I do not understand anything about it but here is a quote that I copied from "Firebug"

<!DOCTYPE html>
<html class="js flexbox canvas canvastext webgl touch geolocation postmessage no-websqldatabase indexeddb hashchange history draganddrop websockets rgba hsla multiplebgs backgroundsize borderimage borderradius boxshadow textshadow opacity cssanimations csscolumns cssgradients no-cssreflections csstransforms no-csstransforms3d csstransitions fontface video audio localstorage sessionstorage webworkers applicationcache svg inlinesvg smil svgclippaths wf-acme-n4-active wf-active">
<head version="2.5.4-rev.3769">
<body id="signedin" class="fluid mainPage no-resize">
</html>

This has been going on for about a week. I can load ldstech just fine. I go over to the clerks office and lds.org works just fine over there.

A few things are different I have added a tablet to my devices with some newly loaded apps. I can't access lds.org on the tablet, but I have previously. I can access lds tools just fine. Would there be a connection with the beta leadership resources page? I am in the area that has the beta for leadership resources. Well have I given to much information? Can anyone help me?

Have you tried taking your laptop or tablet to another location (such as church) and see what happens there? I'm wondering if it's something with your router or ISP.

I will try that this morning. I think that you might be on to something. I used them both at the church last sunday and they both worked. I do have a sisco (?) router. Thank you, so if it works OK at the church and it does not at home, what do I do? Is there a reset? Or should I just unplug the router and then plug it back in and let it go through the process of connecting?

1968leocomeeatabite wrote:Thank you, so if it works OK at the church and it does not at home, what do I do? Is there a reset? Or should I just unplug the router and then plug it back in and let it go through the process of connecting?

Not sure what to suggest. But a reset wouldn't be a bad idea.

My one concern is that the church network is "internal" to the church. A better test would be to find a non-church WiFi and see how that works. Such as going to a store that offers free WiFi.

But the fact it works at church does suggest it's a connection related issue.

russellhltn wrote:

1968leocomeeatabite wrote:Thank you, so if it works OK at the church and it does not at home, what do I do? Is there a reset? Or should I just unplug the router and then plug it back in and let it go through the process of connecting?

My laptop and my tablet worked great at the church. I came home and decided that It would not hurt anything if I unplugged my router for a while and then plugged it back in, just to see if that by chance might work. IT WORKED GREAT! not sure why it worked but it did? Any suggestions of what to look for in the future?

My one concern is that the church network is "internal" to the church. A better test would be to find a non-church WiFi and see how that works. Such as going to a store that offers free WiFi.

I have not had a chance to test this. I will make it a point to do so in the future.

Question: I have been Leary of using WiFi in a public place and going into some of the tools (especially the Clerk or leader resources pages. Is this a valid concern, or am I being to cautious? Would this be in the same category of not doing any bank business when connected to a b public wifi? Would it be best not to even log into lds.org when in a public place?

But the fact it works at church does suggest it's a connection related issue.

So by what I experienced would it be an issue with my router?
Thank you for your help!!

1968leocomeeatabite wrote:I came home and decided that It would not hurt anything if I unplugged my router for a while and then plugged it back in, just to see if that by chance might work. IT WORKED GREAT! not sure why it worked but it did? Any suggestions of what to look for in the future?

The key thing for me is you were having problems with multiple devices in your home, and no one else was complaining about a problem. The connection was something in common to the devices, but to no one else.

1968leocomeeatabite wrote:Question: I have been Leary of using WiFi in a public place and going into some of the tools (especially the Clerk or leader resources pages. Is this a valid concern, or am I being to cautious? Would this be in the same category of not doing any bank business when connected to a b public wifi? Would it be best not to even log into lds.org when in a public place?

It's good to be cautious, but I can't think of what would be dangerous at a public place. It seems to me that church members could make better use of stolen information then your typical coffee shop hacker.

1968leocomeeatabite wrote:So by what I experienced would it be an issue with my router?

Or at least something with your connection. The router being one of the few parts being under your control. It's possible it was forwarding outdated DNS information. Resetting it forced it to get current information from your ISP.

A big thank you to russellhltn for his insight and suggestions. I do appreciate it.

One thing that has changed with this experience. Or at least I perceive that it may be different.

Would there be a connection with the beta leadership resources page? I am in the area that has the beta for leadership resources.

In this Quote I was referring to the beta given to (I think) the leadership in my area. I live in Payson, Utah. If I remember correctly we were changed to beta "Leadership Resources" and 'Clerk Resources". But maybe it was only Clerk Resources I honestly do not remember. I think that we had tho option to change back and forth as we pleased. But now I do not see the beta or the beta option. I guess the time could have expired and I was not aware.

1968leocomeeatabite wrote:In this Quote I was referring to the beta given to (I think) the leadership in my area. I live in Payson, Utah. If I remember correctly we were changed to beta "Leadership Resources" and 'Clerk Resources". But maybe it was only Clerk Resources I honestly do not remember. I think that we had tho option to change back and forth as we pleased. But now I do not see the beta or the beta option. I guess the time could have expired and I was not aware.

The beta only applied to Clerk Resources (not Leader Resources). And the new experience is now live for everyone, so there is no longer a separate beta version of Clerk Resources.

russellhltn wrote:

1968leocomeeatabite wrote:I came home and decided that It would not hurt anything if I unplugged my router for a while and then plugged it back in, just to see if that by chance might work. IT WORKED GREAT! not sure why it worked but it did? Any suggestions of what to look for in the future?

The key thing for me is you were having problems with multiple devices in your home, and no one else was complaining about a problem. The connection was something in common to the devices, but to no one else.

Over a year and a half has passed by and the identical situation has happened. LDS.ORG would not open / load on my PC. (when other sites would) So I shut all pc and devices down unplugged the modem waited for a couple minutes and plugged the modem in, let it cycle, boot up my PC and were back up and running again. I don't understand it but at least it make things all better. I assume it has something to do with resetting the modem and the modem needing to reach out to lds.org and makes things work again.

Thank you for the help. I have been having the same problem since Mon. and wondered what was going on because if I went into FireFox it worked fine. Now with your help it is functioning just fine.

I have my Dell laptop at the meetinghouse, running Windows 7 Ultimate and Chrome. When I try to go to lds.org, I see a message at the bottom of the Chrome window: "Waiting for ldschurch.tt.omtrdc.net" The web page is frozen, and times out after a minute or two when Chrome pops up a message that lds.org is unresponsive, and suggests I kill the attempt to load the web page.

We have a Cisco 800 Series firewall and a Windstream DSL modem. This only happens when I use a wireless connection. If I connect an Ethernet cable from the firewall to my laptop, and disable my wireless adapter, the laptop can connect immediately to lds.org. Internet Explorer 11 can also connect to lds.org immediately, regardless of whether I use wireless or wired connections.