502 bad gateway after SSL is enabled

[fisherman818]

Hi All,

I am referring the issue after deployment using https://github.com/arunoda/meteor-up

Without SSL enabled, the meteor app is working fine; right after SSL is enabled, I always get the 502 Bad gateway error, as described here: zodern/meteor-up#115

I tried to follow the methods by @tcastelli here: #7, but there is no such path

/var/lib/docker/aufs/mnt/CHECKEDID/opt/nginx/conf/nginx.conf

Any idea what is the updated path to find that particular nginx.conf?

Thank you!!

[tcastelli]

Unfortunately, I left the meteor-up train quite a long ago, so I'm not sure how is it going anymore.

[maxmatthews]

@fisherman818 Did you ever get this issue resolved? I'm having the same problem here: zodern/meteor-up#463

[fisherman818]

@maxmatthews no luck for me yet. still trying to find out reasons. I saw your another post, good to know that you solved the problem by scaling up the DO. I tried the same solution before, increase the RAM by 4 times, still having the issue.

My nginx error log show sth:

2017/02/16 17:29:38 [error] 30329#30329: *208 upstream prematurely closed connection while reading response header from upstream, client: xx.xx.xxx.xx, server: www.domain.com, request: "GET /plugin/app.js HTTP/1.1", upstream: "http://127.0.0.1:3000/plugin/app.js", host: "www.domain.com", referrer: "https://www.domain2.com"

I will share more info when I find out the reason

[chrisciampoli]

Same issue here. Have tried with multiple VPS setups, different from scratch projects, etc etc. Not sure whats going on.

[fisherman818]

@chrisciampoli if you have tried all methods on server, it's also time to look at the issues of the Meteor codes, especially the server side's code.

[chrisciampoli]

Unfortunately this happens with a start project, which I the deploy with MUP using its AUTO ssl. Not sure what I would check in regards to the code. In regards to instance being run on Digital Ocean, I’ve tried multiple builds of ubuntu (14.04, and 16.02 both x32 an x64 arch). Same results. :/

…

On Feb 23, 2017, at 8:11 PM, fisherman818 ***@***.***> wrote: @chrisciampoli <https://github.com/chrisciampoli> if you have tried all methods on server, it's also time to look at the issues of the Meteor codes, especially the server side's code. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAyK88P9WcAbqzNLAc4o1U43YublNlSdks5rflh5gaJpZM4LzwAJ>.

[TimeBandit]

I'm seeing this issue to on Ubuntu NodeJS 6.10.2 on 16.04 on Digital Ocean using their cheapest droplet.

[maxmatthews]

@TimeBandit The autogenerate feature doesn't work on 512 mb of RAM. There were talks to add a minimum requirements section to the readme stating 1 gb of RAM is required.

[TimeBandit]

Ok good, I will try to generate the certs locally before deploying, thanks 👍