For anyone interested, I worked a bit this weekend on the integration of Let’s Encrypt in MeteorUp. Feel free to contribute to the PRs. Here the two pull requests!
https://github.com/arunoda/meteor-up/pull/873
Thank you,
Carlos.
For anyone interested, I worked a bit this weekend on the integration of Let’s Encrypt in MeteorUp. Feel free to contribute to the PRs. Here the two pull requests!
https://github.com/arunoda/meteor-up/pull/873
Thank you,
Carlos.
As I couldn’t make it work with stud, I end up using Nginx for that. It seems to be working fine now.
I guess I should switch to mupx which uses Nginx anyway.
Hello, I’m using this more nginx to proxy the meteor port to the port 80/443.
There are any way to remove nginx ? I can’t run meteor on port 80 because I have a few apps runing on the same server, that why I need nginx.
thanks
Humberto
Do you have any cronjob sample for this?
I’m attempting to try this on my prod server.
I can’t do this on my test server (I don’t own the domain name there) so I’m a little nervous.
Just a few questions,
I’m just reading up on this myself, but here are some answers from what I understand.
Adding the SSL values in mup.json simply gets mup to use an additional front-end nginx server in front of the same bundled app you had before adding SSL. So yes, I would think you can revert your mup.json to remove the SSL key, do “mup deploy”, and get back your old deployment. mup also has a mechanism for falling back to a previous deployment in case the current deployment fails.
For similar reasons, unless your 2nd prod server somehow uses mup to set up nginx, you probably need to configure your nginx separately from mup. In that case I think you wouldn’t need to set up SSL for each individual app, assuming they’re all under the same domain.
The cron job solution is typically recommended for installations that are able to use the “webroot” option, which allows the cert to be issued without starting and stopping the server. So, a cron job may not make sense for the manual process discussed in this thread, where you need to stop and re-run mup deploy.
Again, this is all pretty new to me so anyone feel free to provide more info. Good luck, let us know how it goes!
Not sure it matters. Whatever you named the file
I tried to install LetsEncrypt on AWS EC2 instance, but I am failing here, aber downloading git and cd letsencrypt.
The error I get:
-bash: ./bootstrap/install-deps.sh: No such file or directory
Anyone with the same problem?
@choemi You need to install letsencrypt on the machine that you do your development on. It’s likely your own laptop and not an EC2 instance. You can also try sh ./bootstrap/install-deps.sh
instead.
It doesn’t matter if I execute it on my MacBook or per SSH on an AWS ubuntu. I always get the same error message when trying to install it. Is there anything else I need to install?
Looks like things have changed a lot. I wrote this guide 6 months ago and have switched to Galaxy, which has auto letsencrypt support.
Check out the updated documentation:
I know that DO and AWS aren’t exactly the same, but if you spin up an ubuntu instance on AWS, I’m thinking most of this guide should work for you. I just walked through it last week, and with the exception of the fact that Docker installed out of the gate with mupx, it was exactly the same.
General question:
I do have a meteor app on DO (app.domain.com) and a CMS website (www.domain.com) on top of Joomla on other hosting server.
I deploy my app on DO thru mup not mupx.
I want the two have ssl certificate, should I generate separate certificate for both even if they have the same domain?
Thanks!
You can but you need to specify both the www and app version when you
create the certificate. I think you enter them comma separated or something.
@vigorwebsolutions Thx for the guide! Works like a charm. Only problem I had was to download the key files from AWS because I could not access the folders on ubuntu (some problems with root access…). I finally could do it now by copy them from AWS to another server and then download them from their to my local machine.
You will have a downtime in your APP with the STANDALONE version of letsencrypt. You should use webroot plugin instead! https://letsencrypt.readthedocs.io/en/latest/using.html#plugins