Well this is weird… my couchdb server was having pretty much the same issue as yours today.
CouchDB log file said this when I tried to load Fauxton: [error] 2020-04-24T21:06:02.289764Z [email protected] <0.27393.0> -------- application: mochiweb, "Accept failed error", "{error,{options,{keyfile,\"/opt/couchdb/letsencrypt/live/cherrypc.com/privkey.pem\",\n {error,eacces}}}}" [error] 2020-04-24T21:06:02.290000Z [email protected] <0.27393.0> -------- CRASH REPORT Process (<0.27393.0>) with 0 neighbors exited with reason: {error,accept_failed} at mochiweb_acceptor:init/4(line:71) <= proc_lib:init_p_do_apply/3(line:247); initial_call: {mochiweb_acceptor,init,['Argument__1','Argument__2',...]}, ancestors: [https,couch_secondary_services,couch_sup,...], message_queue_len: 0, messages: [], links: [<0.254.0>], dictionary: [], trap_exit: false, status: running, heap_size: 1598, stack_size: 27, reductions: 1983 I ran certbot a few times and it didn’t fix it. It told me the certs were fine. I looked at the cert files and found that the ownership on the new certs were different than the old ones and so were the permissions on the chain.pem. me@couchdb:~$ sudo ls -l /opt/couchdb/letsencrypt/archive/cherrypc.com/ -rw------- 1 couchdb root 1903 Jan 25 19:18 cert4.pem -rw-r--r-- 1 root root 1903 Apr 24 19:40 cert5.pem -rw-r--r-- 1 couchdb root 1647 Jan 25 19:18 chain4.pem -rw-r--r-- 1 root root 1647 Apr 24 19:40 chain5.pem -rw------- 1 couchdb root 3550 Jan 25 19:18 fullchain4.pem -rw-r--r-- 1 root root 3550 Apr 24 19:40 fullchain5.pem -rw------- 1 couchdb root 1704 Jan 25 19:18 privkey4.pem -rw------- 1 root root 1704 Apr 24 19:40 privkey5.pem I made these changes 1st change... sudo chown couchdb:root /opt/couchdb/letsencrypt/archive/cherrypc.com/cert5.pem <http://cherrypc.com/cert5.pem> sudo chown couchdb:root /opt/couchdb/letsencrypt/archive/cherrypc.com/chain5.pem sudo chown couchdb:root /opt/couchdb/letsencrypt/archive/cherrypc.com/fullchain5.pem sudo chown couchdb:root /opt/couchdb/letsencrypt/archive/cherrypc.com/privkey5.pem 2nd change... sudo chmod 600 /opt/couchdb/letsencrypt/archive/cherrypc.com/fullchain5.pem <http://cherrypc.com/fullchain5.pem> And restarted CouchDB: sudo /etc/init.d/couchdb restart That got me back up and running. So, I think what may have happened is the cert was auto renewed this morning and when that happened the ownership and permissions were not set correctly on the new certs. I don’t know if this will help you, but it’s worth checking into. — Bill
