Let's Encrypt makes websocket fail

Trying Let’s Encrypt for the first time with my mup deployment. Using the autogenerate clause in the SSL area of mup.js causes a websocket connection error after my app is deployed.

In Chrome’s console:

WebSocket connection to 'wss://....' failed: Error in connection establishment: net::ERR_NOT_IMPLEMENTED

I usually use uploaded certs and that works fine. I use abernix/meteord:base docker image. Here is the mup.js I’m using:

module.exports = {
	servers: {
			one: {
					host: '172.217.5.110',
					username: 'root',
					pem: '/Users/al/.ssh/id_rsa.do'
			}
	},

	meteor: {
			name: 'sub-domain',
			path: '/Users/al/cool-app',
			docker: {
					image: 'abernix/meteord:base'
			},
			servers: {
					one: {}
			},
			buildOptions: {
					serverOnly: true,
			},
			env: {
					ROOT_URL: "https://sub.domain.com",
					NODE_ENV: "production",
					MONGO_URL: "mongodb://...",
					MONGO_OPLOG_URL: "mongodb://..."
			},
			ssl: {
					port: 443,
					autogenerate: {
						email: '[e-mail]',
						domains: 'sub.domain.com'
					}
			},
			deployCheckWaitTime: 60
	},

};

Is this a known issue? Is there a workaround I can currently use?

I’m on the latest mup 1.2.8.

[ghost]

@trevordowdle a workaround for me was to simply not use let’s encrypt with mup. Instead put the instance behind CloudFlare (free) and use CloudFlare SSL which auto-renews and needs no management of certs.

CloudFlare now supports websockets very well out of the box, including the ones needed for Meteor, which is why this workaround is relatively new.

[zodern]

Since I am unable to reproduce it, I will close this issue. If anyone encounters this again, the issue can be reopened.