Problems with LCR Finance and MLS Transmit

Is anyone else having trouble using the LCRF (Finance) site or doing MLS transmit of finance information?

All 3 wards in our building in Salt Lake City have been broken for the last 3 weeks, unable to transmit in MLS. It just hangs. The rest of the internet works fine, it's just the MLS transfer and LCRF sites. Trying to use the LCRF site is unbearable. If you can get logged in at all, every 3rd click breaks and give the message:

Uh oh! We're Sorry ... It looks like something went wrong which prevented the page you requested from displaying. Sorry for any inconvenience that this may have caused!"

I thought it was just the building internet, but I see the same problem at home, with a different computer, on a different internet connection. It's not just my account, because other wards are seeing the same problem. The only common factor is that the building and my home internet both use CenturyLink/Qwest internet.

So I joined the church computer to my phone hotspot instead (T-Mobile), and the problem was immediately fixed - MLS could transmit and LCRF worked great. This is a great workaround in the short term.

If the problem is with CenturyLink/Qwest, then it must be affecting many others. Who else is seeing this?

We're having a similar issue with one of our buildings. Last week I took the stake computer to another building and it worked just fine there. This week using my phone as you did it is working fine where it wouldn't work before. It will transmit a few files and then hang or timeout. With one of the wards I got it to work by trying over and over, but it was painful.

The problem isn't globally CenturyLink/Quest because all 4 of our buildings use them for their internet provider and only one building is having troubles.

Do you know if the MLS transmission is done via the VPN? Perhaps there's a VPN issue with some buildings.

I did not think an MLS Send/Receive was possible or even authorized on any networks that did not use the church VPN. Many years ago, we had a few admin computers using a wireless connection, because the FM had not yet run Ethernet to those offices. Unfortunately, the neighborhood Wi-Fi was using the same channel as the meetinghouse Wi-Fi, and the neighbor's signal was stronger. So the clerks decided to connect to the neighbor's open Wi-Fi signal. We received several nasty messages about doing an MLS Send/Receive over an open wireless connection, outside of the meetinghouse VPN.

drepouille wrote:I did not think an MLS Send/Receive was possible or even authorized on any networks that did not use the church VPN. ... We received several nasty messages about doing an MLS Send/Receive over an open wireless connection, outside of the meetinghouse VPN.

As your own experience attests, you can, but it will be noticed. I tend to suspect enforcement isn't terribly consistent, or perhaps only the guilty party sees it.

Anyway, I was trying to figure out why MLS transmission would be an issue in the meetinghouse. The firewall is one of the big differences. It wouldn't hurt to reboot it. I'd also check to see if the DNS the clerk's computer is using is correct.

Absolutely. Rebooting the firewall is my first choice, especially if the VPN light is off. Oh wait, does the Meraki even have a VPN light?

Checking the DNS on the admin computer is also a good step. There is no telling who has been messing around with that.

drepouille wrote:Absolutely. Rebooting the firewall is my first choice, especially if the VPN light is off. Oh wait, does the Meraki even have a VPN light?

The simple answer is No VPN light!

Biggles wrote:The simple answer is No VPN light!

Correct. All you have is one lights that kind of a dim "white" when everything is normal.

I investigated this more today. We're seeing this problem from multiple church buildings and from several home internet connections in the area, but only from Centurylink internet connections. If we connect to a non-Centurylink provider, the problem goes away.

The problems are worse than just getting to LCRF. They include several other web sites that we've noticed:

• donations.churchofjesuschrist.org
  lcrf.churchofjesuschrist.org
  k12.com
  americafirst.com
  ksl.com

If I run tracert to any of the problem sites, I see that they are all hosted on level3.net (Comcast). So it looks like a problem between Centurylink and Level3, but maybe only local to this area of Salt Lake City.
I called CenturyLInk today and they said there is a similar problem in our local area and that they are working on it, but I'm not confident that it's the same problem, especially since it's been going on for weeks. I'll give them a couple of days and then call back if it's not fixed.

bsaajm wrote:I investigated this more today. We're seeing this problem from multiple church buildings and from several home internet connections in the area, but only from Centurylink internet connections. If we connect to a non-Centurylink provider, the problem goes away.

The problems are worse than just getting to LCRF. They include several other web sites that we've noticed:

• donations.churchofjesuschrist.org
  lcrf.churchofjesuschrist.org
  k12.com
  americafirst.com
  ksl.com

If I run tracert to any of the problem sites, I see that they are all hosted on level3.net (Comcast). So it looks like a problem between Centurylink and Level3, but maybe only local to this area of Salt Lake City.

Code:

Tracing route to lcrf.churchofjesuschrist.org [216.49.176.123] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.108.1
  2    <1 ms    91 ms    93 ms  slcy-dsl-gw16.slcy.qwest.net [207.108.176.16]
  3    57 ms    63 ms    81 ms  slcy-agw1.inet.qwest.net [207.108.177.121]
  4    98 ms    53 ms    31 ms  4.68.38.161
  5     *        *        *     Request timed out.
  6   108 ms   114 ms   117 ms  corporation.bar1.saltlakecity1.level3.net [4.35.168.14]

I called CenturyLInk today and they said there is a similar problem in our local area and that they are working on it, but I'm not confident that it's the same problem, especially since it's been going on for weeks. I'll give them a couple of days and then call back if it's not fixed.

Can I ask roughly what area of Salt Lake is your units? I'm pretty much dead in the water here by the salt lake fairgrounds. I do not live in this area but serve there at a branch for a correctional center and I can't submit at all using MLS it just spins. Called helpline and was told after an hour that after restarting the firewall the VPN and things seemed to work slowly. This was when no one was at the branch so on a Sunday I'm pretty sure it grinds to a halt. We have CenturyLink I was informed by the tech from the helpline. A brother serving here at the branch lives in the area and has CenturyLink and is having issues as well.

The stake technology specialist submitted a FIR to the FM group to have them look at the issue but who knows how long that will take and if that's the right route even.


Did your issues get resolved??

Thanks
--

We're in the East Millcreek area - 3900 S 2300 E. All the wards in the 2 nearby buildings are having this problem. Several of the neighbors are having similar problems.
I called CenturyLink again today, and of course they had lost my ticket and weren't working on it. So I gave them all the information again and made them triple check it and give me a new ticket number. They say they are working on it now. They told me to call back in the morning to get an update. Hopefully they will figure something out. I'll keep hounding them.

Problem is not resolved. Our stake center address is about 2300 E and 3900 S in Salt Lake City, UT. I have a CenturyLink gigabit connection in my home and have the same problems. If I use the developer tools of the Chrome browser I see the following:

(index):1 A cookie associated with a cross-site resource at http://boncom.demdex.net/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
(index):1

A cookie associated with a cross-site resource at http://demdex.net/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
(index):1

A cookie associated with a cross-site resource at http://dpm.demdex.net/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
(index):1

A cookie associated with a cross-site resource at http://everesttech.net/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.
print-9d9da5ac.css:1

Failed to load resource: net::ERR_CONNECTION_CLOSED
donor-libs-4c04da14.js:1

Failed to load resource: net::ERR_NETWORK_IO_SUSPENDED
donor-app-d5e43ef6.js:1

Uncaught Error: Cannot find module 'angular'
at s (donor-app-d5e43ef6.js:1)
at donor-app-d5e43ef6.js:1
at Object.15.angular (donor-app-d5e43ef6.js:4)
at s (donor-app-d5e43ef6.js:1)
at e (donor-app-d5e43ef6.js:1)
at donor-app-d5e43ef6.js:1
help-module-607e5353.js:1

Uncaught Error: Cannot find module 'angular'
at s (help-module-607e5353.js:1)
at help-module-607e5353.js:1
at Object.3../help-controller.js (help-module-607e5353.js:1)
at s (help-module-607e5353.js:1)
at e (help-module-607e5353.js:1)
at help-module-607e5353.js:1
directive-module-2d28ff56.js:1

Uncaught Error: Cannot find module 'angular'
at s (directive-module-2d28ff56.js:1)
at directive-module-2d28ff56.js:1
at Object.52../add-bank-account-angola-directive.js (directive-module-2d28ff56.js:10)
at s (directive-module-2d28ff56.js:1)
at e (directive-module-2d28ff56.js:1)
at directive-module-2d28ff56.js:1
error-module-925c1de7.js:1

Uncaught Error: Cannot find module 'angular'
at s (error-module-925c1de7.js:1)
at error-module-925c1de7.js:1
at Object.2../general-error-controller.js (error-module-925c1de7.js:1)
at s (error-module-925c1de7.js:1)
at e (error-module-925c1de7.js:1)
at error-module-925c1de7.js:1
access-module-c7f67176.js:1

Uncaught Error: Cannot find module 'angular'
at s (access-module-c7f67176.js:1)
at access-module-c7f67176.js:1
at Object.3../access-controller.js (access-module-c7f67176.js:1)
at s (access-module-c7f67176.js:1)
at e (access-module-c7f67176.js:1)
at access-module-c7f67176.js:1
history-module-d9a3e50b.js:1

Uncaught Error: Cannot find module 'angular'
at s (history-module-d9a3e50b.js:1)
at history-module-d9a3e50b.js:1
at Object.4../history-controller.js (history-module-d9a3e50b.js:2)
at s (history-module-d9a3e50b.js:1)
at e (history-module-d9a3e50b.js:1)
at history-module-d9a3e50b.js:1
service-module-2d17cf55.js:1

Uncaught Error: Cannot find module 'angular'
at s (service-module-2d17cf55.js:1)
at service-module-2d17cf55.js:1
at Object.13../agency-service.js (service-module-2d17cf55.js:4)
at s (service-module-2d17cf55.js:1)
at e (service-module-2d17cf55.js:1)
at service-module-2d17cf55.js:1
welcome-module-f991da53.js:1

Uncaught Error: Cannot find module 'angular'
at s (welcome-module-f991da53.js:1)
at welcome-module-f991da53.js:1
at Object.3../welcome-controller.js (welcome-module-f991da53.js:1)
at s (welcome-module-f991da53.js:1)
at e (welcome-module-f991da53.js:1)
at welcome-module-f991da53.js:1
agency-module-86022f86.js:1

Uncaught Error: Cannot find module 'angular'
at s (agency-module-86022f86.js:1)
at agency-module-86022f86.js:1
at Object.4../agency-controller.js (agency-module-86022f86.js:1)
at s (agency-module-86022f86.js:1)
at e (agency-module-86022f86.js:1)
at agency-module-86022f86.js:1
reports-module-2083fa2c.js:1

Uncaught Error: Cannot find module 'angular'
at s (reports-module-2083fa2c.js:1)
at reports-module-2083fa2c.js:1
at Object.3../reports-controller.js (reports-module-2083fa2c.js:1)
at s (reports-module-2083fa2c.js:1)
at e (reports-module-2083fa2c.js:1)
at reports-module-2083fa2c.js:1
donation-module-9174796b.js:1

Uncaught Error: Cannot find module 'angular'
at s (donation-module-9174796b.js:1)
at donation-module-9174796b.js:1
at Object.5../agreement-step-controller.js (donation-module-9174796b.js:2)
at s (donation-module-9174796b.js:1)
at e (donation-module-9174796b.js:1)
at donation-module-9174796b.js:1
settings-module-a79e9f32.js:1

Uncaught Error: Cannot find module 'angular'
at s (settings-module-a79e9f32.js:1)
at settings-module-a79e9f32.js:1
at Object.3../settings-controller.js (settings-module-a79e9f32.js:2)
at s (settings-module-a79e9f32.js:1)
at e (settings-module-a79e9f32.js:1)
at settings-module-a79e9f32.js:1
prewelcome-module-0fa302b5.js:1

Uncaught Error: Cannot find module 'angular'
at s (prewelcome-module-0fa302b5.js:1)
at prewelcome-module-0fa302b5.js:1
at Object.3../prewelcome-controller.js (prewelcome-module-0fa302b5.js:1)
at s (prewelcome-module-0fa302b5.js:1)
at e (prewelcome-module-0fa302b5.js:1)
at prewelcome-module-0fa302b5.js:1
filter-module-76edb53d.js:1

Uncaught Error: Cannot find module 'angular'
at s (filter-module-76edb53d.js:1)
at filter-module-76edb53d.js:1
at Object.1../status-filter.js (filter-module-76edb53d.js:1)
at s (filter-module-76edb53d.js:1)
at e (filter-module-76edb53d.js:1)
at filter-module-76edb53d.js:1
s-code-contents-a2f7173c619738f8dc11f935a4056d23c9affa42.js:1

Failed to load resource: net::ERR_NETWORK_IO_SUSPENDED
utag.3.js:1

Failed to load resource: net::ERR_NETWORK_IO_SUSPENDED
(index):146

Registration failed: DOMException: Failed to register a ServiceWorker: The origin of the provided scriptURL ('https://www.churchofjesuschrist.org') does not match the current origin ('https://donations.churchofjesuschrist.org').
(anonymous) @ (index):146

Additional details:
From inside Technology Manager (tm.churchofjesuschrist.org) the firewall device for our building has a status of "Warning/VPN down." The firewall status for other buildings in our stake shows status of "Online."

Could this be part of our problem?

4 more calls/chats later and I'm giving up on CenturyLink support. I can't penetrate the bureaucracy. They keep trying to tell me to reboot my modem/computer. I can't figure out how to get past Tier 1 support.

Instead, I called the LDS global service center tonight. They were more helpful. I passed along all the information and they are going to look at it. Maybe they can fix it from their end, or help apply pressure to CenturyLink to fix it.

davidanderspatten wrote:Additional details:
From inside Technology Manager (tm.churchofjesuschrist.org) the firewall device for our building has a status of "Warning/VPN down." The firewall status for other buildings in our stake shows status of "Online."

Could this be part of our problem?

It's certainly a starting point. I'd power cycle the firewall (preferably when there isn't a lot of people in the building). While you're at it, might as well power cycle the modem as well. Stranger things have happened.

I reset all the network hardware this morning. Status of the FIREWALL in Technology Manager portal now shows as ON-LINE.

Dave, thanks for resetting the VPN. Unfortunately, I just tested things out from the church computer and it's still pretty broken. MLS gets stuck during transmit, tm times out, I can't even log into lcrf. KSL.com is still getting stuck frequently. So it looks like we still have the problem. I'm still waiting for a response from LDS global services.

It's a miracle! It all seems to be working tonight, both from the Stake Center and from my house - donations, lcrf, ksl.com, facebook, etc. All the delays and hangs are gone and it seems to be working! Centurylink must have fixed something finally.

Hopefully it's fixed for good. I'll keep an eye on it over the next week.