Comments for Stuart's Weblog

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Stuart

Stuart — Fri, 24 May 2013 21:45:22 +0000

@Ruediger: My bad, I was thinking of the GNU '--tmpdir' option (which you'll likely be missing if you're on Red Hat or not-Linux). Change the first line to: [code lang="bash"]FILE="$( mktemp -t "$( basename "$0" ).XXXXXXXX" )" || { echo >&2 "mktemp failed: $?" ; exit 1 ; }[/code]

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Ruediger

Ruediger — Fri, 24 May 2013 20:05:25 +0000

sorry, does not work for me:

DEBUG: Fetching UID...
DEBUG: Read UID as 'EDE102E60F53B36775683E66566F5307B2' - posting data...

302 Found

Found
The document has moved .

DEBUG: Response received - verifying result...
mktemp: invalid template, `./dyndns.sh.XXXXXXXX', contains directory separator
mktemp failed: 1

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Stuart

Stuart — Thu, 23 May 2013 21:00:02 +0000

@Peterkneter: D’oh!

I don’t actually know that you can change the language – it just struck me that if “Welcome” is localised then it might explain why people are having problems

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Stuart

Stuart — Thu, 23 May 2013 20:57:35 +0000

To everyone who’s having problems:

It does look as if the authentication has actually been successful, but the check afterwards is failing.

To help to diagnose this, please update the final line of the original script to:

FILE="$( mktemp -t "$0.XXXXXXXX" )" || { echo >&2 "mktemp failed: $?" ; exit 1 ; }
curl -b $COOKIES -c $COOKIES -e "$POSTURL" -kso - -A "$UA" --url "$CHKURL" -o "$FILE"
if grep -q "Welcome $LOGIN"; then
    echo "Login successful"
else
    echo >&2 "Login failed"
    grep -q "Welcome " "$FILE" && echo "Page contains 'welcome' string"
    grep -q "$LOGIN" "$FILE" && echo "Page contains username"
    PATTERN="[^&]+ [^<]+"
    grep -Eq "$PATTERN" "$FILE" && echo "Page contains welcome pattern $( grep -Eo "$PATTERN" "$FILE" )"
    echo "Checks complete"
fi
rm "$FILE"

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Peterkneter

Peterkneter — Thu, 23 May 2013 20:52:56 +0000

I found my problem. I used my E-Mail address instead of the username. Now it is working fine.

@Stuart:
Where can I change the language at dyn.com?

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Ruediger

Ruediger — Thu, 23 May 2013 19:47:52 +0000

@Stuart
used debug for successful account and failing one. Here only debug info:
———————————

DEBUG: Fetching UID...
DEBUG: Read UID as '4C963E4A20D55590832C8FE2878B545698' - posting data...


302 Found

Found
The document has moved here.

DEBUG: Response received - verifying result...
Login successful

———————–
———————–

DEBUG: Fetching UID...
DEBUG: Read UID as '3069D920308CF60A496C87B9DCCBC83CAC' - posting data...


302 Found

Found
The document has moved here.

DEBUG: Response received - verifying result...
Login failed

——————-

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Stuart

Stuart — Thu, 23 May 2013 19:19:29 +0000

@silverdulcet:

DEBUG=1 ./dyndns-login.sh

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by silverdulcet

silverdulcet — Thu, 23 May 2013 09:09:35 +0000

I see the DEBUG lines in the script. How would I enable them to see if I can find where the error is.

The usernames of the 2 accounts I tried are 9 and 12 characters, just regular letters no numbers or special characters. Language is set to en-US.

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Stuart

Stuart — Thu, 23 May 2013 08:54:10 +0000

@Peterkneter: 'Found' *is* the correct response at this stage - the final check is a dumb string-match against the accounts page. It could be that your accounts page is localised (e.g. not reading "Welcome") or it could be that it your username ($LOGIN) is interesting and/or long that it has been truncated/altered. @silverdulcet, @Ruediger: Thinking about it, this could be the issue affecting you too. Could anyone with a language *not* set to en-GB or en-US please login manually and then look at the accounts page for the equivalent of "Welcome " and post what they find here?

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Stuart

Stuart — Thu, 23 May 2013 08:49:55 +0000

@yaztromo: … or they might just disable free accounts. That seems to be the way they’re headed.

Step 1: Make free accounts a pain to maintain;
Step 2: Point out the drop-off in the number of free accounts;
Step 3: Because clearly no-one wants a free account, cancel them;
Step 4: ???
Step 5: Profit!

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Stuart

Stuart — Thu, 23 May 2013 08:46:08 +0000

@boo: Your NAS could well be using busybox rather than GNU coreutils grep, in which case it may be lacking the 'match option - but using 'head' is definitely a perfectly good work-around.

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Stuart

Stuart — Thu, 23 May 2013 08:42:38 +0000

@silverdulcet You might need to change the double-quotes for single-quotes, e.g.: [code lang="bash"]LOGIN='myu$sername' PASSWORD='c4@2yP@ssw0rd!'[/code] ... to make sure that nothing tries to interpret it. Dollar symbols especially could be problematic.

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Sean

Sean — Wed, 22 May 2013 19:44:58 +0000

I experience the same thing, using the proper credentials. It’s a great idea, and I’m much appreciative for the script, if I can figure out what’s going wrong.

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Ruediger

Ruediger — Tue, 21 May 2013 21:48:20 +0000

I have tried with 3 accounts. One is working fine, the other two fail. Manual login works fine for all three accounts. None of the credentials contains special characters. The only difference of the failing one is a much longer login name. Might be a coincidence, but this is the only obvious difference…

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Peterkneter

Peterkneter — Tue, 21 May 2013 16:35:07 +0000

It doesn't work for me. I Always get 302 Found. Here my Debug Information:

DEBUG: Fetching initial headers to pre-load cookies...
HTTP/1.1 200 OK
Date: Tue, 21 May 2013 16:31:38 GMT
Server: Apache
Cache-control: no-cache
Content-Type: text/html; charset=ISO-8859-1
Expires: Tue, 21 May 2013 16:31:38 GMT
Set-Cookie: id=/caEcIu/FvC14c6gHKY6kwciz+o; domain=account.dyn.com; path=/; expires=Mon, 19-Aug-2013 16:31:38 GMT
Accept-Ranges: none
Vary: Accept-Encoding

DEBUG: Fetching UID...
DEBUG: Read UID as '7DA5CE1862B7568C0145A5A7CF660002B4' - posting data...


302 Found

Found
The document has moved here.

DEBUG: Response received - verifying result...
Login failed

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by yaztromo

yaztromo — Tue, 21 May 2013 15:34:59 +0000

Thank you for this. It is working fine for me.

The only weakness I see is that it will be easy for Dyn to break the script, and they will probably do just that as often as possible.

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by boo

boo — Tue, 21 May 2013 12:28:58 +0000

Great script, will be running it as a cronjob on my NAS. The only thing I had to change was the grep "-m 1" parameter. My system spits out a "grep: invalid option -- m" when using it. Instead I used "head -n 1", example: [code lang="bash"]VALUE="$( curl -b $COOKIES -c $COOKIES -kso - -A "$UA" --url "$LOGINURL" | grep "multiform" | cut -d"'" -f 6 | head -n 1 )"[/code]

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by silverdulcet

silverdulcet — Tue, 21 May 2013 11:05:01 +0000

Nope. I filled in the proper credentials. Tried it with 2 different accounts. One password has special characters & one doesn’t.

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by Martin

Martin — Tue, 21 May 2013 09:48:21 +0000

@silverdulcet
I hope you are not trying to authenticate with

LOGIN="****"
PASSWORD="****"

Comment on Dyn SLA Update – or, How To Lose Friends and Alienate Customers by fermulator

fermulator — Tue, 21 May 2013 04:57:08 +0000

Still working for me:

fermulator@fermmy-server:~/scripts$ ./dynDns.sh 
Login successful

-------- Original Message --------
From: Fermulator Fermulator 
Sent: Tue 21 May 2013 12:56:05 AM EDT
To: Fermulator Fermulator 
Cc:
Subject: DynDns Login/Update Success\n YEYE!