CName Custom Domain 404 on Create

[jake nassereth]

Wanted to mention that if you use the Custom Domain option for an account on repository, that the Issue Tracker and Wiki do not work.

Works fine:
http://bitbucket.org/<user>/<repo>/issues/new

Doesn't work:
http://mydomain.com/<repo>/issues/new

Receives a 404 apache error when user clicks the "Create" button for the new issue or wiki item.

Would like to mention that when user attempts to create a new issue, url is:
http://mydomain.com/<repo>/issues/new
And when user clicks "Create" button, url redirect is:
http://mydomain.com/<account>/<repo>/issues/new

Which I believe is noteworthy if not the root problem, since a CName custom domain routes to the account itself, and thus http://mydomain.com/<account>/ does not exist in the first place. Bham... 404.

Figured someone might want to fix that? It's a great feature... wish it worked entirely.

Edit:

https://bitbucket.org/site/master/issue/5058/create-issue-button-not-working-with

Looks like it has been an issue for quite some time now then, eh?

[PauloP]

Hi Barry

Just as a double check, in case of new hostname, is this zone available from your DNS? Also, if you're using www.domain, did you create a local redirect to bitbucket?

All those stufs are locally configured.

Cheers,

Paulo Renato

[jake nassereth]

Indeed is available on the new hostname. The DNS is routed from GoDaddy, and have it configured to use the domain without [www.] . I've not configured the redirection for including [www.] however the url denotes that it is not being used, at least not for the client-side resolution.
Perhaps the server(bitbucket.org) is attempting to use such, and requires this?

Will note that as far as chrome and firefox are concerned, the networking data for client-side requests appear to be routing just fine. Only problem is, as described above, the 404 is due to a non-existant path, a folder named by the bitbucket account holder -- which cannot exist since the Custom Domain feature points directly to said account. That is to say neither of these exist:

http://bitbucket.org/<my_account>/<my_account>/<my_repo>/
http://www.bitbucket.org/<my_account>/<my_account>/<my_repo>/

So don't think it has to do with the WWW. Unless the redirection is manually handled by your servers; even so the above problem is still just that.

However I definitely appreciate your assistance, and thorough double-checking on the setup of the server DNS & routing in question. :)