Upgrade complete, pending local DNS

[Jeff Lindsay]

Looks like everything is working. DNS TTL was set super low before switching, so it should be propagated by now and it's working for me. The old client complains and links to the new client. The new client works fine. Notifications seem to be going through.

We are now off the system that would constantly go down. :)

--
Jeff Lindsay
http://progrium.com

[Hunter Gillane]

Cool! I'm gonna push the status app a bit later. Hopefully won't see any red!

Sent from my iPhone

[Brian Dunnington]

glad to hear the old system has been retired. now on to the next problem... =)

the notify.io site itself seems to be having issues. i keep getting
the error below - not every for every single page request, but
probably 8 out of 10:

Error: Server Error
The server encountered an error and could not complete your request.

If the problem persists, please report your problem and mention this
error message and the query that caused it.

[Jeff Lindsay]

Seems to be better now? I know there are some things that could be causing that to look into.

[Brian Dunnington]

yeah, it is much better now.

the only other thing i am seeing now is that the 'send test'
functionality on the Settings page is no longer working. Firebug
reports that the request tries to hit
http://api.notify.io/v1/notify/myemailhash and then the request is
aborted. any ideas on that one?

[Jeff Lindsay]

What's your local DNS resolve api.notify.io to?

[Brian Dunnington]

my DNS resolves api.notifo.io to 174.143.203.167

[Jeff Lindsay]

That's the problem. I'm not sure how/when it will resolve because the authoritative DNS has been set to the new value for a lot longer than the previous TTL -- so this shouldn't be happening. It might just fix itself over time or if you restart/reconnect or some way to flush DNS. 

[Brian Dunnington]

i tried to flush my DNS settings, but to no avail. i am assuming my
provider's DNS has not updated yet either.

what is the new correct DNS entry? i can just update my HOSTS file
manually for now. thanks/.

[Jeff Lindsay]

It's a CNAME to ghs.google.com, which for me resolves to 74.125.77.121

[saqeb.akhter]

I think I'm having the same issue. Does it usually take this long for
a DNS change to propagate?

On Oct 20, 2:44 pm, Jeff Lindsay <progr...@gmail.com> wrote:
> It's a CNAME to ghs.google.com, which for me resolves to 74.125.77.121
>
> On Wed, Oct 20, 2010 at 11:43 AM, Brian Dunnington <
>
>
>
>
>
> briandunning...@gmail.com> wrote:
> > i tried to flush my DNS settings, but to no avail. i am assuming my
> > provider's DNS has not updated yet either.
>
> > what is the new correct DNS entry? i can just update my HOSTS file
> > manually for now. thanks/.
>

> > On Wed, Oct 20, 2010 at 11:40 AM, Jeff Lindsay <progr...@gmail.com> wrote:
> > > That's the problem. I'm not sure how/when it will resolve because the
> > > authoritative DNS has been set to the new value for a lot longer than the
> > > previous TTL -- so this shouldn't be happening. It might just fix itself
> > > over time or if you restart/reconnect or some way to flush DNS.
>
> > > On Wed, Oct 20, 2010 at 11:21 AM, Brian Dunnington
> > > <briandunning...@gmail.com> wrote:
>
> > >> my DNS resolves api.notifo.io to 174.143.203.167
>

> > >> On Wed, Oct 20, 2010 at 11:09 AM, Jeff Lindsay <progr...@gmail.com>

> > wrote:
> > >> > What's your local DNS resolve api.notify.io to?
>
> > >> > On Wed, Oct 20, 2010 at 11:07 AM, Brian Dunnington
> > >> > <briandunning...@gmail.com> wrote:
>
> > >> >> yeah, it is much better now.
>
> > >> >> the only other thing i am seeing now is that the 'send test'
> > >> >> functionality on the Settings page is no longer working. Firebug
> > >> >> reports that the request tries to hit

> > >> >>http://api.notify.io/v1/notify/myemailhashand then the request is

> > >> >> aborted. any ideas on that one?
>

> > >> >> On Wed, Oct 20, 2010 at 10:59 AM, Jeff Lindsay <progr...@gmail.com>

> > >> >> wrote:
> > >> >> > Seems to be better now? I know there are some things that could be
> > >> >> > causing
> > >> >> > that to look into.
>
> > >> >> > On Wed, Oct 20, 2010 at 9:52 AM, Brian Dunnington
> > >> >> > <briandunning...@gmail.com> wrote:
>
> > >> >> >> glad to hear the old system has been retired. now on to the next
> > >> >> >> problem... =)
>
> > >> >> >> the notify.io site itself seems to be having issues. i keep
> > getting
> > >> >> >> the error below - not every for every single page request, but
> > >> >> >> probably 8 out of 10:
>
> > >> >> >> Error: Server Error
> > >> >> >> The server encountered an error and could not complete your
> > request.
>
> > >> >> >> If the problem persists, please report your problem and mention
> > this
> > >> >> >> error message and the query that caused it.
>

> > >> >> >> On Tue, Oct 19, 2010 at 9:21 PM, Jeff Lindsay <progr...@gmail.com

[Jeff Lindsay]

Can you run "dig api.notify.io" and share the results?

[saqeb.akhter]

Sure:


sakhter@sakhter-nas:~$ dig api.notify.io

; <<>> DiG 9.7.1-P2 <<>> api.notify.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3066
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;api.notify.io. IN A

;; ANSWER SECTION:
api.notify.io. 282741 IN A 174.143.203.167

;; Query time: 1 msec
;; SERVER: 192.168.10.254#53(192.168.10.254)
;; WHEN: Sat Oct 23 01:00:13 2010
;; MSG SIZE rcvd: 47

sakhter@sakhter-nas:~$

On Oct 22, 2:46 pm, Jeff Lindsay <progr...@gmail.com> wrote:
> Can you run "dig api.notify.io" and share the results?
>

> > > > >> >>http://api.notify.io/v1/notify/myemailhashandthen the request is

[Jeff Lindsay]

Looks like somebody got a bad TTL and it won't be updated for about 3 more days.

[saqeb.akhter]

I'm still getting a 404 Error when trying to post a notification.


I'm not sure why...I get a 404 Target or Source not found.

On Oct 23, 6:38 pm, Jeff Lindsay <progr...@gmail.com> wrote:
> Looks like somebody got a bad TTL and it won't be updated for about 3 more
> days.
>

> > > > > > >> >>http://api.notify.io/v1/notify/myemailhashandthenthe request

[saqeb.akhter]

looks like the md5 of the email address is case sensitive now :(

[Hunter Gillane]

I think it always has been case sensitive. I remember a while ago I
was having the same issue. I seem to recall that when I signed into
notify.io with my google account, the email address that it sent back
to notify was a camel cased version of my email, and so when I tried
to hash the lower cased version of it and use that as the user hash to
notify it couldn't find it.

Sent from my iPhone

On Oct 24, 2010, at 3:36 PM, "saqeb.akhter" <saqeb....@gmail.com>
wrote:

[saqeb.akhter]

For me the uppercased hash would work, now it does not i've changed it
to lowercase the hash and now it works.

On Oct 24, 8:00 pm, Hunter Gillane <hunter.gill...@gmail.com> wrote:
> I think it always has been case sensitive. I remember a while ago I  
> was having the same issue. I seem to recall that when I signed into  
> notify.io with my google account, the email address that it sent back  
> to notify was a camel cased version of my email, and so when I tried  
> to hash the lower cased version of it and use that as the user hash to  
> notify it couldn't find it.
>
> Sent from my iPhone
>

> On Oct 24, 2010, at 3:36 PM, "saqeb.akhter" <saqeb.akh...@gmail.com>  

[Brian Dunnington]

this bug popped up once before when the old system first launched and
jeff put in a fix for it. must not have gotten ported over to the new
system. i tried to find the link to the original thread, but the group
is not showing threads older than nov 2009, so i am just copying it
from my email archives:

original bug report:

"not sure if this is considered a bug or not, but i thought i would
mention it. if you provide your email hash with uppercase hex values,
notify.io cant match it and returns a 403 Forbidden error. probably
easy enough to .tolower() the input just in case.

example:

works: 251171a6643a794e05827f88601918df
no worky: 251171A6643A794E05827F88601918DF"

Jeff's response:

"Thanks! Taken care of:
http://github.com/progrium/notify-io/commit/830ddc1aeb39320b0aaf565a4314118f2d3911f0

Will go out with the next push to production."

[Jeff Lindsay]

Yep, that was a regression. Sorry about that. Just deployed a fix. Also, Santiago submitted a patch that will email you when a source requests approval, and that got deployed too.

Regression tests coming soon.

-jeff