How to connect domain DNS records to Galaxy?

deployment
1

Setting up app to Galaxy, which is currently hosted by Digital Ocean.

So I setup an account with Galaxy and mlab. Now I am very confused where the new app is? My comandline says the deployment was successful.

Deploying to myappcom.
Now serving at http://myapp.com

But the domain records from the company is purchased the domain from is not set to Galaxy. Is it set to Digital Ocean. so when I go to myapp.com it goes to the old app on Digital Ocean. How do I set the DNS records so it goes to Galaxy?

https://galaxy.meteor.com/help/configuring-dns

this link doesnt explain it clearly.

the A record is pointing towards Digital Ocean IP adress. Do I delete this?

In GoDaddy, I have sometHing called CNAME.
Do I change host to “galaxy-ingress.meteor.com.” with this last full stop?
what about where it says points to?

2

Getting Galaxy wired up with your DNS provider is easiest if you aren’t using a naked domain (see yes-www). So if you’re open to using something like www.myapp.com or app.myapp.com then you can use the easier CNAME option. Let’s assume you want www.myapp.com. Via GoDaddy add a CNAME record that points www to galaxy-ingress.meteor.com (if you want your app to be reachable at www.myapp.com). Then just make sure that when you deploy to Galaxy the domain name you specify via the deploy command line matches your CNAME setup, so:

DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy www.myapp.com --settings settings.json

With this approach, any existing A records you have in place don’t need to change. As an optional step you could then also add a domain forwarding rule via GoDaddy so that when people access your naked domain, myapp.com, they are forwarded to http[s]://www.myapp.com.

1 Like
3

i changed it to where it says “points to” to “galaxy-ingress.meteor.com” hosting is left at “www”

give this an hour to smooth out.

4

so far an error.

404 Not Found: No applications registered for host ‘www.myapp.com’.

5

Just to confirm - when you deploy your app, are you specifying www.myapp.com on the common line via meteor deploy?

6

DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy myapp.com --settings settings.json

7

changed it from myapp.com to www.myapp.com

Thanks alot! works now. next step is to get the old database up.

8

in my culture this means we’re married.

2 Likes
9

Congrats on your marriage.

What’s good with the domain forwarding rule?

10

domain forwarding working.

11

Curious how you entered the domains in the “Domains & Encryption” section of galaxy settings.

I’m pretty sure I have a similar setup as yours, with my GoDaddy www CNAME set to “us-east-1.galaxy-ingress.meteor.com” and domain forwarding set to ‘https://www.myapp.com’. Waiting to see if DNS changes will properly propagate, but seems like it should have resolved by now. I set my TTL to the minimum of 600 seconds. My Galaxy deployment script uses ‘www.myapp.com’. ROOT_URL is ‘https://www.myapp.com’ (if it matters).

When I visit myapp.com in chrome I get “server DNS address could not be found” and when I visit ‘www.myapp.com’ I get redirected to an older path I had setup, myoldapp.meteorapp.com and the error “This site can’t provide a secure connection - myoldapp.meteorapp.com sent an invalid response”. Not having luck clearing my DNS cache in chrome.

My galaxy settings:
Domain - - - - - - - - - - - - Encryption
’www.myapp.com’ - - - - - - Enabled • Force HTTPS

** UPDATE **
If I use incognito, www.myapp.com works, but myapp.com goes to “server DNS address could not be found”