|Cannot "Add new URL" for am App Engine, getting "The term '[mydomain.com]' is not allowed."||ChristofferME||8/3/12 11:55 PM|
I have added a new domain (not an Alias) to my Google Apps account, meaning I have added the domain "planemo-card-game.com" to my Google Apps account "christoffer.me" and got it verified.
I have also a Google App Engine project connected to my private account (firstname.lastname@example.org). In the "Application Settings", beneath "Domain Setup" I have "Add domain", meaning I have connected my Google App Engine project to "christoffer.me" Google Apps Account.
When I visit the dashboard for "christoffer.me" I can see that my Google App Engine project is listed in "Settings".
Now I want to create a new alias for my Google Apps Engine project to "www.planemo-card-game.com", so I click on "Add new URL" and type "www" and select "planemo-card-game.com" in the drop down of all my domains connected to "christoffer.me" Apps Account.
However, when saving I get:
The term 'planemo-card-game.com' is not allowed.
How do I resolve this?
|Re: Cannot "Add new URL" for am App Engine, getting "The term '[mydomain.com]' is not allowed."||email2roy||8/9/12 9:12 AM|
I am getting the same error as you do.
If I am adding it to the primary domain it works. If I am adding it to other domain under the primary. It is giving me this error.
Let me know if you have this resolved
|Re: Cannot "Add new URL" for am App Engine, getting "The term '[mydomain.com]' is not allowed."||Rob.||8/10/12 7:13 PM|
This must be a recent addition as it wasn't possible to use alias domains, only primary.
Will need to ask the Google Advisors about this.
|Re: Cannot "Add new URL" for am App Engine, getting "The term '[mydomain.com]' is not allowed."||Rob.||8/10/12 7:18 PM|
What is the term domain getting rejected?
|Rob.||8/14/12 8:14 PM|
The word from the advisors, is that even though the cpanel is offering this option, it's not possible to use secondary domains.
|email2roy||8/15/12 12:35 AM|
Will this be fixed? or it will be always like this?
Since I have added my other domain to my primary domain. When I add try to link my google app engine app to new domain (secondary), I am getting an error. So I guess I have to disassociate my secondary domain first. if I want to have apps associate to a secondary domain?
|Rob.||8/15/12 12:42 AM|
You'll need to remove the domain as secondary and setup a separate GA account with the required domain (as a primary).
|Locavora||8/17/12 1:26 PM|
I reported the problem to Google Enterprise Support, and they also said that adding custom URLs for App Engine instances on secondary domains are not currently supported.
They recommended everyone needing that feature to use the Send Feedback button on the bottom right of the screen while on the Google Apps control panel and capture the page with the error shown when adding the secondary domain.
|James Pearn||11/11/12 12:52 AM|
I have just run into this same error and have reported it via the "Send feedback" button in Google Apps.
|Ishener||11/11/12 5:06 AM|
same problem here...
|James Pearn||11/11/12 5:24 AM|
I have just found, however, that if you add the secondary domain as an "alias" rather than "other domain" then it works.
I'm not clear on what the difference between "other domain" and "alias domain" is, but so far the setup is working for my needs.
|Pavel Tyslyatsky||11/19/12 7:11 AM|
I reported problem by Send Feedback week ago with adding secondary domain error screenshot (Free account, Belarusian domains .by). No answer.
What to do next: wait answer or send feedback again? Did support add secondary domain after your feedback?
|Locavora||11/19/12 7:29 AM|
@Pavel Tyslyatsky - No, Google Enterprise Support said that the infrastructure was not in place to support secondary domains for AppEngine - they asked people to file requests using the Send Feedback button to show the engineering team how much the feature is requested.
BTW, please also star the related issue on the AppEngine issue tracker: http://code.google.com/p/googleappengine/issues/detail?id=6545
|Pavel Tyslyatsky||11/19/12 8:06 AM|
Oh, bad news. Anyway thanks for answer.
I with my colleagues stared issue. I hope that guys from google will fix it soon.