Can't login anymore

[claneys]

Hi,

either on python 2.7 or 3, i can not login anymore with pygodaddy module. It return false and i have no more clue why.

Thanks to help.

[PointP]

i too had connection problems for 10 hours. It seems like something to do with godaddy and its unstable services. After 10 hours of agony, module works to normal.

[getSurreal]

Mine started failing yesterday and hasn't recovered yet. It runs hourly.

On 6/17/2015 9:10 PM, PointP wrote:

i too had problems with connection for 10 hours. It seems like it is
something to do with godaddy and its unstable services. After 10 hours
of agony, module works back as before.

—
Reply to this email directly or view it on GitHub
#12 (comment).

[xMAC94x]

My last succesfull Domain Record change was on 2015-06-17 4am,
Since 2015-06-18 4am it fails everyday

[getSurreal]

I had mine running from the cron.hourly schedule which was running at 01
minutes of every hour so it's not just 00 they're blocking. I was able
to manually run it at other minutes in the hour. Maybe they tracked IPs
logging in at the same time over and over and blocked that specific
time. Who knows. Hopefully using your random setting will help out a
lot. Thanks for that.

On 6/19/2015 12:30 AM, PointP wrote:

@getSurreal https://github.com/getSurreal i experience same thing
during 2015-06-18 01:00:09,524 Until now. After I test few things
around, i noticed that they cut down 00 minutes connection. Which by
the way, very stupid move from goDaddy. I changed my crontab setting
to something like following and it works just fine. Try it.

*/10 * * * * sleep $(expr $RANDOM % 90); /.../godaddy-dyndns.sh

P.S. you don't have to use random delay on.

—
Reply to this email directly or view it on GitHub
#12 (comment).

[PointP]

I noticed that many deals with none-working script recently.
I told few people about random timing and killing connection from godaddy earier.
However, it turns out something little bit different from what I originally thought.

Here is what is going on with script.

When you use login function from client.py, it goes to "r = self.session.get(self.default_url)"
default_url is "https://dns.godaddy.com/default.aspx" and if you try to connect this address with
anything (web browser and so on...) first connection is always returns the error.

Probably, many already see something like this in their running:

"requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError ..."

This is part where goDaddy just kill your connection.

So how come some of lucky ones able to keep use this script?

If you execute same script one more time right after the first one, it will work just fine.
I think "they" store request information and verify it for next connection until around 15 minutes(not fully tested... around that area for sure) or so.

That is why "hourly" people just simply not worked at all... I feel sorry to you guys...

Here is what i come up with

I would do something like this in client.py line 99

    for i in range(0, 10):
        while True:
            try:
                r = self.session.get(self.default_url)
            except:
                time.sleep(1)
                continue
            break

instead of

    r = self.session.get(self.default_url)

As you can see, it is just looping until connection works. That is very much all of it

Good luck to all.

[getSurreal]

Thanks for that update recommendation. Wouldn't it also be better to only login if the record actually needs to be updated?

Thanks,
James

On Jun 23, 2015, at 4:22 AM, PointP notifications@github.com wrote:

I noticed that many deals with none-working script recently.
I told few people about random timing and killing connection from godaddy earier.
However, it turns anout something little bit different from what i originally thought.

Here is what is going on with script.

When you use login function fro client.py, it goes to "r = self.session.get(self.default_url)"
and default_url is "https://dns.godaddy.com/default.aspx" and if you try to connect this address with
anything (webbrowser and so on...) first connection is always returns the error.

Probably, many already see something like this in their running:

"requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError ..."

This is part where goDaddy just kill your connection.

So how come some of lucky ones able to keep use this script?

If you execute same script one more time right after the first one, it will work just fine.
I think they store request infomation and vertify it for next connection for around 10 minutes(not fully tested... around that area for sure) or so.

That is why "hourly" people just simply not worked at all... I feel sorry to you guys...

Here is what i come up with

I would do something like this in client.py line 99

for i in range(0, 10):
    while True:
        try:
            r = self.session.get(self.default_url)
        except:
            time.sleep(1)
            continue
        break

instead of

r = self.session.get(self.default_url)

As you can see, it is just looping until connection works. That is very much all of it

Good luck to all.

—
Reply to this email directly or view it on GitHub.

[PointP]

@getSurreal Yeap it does that already. Update suggestion line is connection verification part of login function. Cheers.

[getSurreal]

@PointP when I was getting failures every hour, my IP had not changed so that makes me believe it tries to login every time.

Thanks,
James

On Jun 23, 2015, at 8:40 PM, PointP notifications@github.com wrote:

@getSurreal Yeap it does that already. Update suggestion line is connection verification part of login function. Cheers.

—
Reply to this email directly or view it on GitHub.

[ggogel]

Hey,

I'm trying to set up an update script for hours until i found this issue thread. I edited the client.py as @PointP suggested, but authentification is still not working for me. Any suggestions to fix this issue? I recently moved to godaddy and dyndns would be really nice.

Thanks in advance

[ggogel]

This is how I solved it:
Log into godaddy with a browser on pc with the same external ip as the server and then run the script. Now pygodaddy can login and change the A record. To keep it up working, i think you have to run the script every 5min or so. It's working with and without the suggested fix from @PointP.

[PointP]

@gerrit507 sorry for late reply on your comment. Tour approach is valid as well. For me, validation time is longer than 5 minutes. Well anyway main idea is run script twice in a row

[ggogel]

@PointP run script twice in a row does not work for me. I had to log into godaddy in a browser via the same external ip as the server has, otherwise there was no authentifaction possible via the script, even with 10 attempts in a row. Maybe somebody can reproduce this issue...

[dawg6]

Even after logging in from web browser, the script is failing. I've tried running multiple times as well, to no avail. This just started happening for me within the last 24 hours (8/21/15).

Edit: here is the output showing where it is failing now.

ERROR:pygodaddy.client:Login routine broken, godaddy may have updated their login mechanism
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/pygodaddy/client.py", line 101, in login
    viewstate = re.compile(r'id="__VIEWSTATE" value="([^"]+)"').search(r.text).group(1)
AttributeError: 'NoneType' object has no attribute 'group'

[runnerway]

@dawg6 Same problem here!

[antst]

Same problem. godaddy definitely changed their login mechanism.
Does somebody maintain this code nowadays?