On Jan 8, 6:51 am, Tommy wrote:
> Thank you to everyone who helped us with this yesterday.
And thanks to you for updating us on the resolution. Too many posts
here have lots of people spending their time to help, but the
originator never bothers to explain how they eventually resolved the
problem
This problem has been fixed. Even though it looked like we had a CNAME
record, somehow it got messed up. It was actually inconsistent in that it
sometimes worked and sometimes didn't. I guess some servers had a valid
record and some had a bad one or none at all. Eventually the record
disapp
Hey Tommy, one more idea. You might get on IRC and see if you can
catch nickjohnson or ikai_google on there.
Robert
On Thu, Jan 6, 2011 at 18:47, Tommy wrote:
> Thanks for the link. I just submitted a production issue.
>
> Yes, we're also talking to Google App support. But they don't s
Thanks for the link. I just submitted a production issue.
Yes, we're also talking to Google App support. But they don't seem to be
very knowledgeable about this issue. First they said they could access our
site through our domain, which isn't true. Later they said they had
problems accessi
You could try to submit a production issue via the issue tracker.
http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
Sounds like you've also already submitted an issue to the Google Apps
people too?
On Thu, Jan 6, 2011 at 16:56, Tommy wrote:
> Does anyone kn
Does anyone know how I can escalate this with Google tech support? Our app
is live and none of our customers can reach it right now. We just launched
our app so this is a critical time for us, and we can't afford to be down
this long. So far it's probably been 6-7 hours.
We signed up for Go
I've tried that a couple times, and it still doesn't work. Does that fix
take some time to take effect? I tried it the first time about 30 min ago.
Thanks.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send e
Try if deleting mapping and re-establishing mapping fixes that and let us
know.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send em
No, I'm not mapping "www".
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com.
Are you mapping 'www'? If so check that sites does not also have a
mapping for 'www', or that it is disabled.
Robert
On Thu, Jan 6, 2011 at 15:48, Tommy wrote:
> I'm in the US so I hope the authorities aren't blocking it. :)
>
> The domain name does show up as being mapped correctly to
I'm in the US so I hope the authorities aren't blocking it. :)
The domain name does show up as being mapped correctly to my App Engine app
in the Google Apps dashboard.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this g
On Jan 6, 2:27 pm, Tommy wrote:
> My domain is set up to point to my App Engine app through Google Apps. This
> has worked fine for several months. But just a few hours ago, my app was no
> longer accessible through the domain. The CNAME record doing the redirect
> is still set up to point to
12 matches
Mail list logo
