Status

RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: daleharvey, Unassigned)

Tracking

({foxfood})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [bzlite])

(Reporter)

Description

4 years ago
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:41.0) Gecko/20100101 Firefox/41.0

Heroku doesnt allow root domains, we can forward http://bzlite.com but not https at the dns level, either need to switch hosts or dns provider

Comment 1

4 years ago
To comment here a bit -

Heroku *does* allow root domains. However, as DNS does not reliably implement root domain CNAME ssl-endpoint.herokuapp, most DNS providers (including Mozilla's) do not support the ALIAS record type necessary to host it on https correctly.

Transferring DNS service for this domain to Amazon Route 53 would allow you to add the root domain ALIAS ssl-endpoint.herokuapp record. Other DNS providers may permit this as well.
(Reporter)

Comment 2

4 years ago
Richard, happy to get the domain transferred to amazon to get the root domain working, any idea about the process?
Flags: needinfo?(rsoderberg)
(Reporter)

Updated

3 years ago
Component: Gaia::Feedback → Gaia::Bugzilla Lite
Keywords: foxfood
Keywords: dogfood
(Reporter)

Updated

3 years ago
Blocks: 1180660
feature-b2g: --- → 2.5+
(Reporter)

Comment 3

3 years ago
Hey Richard, its not hugely urgent, but wanted to ping you again to see if you had any suggestions on how to get this domain transferred / configured correctly?

Comment 4

3 years ago
Ah, sorry. So, you'll need to set up Route 53 DNS for the domain.

:jbuck, you've done this recently for MoFo (setting up Route 53 with a root ALIAS record) - would you be willing to help Dale set this up, or point me to a guide on setting it up that we can use to help him?

(Obviously the docs are public and it might be simple enough to do without previous experience, but given that Bzlite is already in production and :jbuck has prior experience migrating domains in this way, I thought I'd ask.)
Flags: needinfo?(rsoderberg) → needinfo?(jon)
feature-b2g: 2.5+ → ---

Comment 5

3 years ago
:atoll - Sure thing! I have a Cloudformation script that does 95% of the work at https://github.com/MozillaFoundation/mofo-devops/blob/master/AWS/cloudformation-templates/s3-and-cloudfront.json

What that does is configure a S3 bucket to redirect to the domain of your choice (RedirectHost = www.bzlite.com). It also creates a Cloudfront distribution which will provide a custom SSL certificate for the redirect (IAMCertificateId = whatever the ID of the SSL certificate is, and CloudfrontAliases = bzlite.com). Once you got that deployed, then all you need to do is setup the Route53 zone on AWS with an A ALIAS record for bzlite.com that points at your Cloudfront distribution:

mozillafoundation.org. A ALIAS d2tj9dlffq8w8w.cloudfront.net. (just for example)
Flags: needinfo?(jon)
(Reporter)

Comment 6

3 years ago
Thanks so much for the information.

However that sounds like a fairly complicated setup for a simple site, I have removed any need for the site to run a node server and it could be delivered as a plain static site now so it seems like we could go with something simpler for hosting.

Whats the easiest choice for a simple static site server under mozilla infrastructure, not entirely sure who to ask here so if this needs forwarding that would be appreciated.
Flags: needinfo?(rsoderberg)
(Reporter)

Comment 7

3 years ago
This doesnt block or effect 2.5 at all, so taking the blocker off, but one ill probably want to fix soonish
No longer blocks: 1180660
Dale,

If Route53 is an option, we can consider doing that and keeping you on Heroku. Alternatively, I can also see what our DNS provider can do :)
(Reporter)

Comment 9

3 years ago
Clearing NI, this is no longer an actively developed mozilla product, I will likely put it on my own hosting shortly
Flags: needinfo?(rsoderberg)
(Reporter)

Comment 10

3 years ago
Works now on my own hosting
(Reporter)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.