ok, i used letsencrypt, but now i get a startup error in /var/log/couchdb/couchdb.log (named 'eaddrinuse')
[info] 2020-04-24T09:50:45.814991Z [email protected] <0.11.0> -------- Application mem3 started on node '[email protected]' [info] 2020-04-24T09:50:45.815139Z [email protected] <0.11.0> -------- Application fabric started on node '[email protected]' [error] 2020-04-24T09:50:45.818472Z [email protected] <0.330.0> -------- CRASH REPORT Process (<0.330.0>) with 0 neighbors exited with reason: eaddrinuse at gen_server:init_it/6(line:349) <= proc_lib:init_p_do_apply/3(line:247); initial_call: {mochiweb_socket_server,init,['Argument__1']}, ancestors: [chttpd_sup,<0.327.0>], message_queue_len: 0, messages: [], links: [<0.328.0>], dictionary: [], trap_exit: true, status: running, heap_size: 376, stack_size: 27, reductions: 990 [error] 2020-04-24T09:50:45.818664Z [email protected] <0.328.0> -------- Supervisor chttpd_sup had child chttpd started with chttpd:start_link() at undefined exit with reason eaddrinuse in context start_error [error] 2020-04-24T09:50:45.818903Z [email protected] <0.326.0> -------- CRASH REPORT Process (<0.326.0>) with 0 neighbors exited with reason: {{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}} at application_master:init/4(line:134) <= proc_lib:init_p_do_apply/3(line:247); initial_call: {application_master,init,['Argument__1',...]}, ancestors: [<0.325.0>], message_queue_len: 1, messages: [{'EXIT',<0.327.0>,normal}], links: [<0.325.0>,<0.11.0>], dictionary: [], trap_exit: true, status: running, heap_size: 376, stack_size: 27, reductions: 172 [info] 2020-04-24T09:50:45.819039Z [email protected] <0.11.0> -------- Application chttpd exited with reason: {{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}} [info] 2020-04-24T09:50:47.879699Z [email protected] <0.11.0> -------- Application couch_log started on node '[email protected]' On Fri, Apr 24, 2020 at 4:47 AM Bill Stephenson <[email protected]> wrote: > Hi Rene > > I have these notes on configuring SSL using certbot: > > #Configuring the Firewall > sudo ufw allow 5984 > sudo ufw allow 6984 > > > ## Configure SSL - Lets Encrypt > > sudo apt-get update && sudo apt-get upgrade > sudo apt-get install software-properties-common > sudo add-apt-repository ppa:certbot/certbot > sudo apt-get update > sudo apt-get install python-certbot-apache > > sudo mkdir /opt/couchdb/letsencrypt > > sudo certbot certonly --webroot -w /var/www/YOUR.com --config-dir > /opt/couchdb/letsencrypt --logs-dir /var/log/couchdb -d YOUR.com > > > sudo certbot certonly --webroot -w /var/www/html --config-dir > /opt/couchdb/letsencrypt --logs-dir /var/log/couchdb -d YOUR.com > > sudo chmod 600 /opt/couchdb/letsencrypt/live/YOUR.com/cert.pem > sudo chmod 600 /opt/couchdb/letsencrypt/live/YOUR.com/privkey.pem > sudo chmod 600 /opt/couchdb/letsencrypt/live/YOUR.com/fullchain.pem > > # set the permissions on the files to the following: > > sudo chmod 600 /opt/couchdb/letsencrypt/live/YOUR.com/cert.pem > sudo chmod 600 /opt/couchdb/letsencrypt/live/YOUR.com/privkey.pem > sudo chmod 600 /opt/couchdb/letsencrypt/live/YOUR.com/fullchain.pem > > sudo chown -R couchdb /opt/couchdb/letsencrypt/ > > sudo nano /opt/couchdb/etc/local.ini > > # You will need to modify the following entries: > > port = 6984 > cert_file = /opt/couchdb/letsencrypt/live/YOUR.com/cert.pem > key_file = /opt/couchdb/letsencrypt/live/YOUR.com/privkey.pem > cacert_file = /opt/couchdb/letsencrypt/live/YOUR.com/fullchain.pem < > http://your.com/fullchain.pem> > > test it at: https://YOUR.com:6984/_utils/ > > — > > Kindest Regards, > > Bill Stephenson > Tech Support > www.cherrypc.com <http://www.ezinvoice.com/> > 1-417-546-8390 > > > > > > On Apr 23, 2020, at 9:36 PM, Rene Veerman <[email protected]> > wrote: > > > > i've installed couchdb on ubuntu-18.04, have modified > > /opt/couchdb/etc/local.ini to use the proper https certificates, but i > > can't get a connection to https://mydomain.com:5984 going at all. > > there is nothing of use in /var/log/couchdb/couchdb.log, > > and all i get in the browser is a connection timedout error. > > > > can someone please help me? > > my entire stack of business logic that i had built to run on top of > couchdb > > is unusable at the moment.. > >
