-
Notifications
You must be signed in to change notification settings - Fork 3
download failing #7
Comments
I have been using this for a couple years as well and am getting the same thing. Did you figure anything out yet? |
Thanks for the comment. You are the only person who has said anything so at least I have confirmation that it is not just my system. I have not heard any reply at all yet at this point. Still stuck |
So from my research I came to the conclusion that this API provided by the church is most likely broken and not supported anymore (IMO. Maybe I'm wrong). So I found & switched to another library and API that works. I've found everything I used to use in this API so hopefully it'll work for you as well. |
Thanks for the information. I went and looked at the new API and found that it seems to work but not for me because I am not an official clerk or leader in the ward so I get "access denied" errors. I did have my son try it with his credentials since he is an Executive Secretary in his ward. He was able to access the move in/out list but the membership list url was returning a "file not found" web page. |
Yah the member list worked for me a couple weeks ago, but this week it’s a
404 for me too.
On Sat, Jul 27, 2019 at 3:42 PM brucegifford ***@***.***> wrote:
Thanks for the information. I went and looked at the new API and found
that it seems to work but not for me because I am not an official clerk or
leader in the ward so I get "access denied" errors. I did have my son try
it with his credentials since he is an Executive Secretary in his ward. He
was able to access the move in/out list but the membership list url was
returning a "file not found" web page.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7?email_source=notifications&email_token=AAC5AYH4ZAGFDG3FDZH5ULTQBS6MDA5CNFSM4HSBAW22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD26TDTY#issuecomment-515715535>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAC5AYC3L6GKJ7JWNZSR2A3QBS6MDANCNFSM4HSBAW2Q>
.
--
Chad Saunders
|
I have been using the module for a couple of years. I pull down latest data every week when preparing the sacrament printed program to validate spellings of names etc. A little over a week ago, things just stopped working. I haven't changed anything in my script. The signin still works but I get a 504 error when downloading the current-user-units json from this url: https://www.lds.org/mobiledirectory/services/ludrs/1.1/unit/mobile/current-user-units
I can see the same error in chrome. The page says:
Gateway Timeout
The proxy server did not receive a timely response from the upstream server.
Reference #1.64321cb8.1559162222.2ec9369
I wondering if anyone can verify if this happens to them as well. I tried it on a second computer with the same results.
If I run lds_org.py (running python3.5.3 under Windows 10) with this command line:
<TITLE>Gateway Timeout - In read </TITLE>-e current-user-units --log -
I see this output:
Connected to pydev debugger (build 191.6605.12)
16314feb9b0 Get endpoints
16314feb9b0 Got 70 endponts
16314feb9b0 SIGNIN BruceGifford https://signin.lds.org/login.html
16314feb9b0 SIGNIN success!
16314feb9b0 GET current-user-units
16314feb9b0 GET https://www.lds.org/mobiledirectory/services/ludrs/1.1/unit/mobile/current-user-units
16314feb9b0 Request Headers {'Accept': '/',
'Accept-Encoding': 'gzip, deflate',
'Connection': 'keep-alive',
'Cookie': 'ObSSOCookie=1R3tfV6XMFTfxkjxtloXYniHszT3yPiY9SBl59ZWRl3S2Nll447STGUdynfypeBzOzd0W9hCguMQPg%2BNmBFWfhVqGkcIO0uaVBF4S80qUM5HOgYikjtIM69kbg3yPihh8%2FVR2BcrMccgPPVR7hLIoKhWuVFJPXBWwWMVc%2Blsr%2FrbF3adcl61UXE%2Fw7sQDSnKvvvlQvLTEWowTVFYORXQWxPNv1XbDTBR6RCfcLnF0V0zkHQ2x8elfuQr0mQ%2BSja0iLgSMm7KAndd7z7V8KBFTo8BIy8E8%2FIhUMC8pzijhLOBMRf9g86PBkTuaQKoJ3Tf; '
'TS01b89640=01999b7023b9ce523d52dfbdcce5707837d40f388ef97a9c2cb1c16f0c10010fa36f6e3da982181d4cf451285436ac498c57b45af2',
'User-Agent': 'python-requests/2.13.0'}
16314feb9b0 response=<Response [504]> length=0
16314feb9b0 Response Headers {'Connection': 'keep-alive',
'Content-Length': '251',
'Content-Type': 'text/html',
'Date': 'Sat, 01 Jun 2019 17:27:22 GMT',
'Expires': 'Sat, 01 Jun 2019 17:27:22 GMT',
'Mime-Version': '1.0',
'Server': 'AkamaiGHost',
'Server-Timing': 'cdn-cache; desc=HIT, edge; dur=240000'}
Error: 504 <Response [504]>
Gateway Timeout
The proxy server did not receive a timely response from the upstream server.Reference #1.bed4c217.1559410042.377831c7
The text was updated successfully, but these errors were encountered: