Meteor-Up fork with free SSL certificates by Let's Encrypt

Hi all,

Added Let’s encrypt certificates support to arundo/meteor-up. Built on top of Docker-letsencrypt-nginx-proxy-companion, it automatically generates certificates for specified domain and renews it in 30 days before expiration. All you need to do is add email & domain inside mup.json file and run mupx-letsencrypt setup & mupx-letsencrypt deploy

While I’m already using it on 3 production servers, it is still in beta, so I’m recommending to test it before deploying.

Release version currently supports Meteor <= For Meteor 1.4 you can try dev-version which is based on abernix/meteord:base container with Node 4.4.7:

npm install -g mupx-letsencrypt@meteor14

Will this mup version work with Meteor deployments that don’t need SSL/nginx and other that other extra stuff?

When I tried to move to, my mup deployments broke.

@aadams Yes it will, but if you do not need SSL support it will be just the same as using official arunoda package mupx

A quick question, why do you renew the certificate every hour? The certificates are fine for 90 (or 30?) days right?

Was there a reason why you forked this and didn’t try to get this in the newer MUP version?


Correction: certificates are checked every hour and renewed in case if they are expiring in the next 30 days.

Not actually, but the development inside mup rep does not look pretty active (only 1 pr was merged through the last year), so I doubt that it get there anytime soon. If @arunoda thinks that it makes any sense to make a pr - I would be happy to contribute.

1 Like

Yes. old mup is no longer active.
New development is done here and we’ll add Meteor 1.4 support by today.
@madushan1000 is working on that.

We’ll do a new major release for mup based on the new repo:

@tsepelev send us a PR to this repo:
We are pretty happy to get it.

1 Like

An issue is open here in the new repo by the way with some people having experimented with it before.

I think we could this soon.

It’s really great to hear there’s active development again for MUP!

What timeline are you aiming to release the new Mup? And will there be any support / active development for Cluster?

Actually, we released mup@1.0.0 now. Will do a blog post soon.
But I don’t think Cluster will be continued. It’s a big task and now there are many other solutions based on docker.


Awesome about Mup v1!

Too bad regarding Cluster, I haven’t seen something similar and easy that’s focused on Meteor.
But understandable a lot of work to maintain it.

Good to hear about mup(x). I am curious about cluster though. Do you have anything you recommend or use personally as a replacement for the cluster package? Thanks!

1 Like

@arunoda, does this version work with Meteor version I can’t seem to find a version of mup that works with 1.3.5.

So, to my understanding that feature is still not there, is it?
Please do correct if I’m wrong. :slight_smile:

@tsepelev, with your fork is it possible to specify multiple domains? I would like certificates for, and

I’ve got it working with kadirahq/meteor-up and ./letsencrypt-auto --manual certonly but would love to automate it with no server downtime!

Didn’t try by myself, but if all domains are going to point to the same app then it should work just fine. The fork is based on docker-letsencrypt-nginx-proxy-companion and it supports multiple domains out of the box.

Try to list urls in letsEncrypt domain key, like:

"letsEncrypt": {
  "domain": ",,",
  "email": ""

And feel free to share the result :slight_smile:

Tried it, and it works perfectly on all three subdomains!

I’m on Meteor 1.4 so I used mupx-letsencrypt@meteor14. The server was previously setup using kadirahq/meteor-up, but mupx-letsencrypt init/setup/deploy replaced the previous configuration flawlessly. Clicking on the green icon in the browser reveals a brand new certificate.

Now I need to wait 60 days to see if it auto-renews… Is there anyway I can test this sooner?

This is awesomeness, thanks very much!

Awesome, glad it worked!

Certificates will be renewed after 30 days, but currently you will need to build your own docker-letsencrypt-nginx-proxy-companion container to adjust the number of days. (you can find more info here).

Otherwise you can connect to your server by ssh and check the renewal process by using docker logs letsencrypt-companion