Loomio

I already have SSL set up on my server...

Aonghas PublicSeen by 37

I'm getting this error:

ERROR: driver failed programming external connectivity on endpoint loomiodeploy_nginx_1 (5620af51e4749f9b0173442b2bd11403d38fd3dde43e60c65154d112cf1a5969): Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address already in use

but I already have SSL set up on my main domain (I'm trying to install loomio on a subdomain) so what should I do?

Thanks!

How do I get this working in my free group?

opt-in by Aonghas Closed Mon 6 Mar 2017 4:01PM

Results

Robert Guthrie

Are you installing a computer that is already running another webserver?

Aonghas

Yes I am running it on a digitalocean droplet which already has nginx set up with several virtual hosts

Robert Guthrie

You'll need a new host if you want to use unmodified loomio_deploy. If you must use the same host you're going to need to route your traffic though your existing nginx setup, which I can't help you with, sorry.

James Kiesel

@aonghas The new polling types are currently an experimental feature which we've enabled for our internal groups for beta testing. They're not available to other groups just yet, but will be soon. Stay tuned for a bunch more cool features on the way as well.

If you'd like to enable them on your third party installation, you can do so by visiting /admin/groups/<group_key>, and clicking enable polls towards the bottom.

Pablo Costa

@aonghas you can only have one process to "listen" on a given {ip_address, port} pair. So you have two options:

  • get a new public IP address assigned to your virtual server (if possible, it will cost you money), and use it for your loomio_deploy, or
  • Set up a "front-end proxy" (eg. nginx) that listens on port 443 of your existing ip address and routes requests to the appropriate "back-end server" based on the hostname header in the request. This option will require you to alter the default loomio_deploy because you'll want to move the HTTPS management from the loomio_deploy to the "front-end proxy", incl. the letsencrypt stuff (you can get rid of the letsencrypt stuff if you already have a valid SSL cert for your current setup).