Open ghost opened 9 years ago
I think, you need to update mup with npm i mup
On Sun, Apr 5, 2015 at 7:39 AM artitw notifications@github.com wrote:
I had a different issue earlier (#351 https://github.com/arunoda/meteor-up/issues/351), but it has evolved to this one. When running mup setup with SSL, I don't see any output regarding STUD or SSL:
- Installing Node.js ✔ Installing Node.js: SUCCESS
- Installing PhantomJS ✔ Installing PhantomJS: SUCCESS
- Setting up Environment ✔ Setting up Environment: SUCCESS
- Copying MongoDB configuration ✔ Copying MongoDB configuration: SUCCESS
- Installing MongoDB ✔ Installing MongoDB: SUCCESS
- Configuring upstart ✔ Configuring upstart: SUCCESS
There is supposed to be something, right? In my mup.json, I have
"ssl": { "pem": "./ssl.pem" }
I called mup setup and also mup deploy, but my site still has no https. I also installed force-ssl. The logs showed no errors. Any ideas?
— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/352.
Okay, I just did that and got the output below, then ran mup setup
but still no output relating to STUD or SSL.
npm i mup mup@0.9.7 node_modules/mup ├── colors@0.6.2 ├── underscore@1.7.0 ├── async@0.9.0 ├── uuid@1.4.2 ├── nodemiral@0.3.11 (debug@0.7.4, ejs@0.8.8, handlebars@1.0.12) ├── cjson@0.3.0 (jsonlint@1.6.0) └── rimraf@2.3.2 (glob@4.5.3)
Can you post your mup.json (with credentials, passwords, etc. removed)?
I had his same problem. I just updated mup like @arunoda said above and things started working. It looks like @artitw close this... is it because after updating it worked?
@fongandrew below is my mup.json. When I install and run STUD manually (independent of mup), it works. Thanks very much for your kind help. @aadamsx thanks for calling that out -- I closed this issue unintentionally. Will re-open.
{
"servers": [
{
"host": "cs.technology.com",
"username": "root",
"password": "xxxxxxxxxxxxx"
}
],
"setupMongo": true,
"setupNode": true,
"nodeVersion": "0.10.33",
"setupPhantom": true,
"appName": "CS",
"app": "/root/CS",
"env": {
"PORT": 80,
"ROOT_URL": "http://cs.technology.com/",
"MAIL_URL": "smtp://cstech%40gmail.com:xxxxxxxxxxxxxxxxx@smtp.mandrillapp.com:587/"
},
"deployCheckWaitTime": 30,
"ssl": {
"pem": "./ssl.pem"
}
}
The ROOT_URL is 'http://...' instead of 'https://...' -- is that right?
Yes, it is http://...
Sorry, should it be 'https' instead of just 'http'?
Shouldn't it be:
"ROOT_URL": "https://cs.technology.com/",
I've tried both, giving the same results. From the documentation, I think it should be http://...
Look at this: https://forums.meteor.com/t/mup-and-ssl-configuration/2489 to see if anything I learned can help you.
FWIW, I use https
in the ROOT_URL, which works for me (and makes sense given that it's SSL).
Anyhow, these might be silly questions, but some possible issues off the top of my head:
ssl.pem
file in the same directory as your mup.json
file?ssl.pem
file being properly copied over from your local machine to the server? That is, is the opt/stud/ssl.pem
file on your server identical to the one sitting on your local machine?Another thought: The mup
command is calling the binary for an older (globally installed) version, rather than an up-to-date (locally installed) version.
Try npm update -g mup
and then doing mup setup
again.
@artitw , why do you have a MAIL_URL reference? I'm using amazon mail services in my Meteor application and found I didn't need anything in the mup.json file for this... What am I missing?
@fongandrew thanks for your suggestions. I played around with both HTTP and HTTPS. I'l give it another try and update, since I now installed force-ssl and the mup documentation says it should be HTTPS with force-ssl. I also made sure the files were all in order and no other processes were running. I also updated mup as you suggested. Since I have gotten STUD to work independently of mup, I'll settle for now and see if I can figure it out in the future. Will update with anything I learn
@aadamsx I probably don't need the MAIL_URL there because I set it during Meteor startup anyway.
@arunoda You said in the previous issue that when you want to setup SSL, you just have to mup deploy
but actually you have to do a mup setup
before to install STUD on the server, had the same problem has @artitw but here is the fix.
I'm running into the same issue. I added the ssl block to mup.json
but there's no report of stud being installed in the mup setup
logs, and no trace of stud on the server.
Here's my mup.json
btw: https://gist.github.com/SachaG/1890aa50000963892cb2
@SachaG Did you update mup? Do npm i mup -g
I did, same result.
Maybe a problem with your pem bundle, can't help any further :)
Would a problem with the pem bundle prevent stud from being installed? I assumed it would still be setup, or at least throw some kind of error?
Yeah I guess so, what is the server operating system ?
I wondered if setting the ssl backendPort to 443 revealed anything interesting?
I ended up using MupX, seems to be working so far. So it was probably a problem with the .pem file (MupX doesn't need one).
I had a different issue earlier (https://github.com/arunoda/meteor-up/issues/351), but it has evolved to this one. When running mup setup with SSL, I don't see any output regarding STUD or SSL:
There is supposed to be something, right? In my mup.json, I have
I called mup setup and also mup deploy, but my site still has no https. I also installed force-ssl. The logs showed no errors. Any ideas?