Re: can't get couchdb to work on https

[Rene Veerman]

i'm still having problems getting nginx to work for my couchdb + https
setup.. i've followed https://konstruktor.ee/couchdb-setup-on-ubuntu/

as
advertised on the couchdb mailinglist a few weeks ago, but i can't get
nginx to actually work.. can anyone here help me with that please?
[image: konstruktor.ee]konstruktor.ee
CouchDB 3 setup on Ubuntu 18.04

Setting up a CouchDB 3 instance on Ubuntu 18.04.
2 replies 
Last reply today at 9:36 AMView thread
Rene Veerman   4:59 PM

please note that i'm using ubuntu 20.04, i don't know if that matters
5:00 
systemctl status nginx.service returns :
5:01 
jun 22 16:56:53 albatross nginx[187333]: nginx: [warn] the "ssl" directive
is deprecated, use the "listen ... ssl" d>
jun 22 16:56:53 albatross nginx[187333]: nginx: [emerg] cannot load
certificate "/etc/letsencrypt/live/couchdb.upcou>
jun 22 16:56:53 albatross systemd[1]: nginx.service: Control process
exited, code=exited, status=1/FAILURE
jun 22 16:56:53 albatross systemd[1]: Reload failed for A high performance
web server and a reverse proxy server.
5:01 
please also note that i have https certificates from my domain registrar,
and i don't know if i should be using those if some form or another...

On Fri, May 22, 2020 at 12:04 PM Robert Samuel Newson 
wrote:

> Hi,
>
> Your Slack account is reactivated. Welcome back.
>
> B.
>
> > On 22 May 2020, at 10:16, Rene Veerman  wrote:
> >
> > sorry. i didn't know i was talking to a foundation-level organisation.
> >
> > i'm very sorry about what happened the other days over at slack.
> >
> > please re-instate me when you have some time for that.
> >
> > i'm most willing to learn more than i already know about systems
> > administration.
> >
> > in fact, i must do that (i only know web-browser-level coding so far), in
> > order to make my company grow and flourish.
> >
> > i will never repeat the mistakes i made the other day again.
> >
> > On Fri, May 22, 2020 at 10:17 AM Robert Samuel Newson <
> rnew...@apache.org>
> > wrote:
> >
> >> Hi Rene,
> >>
> >> I ejected you from couchdb.slack.com for good reason, you were being
> rude
> >> and abusive towards myself and others after we had spend many hours
> trying
> >> to assist you.
> >>
> >> Everyone here, and in Slack, is volunteering their time, for free, to
> help
> >> users or potential users of CouchDB. None of us owe you our time or
> >> assistance and it has been withdrawn solely because of your behaviour.
> >>
> >> We are not expecting humility or deference from you or anyone else, only
> >> polite, thoughtful engagement with those seeking to help you.
> >>
> >> With all that said, and depending on your response to my feedback here,
> I
> >> am willing to reinstate you on Slack on a trial basis. Any further
> descent
> >> into abuse on your part and I will remove you from Slack permanently and
> >> from our mailing lists.
> >>
> >> Sincerely,
> >>
> >> Robert Samuel Newson
> >>
> >> Apache CouchDB PMC Member
> >> Member of the Apache Software Foundation
> >>
> >>
> >>> On 22 May 2020, at 02:38, Rene Veerman 
> wrote:
> >>>
> >>> i need user rnewson to unblock me on the slack feed of couchdb
> though.. i
> >>> need his help to even test this.
> >>>
> >>> On Fri, May 22, 2020 at 12:57 AM Rene Veerman  >
> >>> wrote:
> >>>
>  i've found some time on my company's agenda, and i *might* be able to
>  look into this issue over the next few days :)
> 
>  On Wed, May 20, 2020 at 5:18 PM Rene Veerman  >
>  wrote:
> 
> > ehm, Bill & the rest of the couchdb team
> >
> > i have a company to run.
> >
> > so i can't test the solution you provided, at this time.
> >
> > i don't know when i'll be able to. sorry.
> >
> >
> > On Wed, May 20, 2020 at 3:42 AM Rene Veerman <
> seductivea...@gmail.com>
> > wrote:
> >
> >> thanks, Bill :)
> >>
> >> i'll look into it within the next few days :)
> >>
> >> On Fri, May 15, 2020 at 8:18 PM Bill Stephenson
> >>  wrote:
> >>
> >>> I don’t check into Reddit much but I saw this post there today
> that’s
> >>> worth checking into:
> >>>
> >>> CouchDB 3 setup on Ubuntu 18.04 <
> >>> https://konstruktor.ee/couchdb-setup-on-ubuntu/>
> >>>
> >>>
> >>>
> >>> Kindest Regards,
> >>>
> >>> Bill Stephenson
> >>> Tech Support
> >>> www.cherrypc.com 
> >>> 1-417-546-8390
> >>>
> >>>
> >>>
> >>>
>  On May 2, 2020, at 9:38 PM, 

Re: can't get couchdb to work on https

[Robert Samuel Newson]

Hi,

Your Slack account is reactivated. Welcome back.

B.

> On 22 May 2020, at 10:16, Rene Veerman  wrote:
> 
> sorry. i didn't know i was talking to a foundation-level organisation.
> 
> i'm very sorry about what happened the other days over at slack.
> 
> please re-instate me when you have some time for that.
> 
> i'm most willing to learn more than i already know about systems
> administration.
> 
> in fact, i must do that (i only know web-browser-level coding so far), in
> order to make my company grow and flourish.
> 
> i will never repeat the mistakes i made the other day again.
> 
> On Fri, May 22, 2020 at 10:17 AM Robert Samuel Newson 
> wrote:
> 
>> Hi Rene,
>> 
>> I ejected you from couchdb.slack.com for good reason, you were being rude
>> and abusive towards myself and others after we had spend many hours trying
>> to assist you.
>> 
>> Everyone here, and in Slack, is volunteering their time, for free, to help
>> users or potential users of CouchDB. None of us owe you our time or
>> assistance and it has been withdrawn solely because of your behaviour.
>> 
>> We are not expecting humility or deference from you or anyone else, only
>> polite, thoughtful engagement with those seeking to help you.
>> 
>> With all that said, and depending on your response to my feedback here, I
>> am willing to reinstate you on Slack on a trial basis. Any further descent
>> into abuse on your part and I will remove you from Slack permanently and
>> from our mailing lists.
>> 
>> Sincerely,
>> 
>> Robert Samuel Newson
>> 
>> Apache CouchDB PMC Member
>> Member of the Apache Software Foundation
>> 
>> 
>>> On 22 May 2020, at 02:38, Rene Veerman  wrote:
>>> 
>>> i need user rnewson to unblock me on the slack feed of couchdb though.. i
>>> need his help to even test this.
>>> 
>>> On Fri, May 22, 2020 at 12:57 AM Rene Veerman 
>>> wrote:
>>> 
 i've found some time on my company's agenda, and i *might* be able to
 look into this issue over the next few days :)
 
 On Wed, May 20, 2020 at 5:18 PM Rene Veerman 
 wrote:
 
> ehm, Bill & the rest of the couchdb team
> 
> i have a company to run.
> 
> so i can't test the solution you provided, at this time.
> 
> i don't know when i'll be able to. sorry.
> 
> 
> On Wed, May 20, 2020 at 3:42 AM Rene Veerman 
> wrote:
> 
>> thanks, Bill :)
>> 
>> i'll look into it within the next few days :)
>> 
>> On Fri, May 15, 2020 at 8:18 PM Bill Stephenson
>>  wrote:
>> 
>>> I don’t check into Reddit much but I saw this post there today that’s
>>> worth checking into:
>>> 
>>> CouchDB 3 setup on Ubuntu 18.04 <
>>> https://konstruktor.ee/couchdb-setup-on-ubuntu/>
>>> 
>>> 
>>> 
>>> Kindest Regards,
>>> 
>>> Bill Stephenson
>>> Tech Support
>>> www.cherrypc.com 
>>> 1-417-546-8390
>>> 
>>> 
>>> 
>>> 
 On May 2, 2020, at 9:38 PM, Bill Stephenson
>> 
>>> wrote:
 
 Thank you Joan!
 
 I’ll look into both those suggestions when I get a chance and I’ll
>>> report back on the results.
 
 Kindest Regards,
 
 Bill Stephenson
 Tech Support
 www.cherrypc.com 
 1-417-546-8390
 
 
 
 
> On May 1, 2020, at 2:26 PM, Joan Touzet  wrote:
> 
> Hi Bill,
> 
> haproxy should be as simple as installing the binary on your *NIX
>>> platform, then using something similar to our shipped configuration:
> 
> 
>>> 
>> https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
> 
> 
> Also, I see this walkthrough is referenced elsewhere as working for
>>> Let's Encrypt and CouchDB:
> 
> 
>>> 
>> https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
> 
> Hope they help,
> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet
 
>>> 
>>> 
>> 
>> 

Re: can't get couchdb to work on https

[Rene Veerman]

sorry. i didn't know i was talking to a foundation-level organisation.

i'm very sorry about what happened the other days over at slack.

please re-instate me when you have some time for that.

i'm most willing to learn more than i already know about systems
administration.

in fact, i must do that (i only know web-browser-level coding so far), in
order to make my company grow and flourish.

i will never repeat the mistakes i made the other day again.

On Fri, May 22, 2020 at 10:17 AM Robert Samuel Newson 
wrote:

> Hi Rene,
>
> I ejected you from couchdb.slack.com for good reason, you were being rude
> and abusive towards myself and others after we had spend many hours trying
> to assist you.
>
> Everyone here, and in Slack, is volunteering their time, for free, to help
> users or potential users of CouchDB. None of us owe you our time or
> assistance and it has been withdrawn solely because of your behaviour.
>
> We are not expecting humility or deference from you or anyone else, only
> polite, thoughtful engagement with those seeking to help you.
>
> With all that said, and depending on your response to my feedback here, I
> am willing to reinstate you on Slack on a trial basis. Any further descent
> into abuse on your part and I will remove you from Slack permanently and
> from our mailing lists.
>
> Sincerely,
>
> Robert Samuel Newson
>
> Apache CouchDB PMC Member
> Member of the Apache Software Foundation
>
>
> > On 22 May 2020, at 02:38, Rene Veerman  wrote:
> >
> > i need user rnewson to unblock me on the slack feed of couchdb though.. i
> > need his help to even test this.
> >
> > On Fri, May 22, 2020 at 12:57 AM Rene Veerman 
> > wrote:
> >
> >> i've found some time on my company's agenda, and i *might* be able to
> >> look into this issue over the next few days :)
> >>
> >> On Wed, May 20, 2020 at 5:18 PM Rene Veerman 
> >> wrote:
> >>
> >>> ehm, Bill & the rest of the couchdb team
> >>>
> >>> i have a company to run.
> >>>
> >>> so i can't test the solution you provided, at this time.
> >>>
> >>> i don't know when i'll be able to. sorry.
> >>>
> >>>
> >>> On Wed, May 20, 2020 at 3:42 AM Rene Veerman 
> >>> wrote:
> >>>
>  thanks, Bill :)
> 
>  i'll look into it within the next few days :)
> 
>  On Fri, May 15, 2020 at 8:18 PM Bill Stephenson
>   wrote:
> 
> > I don’t check into Reddit much but I saw this post there today that’s
> > worth checking into:
> >
> > CouchDB 3 setup on Ubuntu 18.04 <
> > https://konstruktor.ee/couchdb-setup-on-ubuntu/>
> >
> >
> >
> > Kindest Regards,
> >
> > Bill Stephenson
> > Tech Support
> > www.cherrypc.com 
> > 1-417-546-8390
> >
> >
> >
> >
> >> On May 2, 2020, at 9:38 PM, Bill Stephenson
> 
> > wrote:
> >>
> >> Thank you Joan!
> >>
> >> I’ll look into both those suggestions when I get a chance and I’ll
> > report back on the results.
> >>
> >> Kindest Regards,
> >>
> >> Bill Stephenson
> >> Tech Support
> >> www.cherrypc.com 
> >> 1-417-546-8390
> >>
> >>
> >>
> >>
> >>> On May 1, 2020, at 2:26 PM, Joan Touzet  wrote:
> >>>
> >>> Hi Bill,
> >>>
> >>> haproxy should be as simple as installing the binary on your *NIX
> > platform, then using something similar to our shipped configuration:
> >>>
> >>>
> >
> https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
> >>>
> >>>
> >>> Also, I see this walkthrough is referenced elsewhere as working for
> > Let's Encrypt and CouchDB:
> >>>
> >>>
> >
> https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
> >>>
> >>> Hope they help,
> >>> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet
> >>
> >
> >
>
>

Re: can't get couchdb to work on https

[Robert Samuel Newson]

Hi Rene,

I ejected you from couchdb.slack.com for good reason, you were being rude and 
abusive towards myself and others after we had spend many hours trying to 
assist you.

Everyone here, and in Slack, is volunteering their time, for free, to help 
users or potential users of CouchDB. None of us owe you our time or assistance 
and it has been withdrawn solely because of your behaviour.

We are not expecting humility or deference from you or anyone else, only 
polite, thoughtful engagement with those seeking to help you.

With all that said, and depending on your response to my feedback here, I am 
willing to reinstate you on Slack on a trial basis. Any further descent into 
abuse on your part and I will remove you from Slack permanently and from our 
mailing lists.

Sincerely,

Robert Samuel Newson

Apache CouchDB PMC Member
Member of the Apache Software Foundation


> On 22 May 2020, at 02:38, Rene Veerman  wrote:
> 
> i need user rnewson to unblock me on the slack feed of couchdb though.. i
> need his help to even test this.
> 
> On Fri, May 22, 2020 at 12:57 AM Rene Veerman 
> wrote:
> 
>> i've found some time on my company's agenda, and i *might* be able to
>> look into this issue over the next few days :)
>> 
>> On Wed, May 20, 2020 at 5:18 PM Rene Veerman 
>> wrote:
>> 
>>> ehm, Bill & the rest of the couchdb team
>>> 
>>> i have a company to run.
>>> 
>>> so i can't test the solution you provided, at this time.
>>> 
>>> i don't know when i'll be able to. sorry.
>>> 
>>> 
>>> On Wed, May 20, 2020 at 3:42 AM Rene Veerman 
>>> wrote:
>>> 
 thanks, Bill :)
 
 i'll look into it within the next few days :)
 
 On Fri, May 15, 2020 at 8:18 PM Bill Stephenson
  wrote:
 
> I don’t check into Reddit much but I saw this post there today that’s
> worth checking into:
> 
> CouchDB 3 setup on Ubuntu 18.04 <
> https://konstruktor.ee/couchdb-setup-on-ubuntu/>
> 
> 
> 
> Kindest Regards,
> 
> Bill Stephenson
> Tech Support
> www.cherrypc.com 
> 1-417-546-8390
> 
> 
> 
> 
>> On May 2, 2020, at 9:38 PM, Bill Stephenson 
> wrote:
>> 
>> Thank you Joan!
>> 
>> I’ll look into both those suggestions when I get a chance and I’ll
> report back on the results.
>> 
>> Kindest Regards,
>> 
>> Bill Stephenson
>> Tech Support
>> www.cherrypc.com 
>> 1-417-546-8390
>> 
>> 
>> 
>> 
>>> On May 1, 2020, at 2:26 PM, Joan Touzet  wrote:
>>> 
>>> Hi Bill,
>>> 
>>> haproxy should be as simple as installing the binary on your *NIX
> platform, then using something similar to our shipped configuration:
>>> 
>>> 
> https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
>>> 
>>> 
>>> Also, I see this walkthrough is referenced elsewhere as working for
> Let's Encrypt and CouchDB:
>>> 
>>> 
> https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
>>> 
>>> Hope they help,
>>> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet
>> 
> 
> 

Re: can't get couchdb to work on https

[Rene Veerman]

i need user rnewson to unblock me on the slack feed of couchdb though.. i
need his help to even test this.

On Fri, May 22, 2020 at 12:57 AM Rene Veerman 
wrote:

> i've found some time on my company's agenda, and i *might* be able to
> look into this issue over the next few days :)
>
> On Wed, May 20, 2020 at 5:18 PM Rene Veerman 
> wrote:
>
>> ehm, Bill & the rest of the couchdb team
>>
>> i have a company to run.
>>
>> so i can't test the solution you provided, at this time.
>>
>> i don't know when i'll be able to. sorry.
>>
>>
>> On Wed, May 20, 2020 at 3:42 AM Rene Veerman 
>> wrote:
>>
>>> thanks, Bill :)
>>>
>>> i'll look into it within the next few days :)
>>>
>>> On Fri, May 15, 2020 at 8:18 PM Bill Stephenson
>>>  wrote:
>>>
 I don’t check into Reddit much but I saw this post there today that’s
 worth checking into:

 CouchDB 3 setup on Ubuntu 18.04 <
 https://konstruktor.ee/couchdb-setup-on-ubuntu/>



 Kindest Regards,

 Bill Stephenson
 Tech Support
 www.cherrypc.com 
 1-417-546-8390




 > On May 2, 2020, at 9:38 PM, Bill Stephenson 
 wrote:
 >
 > Thank you Joan!
 >
 > I’ll look into both those suggestions when I get a chance and I’ll
 report back on the results.
 >
 > Kindest Regards,
 >
 > Bill Stephenson
 > Tech Support
 > www.cherrypc.com 
 > 1-417-546-8390
 >
 >
 >
 >
 >> On May 1, 2020, at 2:26 PM, Joan Touzet  wrote:
 >>
 >> Hi Bill,
 >>
 >> haproxy should be as simple as installing the binary on your *NIX
 platform, then using something similar to our shipped configuration:
 >>
 >>
 https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
 >>
 >>
 >> Also, I see this walkthrough is referenced elsewhere as working for
 Let's Encrypt and CouchDB:
 >>
 >>
 https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
 >>
 >> Hope they help,
 >> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet
 >

Re: can't get couchdb to work on https

[Rene Veerman]

i've found some time on my company's agenda, and i *might* be able to look
into this issue over the next few days :)

On Wed, May 20, 2020 at 5:18 PM Rene Veerman 
wrote:

> ehm, Bill & the rest of the couchdb team
>
> i have a company to run.
>
> so i can't test the solution you provided, at this time.
>
> i don't know when i'll be able to. sorry.
>
>
> On Wed, May 20, 2020 at 3:42 AM Rene Veerman 
> wrote:
>
>> thanks, Bill :)
>>
>> i'll look into it within the next few days :)
>>
>> On Fri, May 15, 2020 at 8:18 PM Bill Stephenson 
>> wrote:
>>
>>> I don’t check into Reddit much but I saw this post there today that’s
>>> worth checking into:
>>>
>>> CouchDB 3 setup on Ubuntu 18.04 <
>>> https://konstruktor.ee/couchdb-setup-on-ubuntu/>
>>>
>>>
>>>
>>> Kindest Regards,
>>>
>>> Bill Stephenson
>>> Tech Support
>>> www.cherrypc.com 
>>> 1-417-546-8390
>>>
>>>
>>>
>>>
>>> > On May 2, 2020, at 9:38 PM, Bill Stephenson 
>>> wrote:
>>> >
>>> > Thank you Joan!
>>> >
>>> > I’ll look into both those suggestions when I get a chance and I’ll
>>> report back on the results.
>>> >
>>> > Kindest Regards,
>>> >
>>> > Bill Stephenson
>>> > Tech Support
>>> > www.cherrypc.com 
>>> > 1-417-546-8390
>>> >
>>> >
>>> >
>>> >
>>> >> On May 1, 2020, at 2:26 PM, Joan Touzet  wrote:
>>> >>
>>> >> Hi Bill,
>>> >>
>>> >> haproxy should be as simple as installing the binary on your *NIX
>>> platform, then using something similar to our shipped configuration:
>>> >>
>>> >>
>>> https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
>>> >>
>>> >>
>>> >> Also, I see this walkthrough is referenced elsewhere as working for
>>> Let's Encrypt and CouchDB:
>>> >>
>>> >>
>>> https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
>>> >>
>>> >> Hope they help,
>>> >> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet
>>> >
>>>
>>>

Re: can't get couchdb to work on https

[Rene Veerman]

ehm, Bill & the rest of the couchdb team

i have a company to run.

so i can't test the solution you provided, at this time.

i don't know when i'll be able to. sorry.


On Wed, May 20, 2020 at 3:42 AM Rene Veerman 
wrote:

> thanks, Bill :)
>
> i'll look into it within the next few days :)
>
> On Fri, May 15, 2020 at 8:18 PM Bill Stephenson 
> wrote:
>
>> I don’t check into Reddit much but I saw this post there today that’s
>> worth checking into:
>>
>> CouchDB 3 setup on Ubuntu 18.04 <
>> https://konstruktor.ee/couchdb-setup-on-ubuntu/>
>>
>>
>>
>> Kindest Regards,
>>
>> Bill Stephenson
>> Tech Support
>> www.cherrypc.com 
>> 1-417-546-8390
>>
>>
>>
>>
>> > On May 2, 2020, at 9:38 PM, Bill Stephenson 
>> wrote:
>> >
>> > Thank you Joan!
>> >
>> > I’ll look into both those suggestions when I get a chance and I’ll
>> report back on the results.
>> >
>> > Kindest Regards,
>> >
>> > Bill Stephenson
>> > Tech Support
>> > www.cherrypc.com 
>> > 1-417-546-8390
>> >
>> >
>> >
>> >
>> >> On May 1, 2020, at 2:26 PM, Joan Touzet  wrote:
>> >>
>> >> Hi Bill,
>> >>
>> >> haproxy should be as simple as installing the binary on your *NIX
>> platform, then using something similar to our shipped configuration:
>> >>
>> >>
>> https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
>> >>
>> >>
>> >> Also, I see this walkthrough is referenced elsewhere as working for
>> Let's Encrypt and CouchDB:
>> >>
>> >>
>> https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
>> >>
>> >> Hope they help,
>> >> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet
>> >
>>
>>

Re: can't get couchdb to work on https

[Rene Veerman]

thanks, Bill :)

i'll look into it within the next few days :)

On Fri, May 15, 2020 at 8:18 PM Bill Stephenson 
wrote:

> I don’t check into Reddit much but I saw this post there today that’s
> worth checking into:
>
> CouchDB 3 setup on Ubuntu 18.04 <
> https://konstruktor.ee/couchdb-setup-on-ubuntu/>
>
>
>
> Kindest Regards,
>
> Bill Stephenson
> Tech Support
> www.cherrypc.com 
> 1-417-546-8390
>
>
>
>
> > On May 2, 2020, at 9:38 PM, Bill Stephenson 
> wrote:
> >
> > Thank you Joan!
> >
> > I’ll look into both those suggestions when I get a chance and I’ll
> report back on the results.
> >
> > Kindest Regards,
> >
> > Bill Stephenson
> > Tech Support
> > www.cherrypc.com 
> > 1-417-546-8390
> >
> >
> >
> >
> >> On May 1, 2020, at 2:26 PM, Joan Touzet  wrote:
> >>
> >> Hi Bill,
> >>
> >> haproxy should be as simple as installing the binary on your *NIX
> platform, then using something similar to our shipped configuration:
> >>
> >>
> https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
> >>
> >>
> >> Also, I see this walkthrough is referenced elsewhere as working for
> Let's Encrypt and CouchDB:
> >>
> >>
> https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
> >>
> >> Hope they help,
> >> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet
> >
>
>

Re: can't get couchdb to work on https

[Bill Stephenson]

I don’t check into Reddit much but I saw this post there today that’s worth 
checking into:

CouchDB 3 setup on Ubuntu 18.04 




Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390




> On May 2, 2020, at 9:38 PM, Bill Stephenson  wrote:
> 
> Thank you Joan!
> 
> I’ll look into both those suggestions when I get a chance and I’ll report 
> back on the results.
> 
> Kindest Regards,
> 
> Bill Stephenson
> Tech Support
> www.cherrypc.com 
> 1-417-546-8390
> 
> 
> 
> 
>> On May 1, 2020, at 2:26 PM, Joan Touzet  wrote:
>> 
>> Hi Bill,
>> 
>> haproxy should be as simple as installing the binary on your *NIX platform, 
>> then using something similar to our shipped configuration:
>> 
>> https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
>> 
>> 
>> Also, I see this walkthrough is referenced elsewhere as working for Let's 
>> Encrypt and CouchDB:
>> 
>> https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
>> 
>> Hope they help,
>> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet
> 

Re: can't get couchdb to work on https

[Bill Stephenson]

Thank you Joan!

I’ll look into both those suggestions when I get a chance and I’ll report back 
on the results.

Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390




> On May 1, 2020, at 2:26 PM, Joan Touzet  wrote:
> 
> Hi Bill,
> 
> haproxy should be as simple as installing the binary on your *NIX platform, 
> then using something similar to our shipped configuration:
> 
> https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
> 
> 
> Also, I see this walkthrough is referenced elsewhere as working for Let's 
> Encrypt and CouchDB:
> 
> https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
> 
> Hope they help,
> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet

Re: can't get couchdb to work on https

[Joan Touzet]

Yup! Scroll a little bit down in our docs and we provide a minimal 
working config for Nginx. As the docs say:


"Proxy buffering must be disabled, or continuous replication will not 
function correctly behind nginx."


https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-nginx

-Joan "lisp machines are fun" Touzet

On 2020-05-01 15:29, Joel Jucá wrote:

You can make this setup using Nginx too. I'm unsure about haproxy but Nginx
is quite trivial to setup.

On Fri, May 1, 2020 at 4:26 PM Joan Touzet  wrote:


Hi Bill,

haproxy should be as simple as installing the binary on your *NIX
platform, then using something similar to our shipped configuration:


https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy


Also, I see this walkthrough is referenced elsewhere as working for
Let's Encrypt and CouchDB:


https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/

Hope they help,
Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet

On 2020-05-01 15:16, Bill Stephenson wrote:

FWIW, I tried the instructions I provided earlier this week and didn’t

get them to work again. I don’t know if it’s a change made by Let’s Encrypt
or I forget exactly what I did.


I’ll go through the process setting up a Digital Ocean vps again as soon

as I get some time because getting those certs configured has always been a
bit of a pain and it’d be a good thing to nail that process down.


If anyone has a list of instruction on setting up haproxy they can share

I’d be glad to have them and give that a shot too.



Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390





On Apr 30, 2020, at 3:56 PM, Joan Touzet  wrote:

On 2020-04-30 16:22, Rene Veerman wrote:

i'm really only looking for a quick and easy way to getting https to

work

again..


Bill Stephenson gave you a step-by-step that seemed reasonable to me.


do the creators of couchdb read this mailinglist?


Yes.

Most of us terminate SSL ahead of CouchDB at a reverse proxy (such as

haproxy). Some of us have even contemplated dropping native SSL support in
CouchDB entirely, because configuring it is a bit of a pain, as you've
found. But it can be done, and it does work.


For SSL in pure CouchDB, when I must, I use something like EasyRSA:

   https://github.com/OpenVPN/easy-rsa

to generate the certs, then munge them together and start it. It works

OK. But I do this about once every 2 years max.


-Joan "Erlang's SSL support isn't great" Touzet



On Sun, Apr 26, 2020 at 3:04 PM Joel Jucá 

wrote:

Rene,

Your problem seems to be infrastructure-related, rather than CouchDB
related. I would recommend you to read about Infrastructure as Code.

This

is a practice that allows a developer to declare its infrastructure

(in

your specific case, server configuration) and have some sort of
reproducibility from it. Then, you could also understand every single
change made to your server infrastructure - and even share it as a

Gist,

for instance, and have some sort of feedback/pull request directly on

it.


I would recommend you Ansible (
https://www.ansible.com/resources/get-started).
It's a great solution that allows you to declare your server

configuration

as YAML files and use it within Ansible CLI to reproduce the declared
configuration on a targeted server (eg: your Ubuntu-powered CouchDB
server).

I've struggled a lot with server configuration back in 2010-2012 when

I was

a full-stack PHP/Drupal developer, and after discovering Ansible I

could

never imagine myself handling performing a complex task (server
configuration) manually!

I hope it helps you in some way.

On Sat, Apr 25, 2020 at 6:28 PM Rene Veerman 


wrote:


yes, i did..

On Sat, Apr 25, 2020 at 9:16 PM Bill Stephenson




wrote:


Did you do a "sudo ufw allow 6984”?


Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390





On Apr 25, 2020, at 9:28 AM, Rene Veerman 


wrote:


also (FYI) : i have already entered the right port forwarding

commands

into

my ADSL modem..

On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman <

seductivea...@gmail.com>

wrote:


that gets me a 'connection refused' :

('albatross' === localhost === nicer.app)

root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
Trying 127.0.0.1...
Trying 82.161.37.94...
telnet: Unable to connect to remote host: Connection refused
root@albatross:/opt/couchdb/letsencrypt#

On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher <

st...@meredrica.org>

wrote:


Did you try to telnet to the port while couchdb is down? If there

is

no

open port, telnet won't connect.


On 

Re: can't get couchdb to work on https

[Joel Jucá]

You can make this setup using Nginx too. I'm unsure about haproxy but Nginx
is quite trivial to setup.

On Fri, May 1, 2020 at 4:26 PM Joan Touzet  wrote:

> Hi Bill,
>
> haproxy should be as simple as installing the binary on your *NIX
> platform, then using something similar to our shipped configuration:
>
>
> https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy
>
>
> Also, I see this walkthrough is referenced elsewhere as working for
> Let's Encrypt and CouchDB:
>
>
> https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/
>
> Hope they help,
> Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet
>
> On 2020-05-01 15:16, Bill Stephenson wrote:
> > FWIW, I tried the instructions I provided earlier this week and didn’t
> get them to work again. I don’t know if it’s a change made by Let’s Encrypt
> or I forget exactly what I did.
> >
> > I’ll go through the process setting up a Digital Ocean vps again as soon
> as I get some time because getting those certs configured has always been a
> bit of a pain and it’d be a good thing to nail that process down.
> >
> > If anyone has a list of instruction on setting up haproxy they can share
> I’d be glad to have them and give that a shot too.
> >
> >
> > Kindest Regards,
> >
> > Bill Stephenson
> > Tech Support
> > www.cherrypc.com 
> > 1-417-546-8390
> >
> >
> >
> >
> >> On Apr 30, 2020, at 3:56 PM, Joan Touzet  wrote:
> >>
> >> On 2020-04-30 16:22, Rene Veerman wrote:
> >>> i'm really only looking for a quick and easy way to getting https to
> work
> >>> again..
> >>
> >> Bill Stephenson gave you a step-by-step that seemed reasonable to me.
> >>
> >>> do the creators of couchdb read this mailinglist?
> >>
> >> Yes.
> >>
> >> Most of us terminate SSL ahead of CouchDB at a reverse proxy (such as
> haproxy). Some of us have even contemplated dropping native SSL support in
> CouchDB entirely, because configuring it is a bit of a pain, as you've
> found. But it can be done, and it does work.
> >>
> >> For SSL in pure CouchDB, when I must, I use something like EasyRSA:
> >>
> >>   https://github.com/OpenVPN/easy-rsa
> >>
> >> to generate the certs, then munge them together and start it. It works
> OK. But I do this about once every 2 years max.
> >>
> >> -Joan "Erlang's SSL support isn't great" Touzet
> >>
> >>
> >>> On Sun, Apr 26, 2020 at 3:04 PM Joel Jucá 
> wrote:
>  Rene,
> 
>  Your problem seems to be infrastructure-related, rather than CouchDB
>  related. I would recommend you to read about Infrastructure as Code.
> This
>  is a practice that allows a developer to declare its infrastructure
> (in
>  your specific case, server configuration) and have some sort of
>  reproducibility from it. Then, you could also understand every single
>  change made to your server infrastructure - and even share it as a
> Gist,
>  for instance, and have some sort of feedback/pull request directly on
> it.
> 
>  I would recommend you Ansible (
>  https://www.ansible.com/resources/get-started).
>  It's a great solution that allows you to declare your server
> configuration
>  as YAML files and use it within Ansible CLI to reproduce the declared
>  configuration on a targeted server (eg: your Ubuntu-powered CouchDB
>  server).
> 
>  I've struggled a lot with server configuration back in 2010-2012 when
> I was
>  a full-stack PHP/Drupal developer, and after discovering Ansible I
> could
>  never imagine myself handling performing a complex task (server
>  configuration) manually!
> 
>  I hope it helps you in some way.
> 
>  On Sat, Apr 25, 2020 at 6:28 PM Rene Veerman  >
>  wrote:
> 
> > yes, i did..
> >
> > On Sat, Apr 25, 2020 at 9:16 PM Bill Stephenson
>   >>
> > wrote:
> >
> >> Did you do a "sudo ufw allow 6984”?
> >>
> >>
> >> Kindest Regards,
> >>
> >> Bill Stephenson
> >> Tech Support
> >> www.cherrypc.com 
> >> 1-417-546-8390
> >>
> >>
> >>
> >>
> >>> On Apr 25, 2020, at 9:28 AM, Rene Veerman  >
> >> wrote:
> >>>
> >>> also (FYI) : i have already entered the right port forwarding
>  commands
> >> into
> >>> my ADSL modem..
> >>>
> >>> On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman <
>  seductivea...@gmail.com>
> >>> wrote:
> >>>
>  that gets me a 'connection refused' :
> 
>  ('albatross' === localhost === nicer.app)
> 
>  root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
>  root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
>  Trying 127.0.0.1...
>  telnet: Unable to connect to remote host: Connection refused
>  root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
>  Trying 

Re: can't get couchdb to work on https

[Joan Touzet]

Hi Bill,

haproxy should be as simple as installing the binary on your *NIX 
platform, then using something similar to our shipped configuration:


https://docs.couchdb.org/en/latest/best-practices/reverse-proxies.html?highlight=haproxy#reverse-proxying-with-haproxy


Also, I see this walkthrough is referenced elsewhere as working for 
Let's Encrypt and CouchDB:


https://www.joshmorony.com/creating-a-couchdb-database-on-an-ubuntu-server-digital-ocean/

Hope they help,
Joan "3.0.1 and 3.1.0 out hopefully next week" Touzet

On 2020-05-01 15:16, Bill Stephenson wrote:

FWIW, I tried the instructions I provided earlier this week and didn’t get them 
to work again. I don’t know if it’s a change made by Let’s Encrypt or I forget 
exactly what I did.

I’ll go through the process setting up a Digital Ocean vps again as soon as I 
get some time because getting those certs configured has always been a bit of a 
pain and it’d be a good thing to nail that process down.

If anyone has a list of instruction on setting up haproxy they can share I’d be 
glad to have them and give that a shot too.


Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390





On Apr 30, 2020, at 3:56 PM, Joan Touzet  wrote:

On 2020-04-30 16:22, Rene Veerman wrote:

i'm really only looking for a quick and easy way to getting https to work
again..


Bill Stephenson gave you a step-by-step that seemed reasonable to me.


do the creators of couchdb read this mailinglist?


Yes.

Most of us terminate SSL ahead of CouchDB at a reverse proxy (such as haproxy). 
Some of us have even contemplated dropping native SSL support in CouchDB 
entirely, because configuring it is a bit of a pain, as you've found. But it 
can be done, and it does work.

For SSL in pure CouchDB, when I must, I use something like EasyRSA:

  https://github.com/OpenVPN/easy-rsa

to generate the certs, then munge them together and start it. It works OK. But 
I do this about once every 2 years max.

-Joan "Erlang's SSL support isn't great" Touzet



On Sun, Apr 26, 2020 at 3:04 PM Joel Jucá  wrote:

Rene,

Your problem seems to be infrastructure-related, rather than CouchDB
related. I would recommend you to read about Infrastructure as Code. This
is a practice that allows a developer to declare its infrastructure (in
your specific case, server configuration) and have some sort of
reproducibility from it. Then, you could also understand every single
change made to your server infrastructure - and even share it as a Gist,
for instance, and have some sort of feedback/pull request directly on it.

I would recommend you Ansible (
https://www.ansible.com/resources/get-started).
It's a great solution that allows you to declare your server configuration
as YAML files and use it within Ansible CLI to reproduce the declared
configuration on a targeted server (eg: your Ubuntu-powered CouchDB
server).

I've struggled a lot with server configuration back in 2010-2012 when I was
a full-stack PHP/Drupal developer, and after discovering Ansible I could
never imagine myself handling performing a complex task (server
configuration) manually!

I hope it helps you in some way.

On Sat, Apr 25, 2020 at 6:28 PM Rene Veerman 
wrote:


yes, i did..

On Sat, Apr 25, 2020 at 9:16 PM Bill Stephenson




wrote:


Did you do a "sudo ufw allow 6984”?


Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390





On Apr 25, 2020, at 9:28 AM, Rene Veerman 

wrote:


also (FYI) : i have already entered the right port forwarding

commands

into

my ADSL modem..

On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman <

seductivea...@gmail.com>

wrote:


that gets me a 'connection refused' :

('albatross' === localhost === nicer.app)

root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
Trying 127.0.0.1...
Trying 82.161.37.94...
telnet: Unable to connect to remote host: Connection refused
root@albatross:/opt/couchdb/letsencrypt#

On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher <

st...@meredrica.org>

wrote:


Did you try to telnet to the port while couchdb is down? If there

is

no

open port, telnet won't connect.


On April 25, 2020 03:50:56 Rene Veerman 

wrote:




unfortunately that didn't fix things either. i'm still stuck at

the

eaddrinuse error..



[info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0>



Apache CouchDB has started on https://0.0.0.0:6984/
[info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0>



Application couch started on node 'couchdb@127.0.0.1'
[info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0>



Application ets_lru started on node 'couchdb@127.0.0.1'
[notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0>

Re: can't get couchdb to work on https

[Bill Stephenson]

FWIW, I tried the instructions I provided earlier this week and didn’t get them 
to work again. I don’t know if it’s a change made by Let’s Encrypt or I forget 
exactly what I did. 

I’ll go through the process setting up a Digital Ocean vps again as soon as I 
get some time because getting those certs configured has always been a bit of a 
pain and it’d be a good thing to nail that process down.

If anyone has a list of instruction on setting up haproxy they can share I’d be 
glad to have them and give that a shot too.


Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390




> On Apr 30, 2020, at 3:56 PM, Joan Touzet  wrote:
> 
> On 2020-04-30 16:22, Rene Veerman wrote:
>> i'm really only looking for a quick and easy way to getting https to work
>> again..
> 
> Bill Stephenson gave you a step-by-step that seemed reasonable to me.
> 
>> do the creators of couchdb read this mailinglist?
> 
> Yes.
> 
> Most of us terminate SSL ahead of CouchDB at a reverse proxy (such as 
> haproxy). Some of us have even contemplated dropping native SSL support in 
> CouchDB entirely, because configuring it is a bit of a pain, as you've found. 
> But it can be done, and it does work.
> 
> For SSL in pure CouchDB, when I must, I use something like EasyRSA:
> 
>  https://github.com/OpenVPN/easy-rsa
> 
> to generate the certs, then munge them together and start it. It works OK. 
> But I do this about once every 2 years max.
> 
> -Joan "Erlang's SSL support isn't great" Touzet
> 
> 
>> On Sun, Apr 26, 2020 at 3:04 PM Joel Jucá  wrote:
>>> Rene,
>>> 
>>> Your problem seems to be infrastructure-related, rather than CouchDB
>>> related. I would recommend you to read about Infrastructure as Code. This
>>> is a practice that allows a developer to declare its infrastructure (in
>>> your specific case, server configuration) and have some sort of
>>> reproducibility from it. Then, you could also understand every single
>>> change made to your server infrastructure - and even share it as a Gist,
>>> for instance, and have some sort of feedback/pull request directly on it.
>>> 
>>> I would recommend you Ansible (
>>> https://www.ansible.com/resources/get-started).
>>> It's a great solution that allows you to declare your server configuration
>>> as YAML files and use it within Ansible CLI to reproduce the declared
>>> configuration on a targeted server (eg: your Ubuntu-powered CouchDB
>>> server).
>>> 
>>> I've struggled a lot with server configuration back in 2010-2012 when I was
>>> a full-stack PHP/Drupal developer, and after discovering Ansible I could
>>> never imagine myself handling performing a complex task (server
>>> configuration) manually!
>>> 
>>> I hope it helps you in some way.
>>> 
>>> On Sat, Apr 25, 2020 at 6:28 PM Rene Veerman 
>>> wrote:
>>> 
 yes, i did..
 
 On Sat, Apr 25, 2020 at 9:16 PM Bill Stephenson
>>>  
 wrote:
 
> Did you do a "sudo ufw allow 6984”?
> 
> 
> Kindest Regards,
> 
> Bill Stephenson
> Tech Support
> www.cherrypc.com 
> 1-417-546-8390
> 
> 
> 
> 
>> On Apr 25, 2020, at 9:28 AM, Rene Veerman 
> wrote:
>> 
>> also (FYI) : i have already entered the right port forwarding
>>> commands
> into
>> my ADSL modem..
>> 
>> On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman <
>>> seductivea...@gmail.com>
>> wrote:
>> 
>>> that gets me a 'connection refused' :
>>> 
>>> ('albatross' === localhost === nicer.app)
>>> 
>>> root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
>>> root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
>>> Trying 127.0.0.1...
>>> telnet: Unable to connect to remote host: Connection refused
>>> root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
>>> Trying 127.0.0.1...
>>> Trying 82.161.37.94...
>>> telnet: Unable to connect to remote host: Connection refused
>>> root@albatross:/opt/couchdb/letsencrypt#
>>> 
>>> On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher <
> st...@meredrica.org>
>>> wrote:
>>> 
 Did you try to telnet to the port while couchdb is down? If there
>>> is
 no
 open port, telnet won't connect.
 
 
 On April 25, 2020 03:50:56 Rene Veerman 
> wrote:
 
>> 
>> unfortunately that didn't fix things either. i'm still stuck at
>>> the
>> eaddrinuse error..
>> 
> 
> [info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0>
> 
> Apache CouchDB has started on https://0.0.0.0:6984/
> [info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0>
> 
> Application couch started on node 'couchdb@127.0.0.1'
> [info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0>
> 
> Application ets_lru started on node 

Re: can't get couchdb to work on https

[Joan Touzet]

On 2020-04-30 16:22, Rene Veerman wrote:

i'm really only looking for a quick and easy way to getting https to work
again..


Bill Stephenson gave you a step-by-step that seemed reasonable to me.


do the creators of couchdb read this mailinglist?


Yes.

Most of us terminate SSL ahead of CouchDB at a reverse proxy (such as 
haproxy). Some of us have even contemplated dropping native SSL support 
in CouchDB entirely, because configuring it is a bit of a pain, as 
you've found. But it can be done, and it does work.


For SSL in pure CouchDB, when I must, I use something like EasyRSA:

  https://github.com/OpenVPN/easy-rsa

to generate the certs, then munge them together and start it. It works 
OK. But I do this about once every 2 years max.


-Joan "Erlang's SSL support isn't great" Touzet



On Sun, Apr 26, 2020 at 3:04 PM Joel Jucá  wrote:


Rene,

Your problem seems to be infrastructure-related, rather than CouchDB
related. I would recommend you to read about Infrastructure as Code. This
is a practice that allows a developer to declare its infrastructure (in
your specific case, server configuration) and have some sort of
reproducibility from it. Then, you could also understand every single
change made to your server infrastructure - and even share it as a Gist,
for instance, and have some sort of feedback/pull request directly on it.

I would recommend you Ansible (
https://www.ansible.com/resources/get-started).
It's a great solution that allows you to declare your server configuration
as YAML files and use it within Ansible CLI to reproduce the declared
configuration on a targeted server (eg: your Ubuntu-powered CouchDB
server).

I've struggled a lot with server configuration back in 2010-2012 when I was
a full-stack PHP/Drupal developer, and after discovering Ansible I could
never imagine myself handling performing a complex task (server
configuration) manually!

I hope it helps you in some way.

On Sat, Apr 25, 2020 at 6:28 PM Rene Veerman 
wrote:


yes, i did..

On Sat, Apr 25, 2020 at 9:16 PM Bill Stephenson




wrote:


Did you do a "sudo ufw allow 6984”?


Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390





On Apr 25, 2020, at 9:28 AM, Rene Veerman 

wrote:


also (FYI) : i have already entered the right port forwarding

commands

into

my ADSL modem..

On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman <

seductivea...@gmail.com>

wrote:


that gets me a 'connection refused' :

('albatross' === localhost === nicer.app)

root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
Trying 127.0.0.1...
Trying 82.161.37.94...
telnet: Unable to connect to remote host: Connection refused
root@albatross:/opt/couchdb/letsencrypt#

On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher <

st...@meredrica.org>

wrote:


Did you try to telnet to the port while couchdb is down? If there

is

no

open port, telnet won't connect.


On April 25, 2020 03:50:56 Rene Veerman 

wrote:




unfortunately that didn't fix things either. i'm still stuck at

the

eaddrinuse error..



[info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0>



Apache CouchDB has started on https://0.0.0.0:6984/
[info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0>



Application couch started on node 'couchdb@127.0.0.1'
[info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0>



Application ets_lru started on node 'couchdb@127.0.0.1'
[notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0>



rexi_server : started servers
[notice] 2020-04-25T01:49:15.738914Z couchdb@127.0.0.1 <0.288.0>



rexi_buffer : started servers
[info] 2020-04-25T01:49:15.739062Z couchdb@127.0.0.1 <0.11.0>



Application rexi started on node 'couchdb@127.0.0.1'
[notice] 2020-04-25T01:49:15.786354Z couchdb@127.0.0.1 <0.318.0>



mem3_reshard_dbdoc start init()
[notice] 2020-04-25T01:49:15.790014Z couchdb@127.0.0.1 <0.320.0>



mem3_reshard start init()
[notice] 2020-04-25T01:49:15.790112Z couchdb@127.0.0.1 <0.321.0>



mem3_reshard db monitor <0.321.0> starting
[notice] 2020-04-25T01:49:15.792025Z couchdb@127.0.0.1 <0.320.0>



mem3_reshard starting reloading jobs
[notice] 2020-04-25T01:49:15.792087Z couchdb@127.0.0.1 <0.320.0>



mem3_reshard finished reloading jobs
[info] 2020-04-25T01:49:15.792900Z couchdb@127.0.0.1 <0.11.0>



Application mem3 started on node 'couchdb@127.0.0.1'
[info] 2020-04-25T01:49:15.793024Z couchdb@127.0.0.1 <0.11.0>



Application fabric started on node 'couchdb@127.0.0.1'
[error] 2020-04-25T01:49:15.796505Z couchdb@127.0.0.1 <0.330.0>



CRASH REPORT Process  (<0.330.0>) with 0 neighbors exited with

reason:

eaddrinuse at 

Re: can't get couchdb to work on https

[Rene Veerman]

i'm really only looking for a quick and easy way to getting https to work
again..
do the creators of couchdb read this mailinglist?

On Sun, Apr 26, 2020 at 3:04 PM Joel Jucá  wrote:

> Rene,
>
> Your problem seems to be infrastructure-related, rather than CouchDB
> related. I would recommend you to read about Infrastructure as Code. This
> is a practice that allows a developer to declare its infrastructure (in
> your specific case, server configuration) and have some sort of
> reproducibility from it. Then, you could also understand every single
> change made to your server infrastructure - and even share it as a Gist,
> for instance, and have some sort of feedback/pull request directly on it.
>
> I would recommend you Ansible (
> https://www.ansible.com/resources/get-started).
> It's a great solution that allows you to declare your server configuration
> as YAML files and use it within Ansible CLI to reproduce the declared
> configuration on a targeted server (eg: your Ubuntu-powered CouchDB
> server).
>
> I've struggled a lot with server configuration back in 2010-2012 when I was
> a full-stack PHP/Drupal developer, and after discovering Ansible I could
> never imagine myself handling performing a complex task (server
> configuration) manually!
>
> I hope it helps you in some way.
>
> On Sat, Apr 25, 2020 at 6:28 PM Rene Veerman 
> wrote:
>
> > yes, i did..
> >
> > On Sat, Apr 25, 2020 at 9:16 PM Bill Stephenson
>  > >
> > wrote:
> >
> > > Did you do a "sudo ufw allow 6984”?
> > >
> > >
> > > Kindest Regards,
> > >
> > > Bill Stephenson
> > > Tech Support
> > > www.cherrypc.com 
> > > 1-417-546-8390
> > >
> > >
> > >
> > >
> > > > On Apr 25, 2020, at 9:28 AM, Rene Veerman 
> > > wrote:
> > > >
> > > > also (FYI) : i have already entered the right port forwarding
> commands
> > > into
> > > > my ADSL modem..
> > > >
> > > > On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman <
> seductivea...@gmail.com>
> > > > wrote:
> > > >
> > > >> that gets me a 'connection refused' :
> > > >>
> > > >> ('albatross' === localhost === nicer.app)
> > > >>
> > > >> root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
> > > >> root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
> > > >> Trying 127.0.0.1...
> > > >> telnet: Unable to connect to remote host: Connection refused
> > > >> root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
> > > >> Trying 127.0.0.1...
> > > >> Trying 82.161.37.94...
> > > >> telnet: Unable to connect to remote host: Connection refused
> > > >> root@albatross:/opt/couchdb/letsencrypt#
> > > >>
> > > >> On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher <
> > > st...@meredrica.org>
> > > >> wrote:
> > > >>
> > > >>> Did you try to telnet to the port while couchdb is down? If there
> is
> > no
> > > >>> open port, telnet won't connect.
> > > >>>
> > > >>>
> > > >>> On April 25, 2020 03:50:56 Rene Veerman 
> > > wrote:
> > > >>>
> > > >
> > > > unfortunately that didn't fix things either. i'm still stuck at
> the
> > > > eaddrinuse error..
> > > >
> > > 
> > >  [info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0>
> > > 
> > >  Apache CouchDB has started on https://0.0.0.0:6984/
> > >  [info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0>
> > > 
> > >  Application couch started on node 'couchdb@127.0.0.1'
> > >  [info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0>
> > > 
> > >  Application ets_lru started on node 'couchdb@127.0.0.1'
> > >  [notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0>
> > > >>> 
> > >  rexi_server : started servers
> > >  [notice] 2020-04-25T01:49:15.738914Z couchdb@127.0.0.1 <0.288.0>
> > > >>> 
> > >  rexi_buffer : started servers
> > >  [info] 2020-04-25T01:49:15.739062Z couchdb@127.0.0.1 <0.11.0>
> > > 
> > >  Application rexi started on node 'couchdb@127.0.0.1'
> > >  [notice] 2020-04-25T01:49:15.786354Z couchdb@127.0.0.1 <0.318.0>
> > > >>> 
> > >  mem3_reshard_dbdoc start init()
> > >  [notice] 2020-04-25T01:49:15.790014Z couchdb@127.0.0.1 <0.320.0>
> > > >>> 
> > >  mem3_reshard start init()
> > >  [notice] 2020-04-25T01:49:15.790112Z couchdb@127.0.0.1 <0.321.0>
> > > >>> 
> > >  mem3_reshard db monitor <0.321.0> starting
> > >  [notice] 2020-04-25T01:49:15.792025Z couchdb@127.0.0.1 <0.320.0>
> > > >>> 
> > >  mem3_reshard starting reloading jobs
> > >  [notice] 2020-04-25T01:49:15.792087Z couchdb@127.0.0.1 <0.320.0>
> > > >>> 
> > >  mem3_reshard finished reloading jobs
> > >  [info] 2020-04-25T01:49:15.792900Z couchdb@127.0.0.1 <0.11.0>
> > > 
> > >  Application mem3 started on node 'couchdb@127.0.0.1'
> > >  [info] 2020-04-25T01:49:15.793024Z couchdb@127.0.0.1 <0.11.0>
> > > 
> > >  Application fabric started on node 'couchdb@127.0.0.1'
> > >  

Re: can't get couchdb to work on https

[Joel Jucá]

Rene,

Your problem seems to be infrastructure-related, rather than CouchDB
related. I would recommend you to read about Infrastructure as Code. This
is a practice that allows a developer to declare its infrastructure (in
your specific case, server configuration) and have some sort of
reproducibility from it. Then, you could also understand every single
change made to your server infrastructure - and even share it as a Gist,
for instance, and have some sort of feedback/pull request directly on it.

I would recommend you Ansible (https://www.ansible.com/resources/get-started).
It's a great solution that allows you to declare your server configuration
as YAML files and use it within Ansible CLI to reproduce the declared
configuration on a targeted server (eg: your Ubuntu-powered CouchDB server).

I've struggled a lot with server configuration back in 2010-2012 when I was
a full-stack PHP/Drupal developer, and after discovering Ansible I could
never imagine myself handling performing a complex task (server
configuration) manually!

I hope it helps you in some way.

On Sat, Apr 25, 2020 at 6:28 PM Rene Veerman 
wrote:

> yes, i did..
>
> On Sat, Apr 25, 2020 at 9:16 PM Bill Stephenson  >
> wrote:
>
> > Did you do a "sudo ufw allow 6984”?
> >
> >
> > Kindest Regards,
> >
> > Bill Stephenson
> > Tech Support
> > www.cherrypc.com 
> > 1-417-546-8390
> >
> >
> >
> >
> > > On Apr 25, 2020, at 9:28 AM, Rene Veerman 
> > wrote:
> > >
> > > also (FYI) : i have already entered the right port forwarding commands
> > into
> > > my ADSL modem..
> > >
> > > On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman 
> > > wrote:
> > >
> > >> that gets me a 'connection refused' :
> > >>
> > >> ('albatross' === localhost === nicer.app)
> > >>
> > >> root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
> > >> root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
> > >> Trying 127.0.0.1...
> > >> telnet: Unable to connect to remote host: Connection refused
> > >> root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
> > >> Trying 127.0.0.1...
> > >> Trying 82.161.37.94...
> > >> telnet: Unable to connect to remote host: Connection refused
> > >> root@albatross:/opt/couchdb/letsencrypt#
> > >>
> > >> On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher <
> > st...@meredrica.org>
> > >> wrote:
> > >>
> > >>> Did you try to telnet to the port while couchdb is down? If there is
> no
> > >>> open port, telnet won't connect.
> > >>>
> > >>>
> > >>> On April 25, 2020 03:50:56 Rene Veerman 
> > wrote:
> > >>>
> > >
> > > unfortunately that didn't fix things either. i'm still stuck at the
> > > eaddrinuse error..
> > >
> > 
> >  [info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0>
> > 
> >  Apache CouchDB has started on https://0.0.0.0:6984/
> >  [info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0>
> > 
> >  Application couch started on node 'couchdb@127.0.0.1'
> >  [info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0>
> > 
> >  Application ets_lru started on node 'couchdb@127.0.0.1'
> >  [notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0>
> > >>> 
> >  rexi_server : started servers
> >  [notice] 2020-04-25T01:49:15.738914Z couchdb@127.0.0.1 <0.288.0>
> > >>> 
> >  rexi_buffer : started servers
> >  [info] 2020-04-25T01:49:15.739062Z couchdb@127.0.0.1 <0.11.0>
> > 
> >  Application rexi started on node 'couchdb@127.0.0.1'
> >  [notice] 2020-04-25T01:49:15.786354Z couchdb@127.0.0.1 <0.318.0>
> > >>> 
> >  mem3_reshard_dbdoc start init()
> >  [notice] 2020-04-25T01:49:15.790014Z couchdb@127.0.0.1 <0.320.0>
> > >>> 
> >  mem3_reshard start init()
> >  [notice] 2020-04-25T01:49:15.790112Z couchdb@127.0.0.1 <0.321.0>
> > >>> 
> >  mem3_reshard db monitor <0.321.0> starting
> >  [notice] 2020-04-25T01:49:15.792025Z couchdb@127.0.0.1 <0.320.0>
> > >>> 
> >  mem3_reshard starting reloading jobs
> >  [notice] 2020-04-25T01:49:15.792087Z couchdb@127.0.0.1 <0.320.0>
> > >>> 
> >  mem3_reshard finished reloading jobs
> >  [info] 2020-04-25T01:49:15.792900Z couchdb@127.0.0.1 <0.11.0>
> > 
> >  Application mem3 started on node 'couchdb@127.0.0.1'
> >  [info] 2020-04-25T01:49:15.793024Z couchdb@127.0.0.1 <0.11.0>
> > 
> >  Application fabric started on node 'couchdb@127.0.0.1'
> >  [error] 2020-04-25T01:49:15.796505Z couchdb@127.0.0.1 <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: [], 

Re: can't get couchdb to work on https

[Rene Veerman]

yes, i did..

On Sat, Apr 25, 2020 at 9:16 PM Bill Stephenson 
wrote:

> Did you do a "sudo ufw allow 6984”?
>
>
> Kindest Regards,
>
> Bill Stephenson
> Tech Support
> www.cherrypc.com 
> 1-417-546-8390
>
>
>
>
> > On Apr 25, 2020, at 9:28 AM, Rene Veerman 
> wrote:
> >
> > also (FYI) : i have already entered the right port forwarding commands
> into
> > my ADSL modem..
> >
> > On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman 
> > wrote:
> >
> >> that gets me a 'connection refused' :
> >>
> >> ('albatross' === localhost === nicer.app)
> >>
> >> root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
> >> root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
> >> Trying 127.0.0.1...
> >> telnet: Unable to connect to remote host: Connection refused
> >> root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
> >> Trying 127.0.0.1...
> >> Trying 82.161.37.94...
> >> telnet: Unable to connect to remote host: Connection refused
> >> root@albatross:/opt/couchdb/letsencrypt#
> >>
> >> On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher <
> st...@meredrica.org>
> >> wrote:
> >>
> >>> Did you try to telnet to the port while couchdb is down? If there is no
> >>> open port, telnet won't connect.
> >>>
> >>>
> >>> On April 25, 2020 03:50:56 Rene Veerman 
> wrote:
> >>>
> >
> > unfortunately that didn't fix things either. i'm still stuck at the
> > eaddrinuse error..
> >
> 
>  [info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0>
> 
>  Apache CouchDB has started on https://0.0.0.0:6984/
>  [info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0>
> 
>  Application couch started on node 'couchdb@127.0.0.1'
>  [info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0>
> 
>  Application ets_lru started on node 'couchdb@127.0.0.1'
>  [notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0>
> >>> 
>  rexi_server : started servers
>  [notice] 2020-04-25T01:49:15.738914Z couchdb@127.0.0.1 <0.288.0>
> >>> 
>  rexi_buffer : started servers
>  [info] 2020-04-25T01:49:15.739062Z couchdb@127.0.0.1 <0.11.0>
> 
>  Application rexi started on node 'couchdb@127.0.0.1'
>  [notice] 2020-04-25T01:49:15.786354Z couchdb@127.0.0.1 <0.318.0>
> >>> 
>  mem3_reshard_dbdoc start init()
>  [notice] 2020-04-25T01:49:15.790014Z couchdb@127.0.0.1 <0.320.0>
> >>> 
>  mem3_reshard start init()
>  [notice] 2020-04-25T01:49:15.790112Z couchdb@127.0.0.1 <0.321.0>
> >>> 
>  mem3_reshard db monitor <0.321.0> starting
>  [notice] 2020-04-25T01:49:15.792025Z couchdb@127.0.0.1 <0.320.0>
> >>> 
>  mem3_reshard starting reloading jobs
>  [notice] 2020-04-25T01:49:15.792087Z couchdb@127.0.0.1 <0.320.0>
> >>> 
>  mem3_reshard finished reloading jobs
>  [info] 2020-04-25T01:49:15.792900Z couchdb@127.0.0.1 <0.11.0>
> 
>  Application mem3 started on node 'couchdb@127.0.0.1'
>  [info] 2020-04-25T01:49:15.793024Z couchdb@127.0.0.1 <0.11.0>
> 
>  Application fabric started on node 'couchdb@127.0.0.1'
>  [error] 2020-04-25T01:49:15.796505Z couchdb@127.0.0.1 <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-25T01:49:15.796670Z couchdb@127.0.0.1 <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-25T01:49:15.796942Z couchdb@127.0.0.1 <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-25T01:49:15.797060Z couchdb@127.0.0.1 <0.11.0>
> 
>  Application chttpd exited with reason:
> 
> >>>
> {{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}
>  [info] 2020-04-25T01:49:17.882186Z couchdb@127.0.0.1 <0.11.0>
> 
>  Application couch_log started on node 

Re: can't get couchdb to work on https

[Bill Stephenson]

Did you do a "sudo ufw allow 6984”?


Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390




> On Apr 25, 2020, at 9:28 AM, Rene Veerman  wrote:
> 
> also (FYI) : i have already entered the right port forwarding commands into
> my ADSL modem..
> 
> On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman 
> wrote:
> 
>> that gets me a 'connection refused' :
>> 
>> ('albatross' === localhost === nicer.app)
>> 
>> root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
>> root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
>> Trying 127.0.0.1...
>> telnet: Unable to connect to remote host: Connection refused
>> root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
>> Trying 127.0.0.1...
>> Trying 82.161.37.94...
>> telnet: Unable to connect to remote host: Connection refused
>> root@albatross:/opt/couchdb/letsencrypt#
>> 
>> On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher 
>> wrote:
>> 
>>> Did you try to telnet to the port while couchdb is down? If there is no
>>> open port, telnet won't connect.
>>> 
>>> 
>>> On April 25, 2020 03:50:56 Rene Veerman  wrote:
>>> 
> 
> unfortunately that didn't fix things either. i'm still stuck at the
> eaddrinuse error..
> 
 
 [info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0> 
 Apache CouchDB has started on https://0.0.0.0:6984/
 [info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0> 
 Application couch started on node 'couchdb@127.0.0.1'
 [info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0> 
 Application ets_lru started on node 'couchdb@127.0.0.1'
 [notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0>
>>> 
 rexi_server : started servers
 [notice] 2020-04-25T01:49:15.738914Z couchdb@127.0.0.1 <0.288.0>
>>> 
 rexi_buffer : started servers
 [info] 2020-04-25T01:49:15.739062Z couchdb@127.0.0.1 <0.11.0> 
 Application rexi started on node 'couchdb@127.0.0.1'
 [notice] 2020-04-25T01:49:15.786354Z couchdb@127.0.0.1 <0.318.0>
>>> 
 mem3_reshard_dbdoc start init()
 [notice] 2020-04-25T01:49:15.790014Z couchdb@127.0.0.1 <0.320.0>
>>> 
 mem3_reshard start init()
 [notice] 2020-04-25T01:49:15.790112Z couchdb@127.0.0.1 <0.321.0>
>>> 
 mem3_reshard db monitor <0.321.0> starting
 [notice] 2020-04-25T01:49:15.792025Z couchdb@127.0.0.1 <0.320.0>
>>> 
 mem3_reshard starting reloading jobs
 [notice] 2020-04-25T01:49:15.792087Z couchdb@127.0.0.1 <0.320.0>
>>> 
 mem3_reshard finished reloading jobs
 [info] 2020-04-25T01:49:15.792900Z couchdb@127.0.0.1 <0.11.0> 
 Application mem3 started on node 'couchdb@127.0.0.1'
 [info] 2020-04-25T01:49:15.793024Z couchdb@127.0.0.1 <0.11.0> 
 Application fabric started on node 'couchdb@127.0.0.1'
 [error] 2020-04-25T01:49:15.796505Z couchdb@127.0.0.1 <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-25T01:49:15.796670Z couchdb@127.0.0.1 <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-25T01:49:15.796942Z couchdb@127.0.0.1 <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-25T01:49:15.797060Z couchdb@127.0.0.1 <0.11.0> 
 Application chttpd exited with reason:
 
>>> {{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}
 [info] 2020-04-25T01:49:17.882186Z couchdb@127.0.0.1 <0.11.0> 
 Application couch_log started on node 'couchdb@127.0.0.1'
>>> 
>>> 
>>> 
>>> 

Re: can't get couchdb to work on https

[Rene Veerman]

also (FYI) : i have already entered the right port forwarding commands into
my ADSL modem..

On Sat, Apr 25, 2020 at 4:21 PM Rene Veerman 
wrote:

> that gets me a 'connection refused' :
>
> ('albatross' === localhost === nicer.app)
>
> root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
> root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
> Trying 127.0.0.1...
> telnet: Unable to connect to remote host: Connection refused
> root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
> Trying 127.0.0.1...
> Trying 82.161.37.94...
> telnet: Unable to connect to remote host: Connection refused
> root@albatross:/opt/couchdb/letsencrypt#
>
> On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher 
> wrote:
>
>> Did you try to telnet to the port while couchdb is down? If there is no
>> open port, telnet won't connect.
>>
>>
>> On April 25, 2020 03:50:56 Rene Veerman  wrote:
>>
>> >>
>> >> unfortunately that didn't fix things either. i'm still stuck at the
>> >> eaddrinuse error..
>> >>
>> >
>> > [info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0> 
>> > Apache CouchDB has started on https://0.0.0.0:6984/
>> > [info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0> 
>> > Application couch started on node 'couchdb@127.0.0.1'
>> > [info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0> 
>> > Application ets_lru started on node 'couchdb@127.0.0.1'
>> > [notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0>
>> 
>> > rexi_server : started servers
>> > [notice] 2020-04-25T01:49:15.738914Z couchdb@127.0.0.1 <0.288.0>
>> 
>> > rexi_buffer : started servers
>> > [info] 2020-04-25T01:49:15.739062Z couchdb@127.0.0.1 <0.11.0> 
>> > Application rexi started on node 'couchdb@127.0.0.1'
>> > [notice] 2020-04-25T01:49:15.786354Z couchdb@127.0.0.1 <0.318.0>
>> 
>> > mem3_reshard_dbdoc start init()
>> > [notice] 2020-04-25T01:49:15.790014Z couchdb@127.0.0.1 <0.320.0>
>> 
>> > mem3_reshard start init()
>> > [notice] 2020-04-25T01:49:15.790112Z couchdb@127.0.0.1 <0.321.0>
>> 
>> > mem3_reshard db monitor <0.321.0> starting
>> > [notice] 2020-04-25T01:49:15.792025Z couchdb@127.0.0.1 <0.320.0>
>> 
>> > mem3_reshard starting reloading jobs
>> > [notice] 2020-04-25T01:49:15.792087Z couchdb@127.0.0.1 <0.320.0>
>> 
>> > mem3_reshard finished reloading jobs
>> > [info] 2020-04-25T01:49:15.792900Z couchdb@127.0.0.1 <0.11.0> 
>> > Application mem3 started on node 'couchdb@127.0.0.1'
>> > [info] 2020-04-25T01:49:15.793024Z couchdb@127.0.0.1 <0.11.0> 
>> > Application fabric started on node 'couchdb@127.0.0.1'
>> > [error] 2020-04-25T01:49:15.796505Z couchdb@127.0.0.1 <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-25T01:49:15.796670Z couchdb@127.0.0.1 <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-25T01:49:15.796942Z couchdb@127.0.0.1 <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-25T01:49:15.797060Z couchdb@127.0.0.1 <0.11.0> 
>> > Application chttpd exited with reason:
>> >
>> {{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}
>> > [info] 2020-04-25T01:49:17.882186Z couchdb@127.0.0.1 <0.11.0> 
>> > Application couch_log started on node 'couchdb@127.0.0.1'
>>
>>
>>
>>

Re: can't get couchdb to work on https

[Rene Veerman]

that gets me a 'connection refused' :

('albatross' === localhost === nicer.app)

root@albatross:/opt/couchdb/letsencrypt# service couchdb stop
root@albatross:/opt/couchdb/letsencrypt# telnet localhost 6984
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
root@albatross:/opt/couchdb/letsencrypt# telnet nicer.app 6984
Trying 127.0.0.1...
Trying 82.161.37.94...
telnet: Unable to connect to remote host: Connection refused
root@albatross:/opt/couchdb/letsencrypt#

On Sat, Apr 25, 2020 at 1:41 PM Florian Westreicher 
wrote:

> Did you try to telnet to the port while couchdb is down? If there is no
> open port, telnet won't connect.
>
>
> On April 25, 2020 03:50:56 Rene Veerman  wrote:
>
> >>
> >> unfortunately that didn't fix things either. i'm still stuck at the
> >> eaddrinuse error..
> >>
> >
> > [info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0> 
> > Apache CouchDB has started on https://0.0.0.0:6984/
> > [info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0> 
> > Application couch started on node 'couchdb@127.0.0.1'
> > [info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0> 
> > Application ets_lru started on node 'couchdb@127.0.0.1'
> > [notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0>
> 
> > rexi_server : started servers
> > [notice] 2020-04-25T01:49:15.738914Z couchdb@127.0.0.1 <0.288.0>
> 
> > rexi_buffer : started servers
> > [info] 2020-04-25T01:49:15.739062Z couchdb@127.0.0.1 <0.11.0> 
> > Application rexi started on node 'couchdb@127.0.0.1'
> > [notice] 2020-04-25T01:49:15.786354Z couchdb@127.0.0.1 <0.318.0>
> 
> > mem3_reshard_dbdoc start init()
> > [notice] 2020-04-25T01:49:15.790014Z couchdb@127.0.0.1 <0.320.0>
> 
> > mem3_reshard start init()
> > [notice] 2020-04-25T01:49:15.790112Z couchdb@127.0.0.1 <0.321.0>
> 
> > mem3_reshard db monitor <0.321.0> starting
> > [notice] 2020-04-25T01:49:15.792025Z couchdb@127.0.0.1 <0.320.0>
> 
> > mem3_reshard starting reloading jobs
> > [notice] 2020-04-25T01:49:15.792087Z couchdb@127.0.0.1 <0.320.0>
> 
> > mem3_reshard finished reloading jobs
> > [info] 2020-04-25T01:49:15.792900Z couchdb@127.0.0.1 <0.11.0> 
> > Application mem3 started on node 'couchdb@127.0.0.1'
> > [info] 2020-04-25T01:49:15.793024Z couchdb@127.0.0.1 <0.11.0> 
> > Application fabric started on node 'couchdb@127.0.0.1'
> > [error] 2020-04-25T01:49:15.796505Z couchdb@127.0.0.1 <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-25T01:49:15.796670Z couchdb@127.0.0.1 <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-25T01:49:15.796942Z couchdb@127.0.0.1 <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-25T01:49:15.797060Z couchdb@127.0.0.1 <0.11.0> 
> > Application chttpd exited with reason:
> >
> {{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}
> > [info] 2020-04-25T01:49:17.882186Z couchdb@127.0.0.1 <0.11.0> 
> > Application couch_log started on node 'couchdb@127.0.0.1'
>
>
>
>

Re: can't get couchdb to work on https

[Florian Westreicher]

Did you try to telnet to the port while couchdb is down? If there is no 
open port, telnet won't connect.



On April 25, 2020 03:50:56 Rene Veerman  wrote:



unfortunately that didn't fix things either. i'm still stuck at the
eaddrinuse error..



[info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0> 
Apache CouchDB has started on https://0.0.0.0:6984/
[info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0> 
Application couch started on node 'couchdb@127.0.0.1'
[info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0> 
Application ets_lru started on node 'couchdb@127.0.0.1'
[notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0> 
rexi_server : started servers
[notice] 2020-04-25T01:49:15.738914Z couchdb@127.0.0.1 <0.288.0> 
rexi_buffer : started servers
[info] 2020-04-25T01:49:15.739062Z couchdb@127.0.0.1 <0.11.0> 
Application rexi started on node 'couchdb@127.0.0.1'
[notice] 2020-04-25T01:49:15.786354Z couchdb@127.0.0.1 <0.318.0> 
mem3_reshard_dbdoc start init()
[notice] 2020-04-25T01:49:15.790014Z couchdb@127.0.0.1 <0.320.0> 
mem3_reshard start init()
[notice] 2020-04-25T01:49:15.790112Z couchdb@127.0.0.1 <0.321.0> 
mem3_reshard db monitor <0.321.0> starting
[notice] 2020-04-25T01:49:15.792025Z couchdb@127.0.0.1 <0.320.0> 
mem3_reshard starting reloading jobs
[notice] 2020-04-25T01:49:15.792087Z couchdb@127.0.0.1 <0.320.0> 
mem3_reshard finished reloading jobs
[info] 2020-04-25T01:49:15.792900Z couchdb@127.0.0.1 <0.11.0> 
Application mem3 started on node 'couchdb@127.0.0.1'
[info] 2020-04-25T01:49:15.793024Z couchdb@127.0.0.1 <0.11.0> 
Application fabric started on node 'couchdb@127.0.0.1'
[error] 2020-04-25T01:49:15.796505Z couchdb@127.0.0.1 <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-25T01:49:15.796670Z couchdb@127.0.0.1 <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-25T01:49:15.796942Z couchdb@127.0.0.1 <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-25T01:49:15.797060Z couchdb@127.0.0.1 <0.11.0> 
Application chttpd exited with reason:
{{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}
[info] 2020-04-25T01:49:17.882186Z couchdb@127.0.0.1 <0.11.0> 
Application couch_log started on node 'couchdb@127.0.0.1'

Re: can't get couchdb to work on https

[Rene Veerman]

>
> unfortunately that didn't fix things either. i'm still stuck at the
> eaddrinuse error..
>

[info] 2020-04-25T01:49:15.730815Z couchdb@127.0.0.1 <0.232.0> 
Apache CouchDB has started on https://0.0.0.0:6984/
[info] 2020-04-25T01:49:15.731032Z couchdb@127.0.0.1 <0.11.0> 
Application couch started on node 'couchdb@127.0.0.1'
[info] 2020-04-25T01:49:15.731178Z couchdb@127.0.0.1 <0.11.0> 
Application ets_lru started on node 'couchdb@127.0.0.1'
[notice] 2020-04-25T01:49:15.737605Z couchdb@127.0.0.1 <0.284.0> 
rexi_server : started servers
[notice] 2020-04-25T01:49:15.738914Z couchdb@127.0.0.1 <0.288.0> 
rexi_buffer : started servers
[info] 2020-04-25T01:49:15.739062Z couchdb@127.0.0.1 <0.11.0> 
Application rexi started on node 'couchdb@127.0.0.1'
[notice] 2020-04-25T01:49:15.786354Z couchdb@127.0.0.1 <0.318.0> 
mem3_reshard_dbdoc start init()
[notice] 2020-04-25T01:49:15.790014Z couchdb@127.0.0.1 <0.320.0> 
mem3_reshard start init()
[notice] 2020-04-25T01:49:15.790112Z couchdb@127.0.0.1 <0.321.0> 
mem3_reshard db monitor <0.321.0> starting
[notice] 2020-04-25T01:49:15.792025Z couchdb@127.0.0.1 <0.320.0> 
mem3_reshard starting reloading jobs
[notice] 2020-04-25T01:49:15.792087Z couchdb@127.0.0.1 <0.320.0> 
mem3_reshard finished reloading jobs
[info] 2020-04-25T01:49:15.792900Z couchdb@127.0.0.1 <0.11.0> 
Application mem3 started on node 'couchdb@127.0.0.1'
[info] 2020-04-25T01:49:15.793024Z couchdb@127.0.0.1 <0.11.0> 
Application fabric started on node 'couchdb@127.0.0.1'
[error] 2020-04-25T01:49:15.796505Z couchdb@127.0.0.1 <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-25T01:49:15.796670Z couchdb@127.0.0.1 <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-25T01:49:15.796942Z couchdb@127.0.0.1 <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-25T01:49:15.797060Z couchdb@127.0.0.1 <0.11.0> 
Application chttpd exited with reason:
{{shutdown,{failed_to_start_child,chttpd,eaddrinuse}},{chttpd_app,start,[normal,[]]}}
[info] 2020-04-25T01:49:17.882186Z couchdb@127.0.0.1 <0.11.0> 
Application couch_log started on node 'couchdb@127.0.0.1'

Re: can't get couchdb to work on https

[Bill Stephenson]

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 couchdb@127.0.0.1 <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.29Z couchdb@127.0.0.1 <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 rootroot 1903 Apr 24 19:40 cert5.pem
-rw-r--r-- 1 couchdb root 1647 Jan 25 19:18 chain4.pem
-rw-r--r-- 1 rootroot 1647 Apr 24 19:40 chain5.pem
-rw--- 1 couchdb root 3550 Jan 25 19:18 fullchain4.pem
-rw-r--r-- 1 rootroot 3550 Apr 24 19:40 fullchain5.pem
-rw--- 1 couchdb root 1704 Jan 25 19:18 privkey4.pem
-rw--- 1 rootroot 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 


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 


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

Re: can't get couchdb to work on https

[Rene Veerman]

it isn't...

root@albatross:/opt/couchdb/letsencrypt# sudo lsof -i -P -n | grep LISTEN
systemd-r   856 systemd-resolve   13u  IPv4   19944  0t0  TCP
127.0.0.53:53 (LISTEN)
vsftpd  965root3u  IPv6   23904  0t0  TCP *:21
(LISTEN)
apache21018root3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache21018root5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
apache21976www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache21976www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
apache21978www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache21978www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
apache21979www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache21979www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
apache21980www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache21980www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
apache21981www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache21981www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
cupsd  1985root6u  IPv6 3967527  0t0  TCP [::1]:631
(LISTEN)
cupsd  1985root7u  IPv4 3967528  0t0  TCP
127.0.0.1:631 (LISTEN)
apache22058www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache22058www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
apache22770www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache22770www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
apache2   20337www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache2   20337www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
apache2   20448www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache2   20448www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
apache2   20578www-data3u  IPv4   24874  0t0  TCP *:80
(LISTEN)
apache2   20578www-data5u  IPv6   24878  0t0  TCP *:443
(LISTEN)
root@albatross:/opt/couchdb/letsencrypt#

On Fri, Apr 24, 2020 at 12:21 PM Ronny Berndt  wrote:

> Please check if your used port is bound to another service running on that
> machine...
>
> Vom iPhone gesendet
>
> > Am 24.04.2020 um 11:52 schrieb Rene Veerman :
> >
> > 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 couchdb@127.0.0.1 <0.11.0> 
> > Application mem3 started on node 'couchdb@127.0.0.1'
> > [info] 2020-04-24T09:50:45.815139Z couchdb@127.0.0.1 <0.11.0> 
> > Application fabric started on node 'couchdb@127.0.0.1'
> > [error] 2020-04-24T09:50:45.818472Z couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <0.11.0> 
> > Application couch_log started on node 'couchdb@127.0.0.1'
> >
> >> On Fri, Apr 24, 2020 at 4:47 AM Bill Stephenson
> 
> >> 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

Re: can't get couchdb to work on https

[Ronny Berndt]

Please check if your used port is bound to another service running on that 
machine...

Vom iPhone gesendet

> Am 24.04.2020 um 11:52 schrieb Rene Veerman :
> 
> 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 couchdb@127.0.0.1 <0.11.0> 
> Application mem3 started on node 'couchdb@127.0.0.1'
> [info] 2020-04-24T09:50:45.815139Z couchdb@127.0.0.1 <0.11.0> 
> Application fabric started on node 'couchdb@127.0.0.1'
> [error] 2020-04-24T09:50:45.818472Z couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <0.11.0> 
> Application couch_log started on node 'couchdb@127.0.0.1'
> 
>> On Fri, Apr 24, 2020 at 4:47 AM Bill Stephenson 
>> 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 
>> 1-417-546-8390
>> 
>> 
>> 
>> 
>>> On Apr 23, 2020, at 9:36 PM, Rene Veerman 
>> 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..
>> 
>> 

Re: can't get couchdb to work on https

[Rene Veerman]

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 couchdb@127.0.0.1 <0.11.0> 
Application mem3 started on node 'couchdb@127.0.0.1'
[info] 2020-04-24T09:50:45.815139Z couchdb@127.0.0.1 <0.11.0> 
Application fabric started on node 'couchdb@127.0.0.1'
[error] 2020-04-24T09:50:45.818472Z couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <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 couchdb@127.0.0.1 <0.11.0> 
Application couch_log started on node 'couchdb@127.0.0.1'

On Fri, Apr 24, 2020 at 4:47 AM Bill Stephenson 
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 
> 1-417-546-8390
>
>
>
>
> > On Apr 23, 2020, at 9:36 PM, Rene Veerman 
> 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..
>
>

Re: can't get couchdb to work on https

[Sebastien]

Personally, I'm relying on the edge of my Kubernetes cluster (for now):
https://medium.com/@dSebastien/deploying-tls-certificates-for-local-development-and-production-using-kubernetes-cert-manager-9ab46abdd569

It's not ideal as the traffic remains in cleartext within the cluster, but
can be a nice (and rather straightforward) first step.

kr,
Sébastien

On Fri, Apr 24, 2020 at 6:18 AM Jonathan Aquilina 
wrote:

> With Lets encrypt if you have apache running they have a cert bot which
> automates the generation of the Certs and then adjusts the vhosts for
> apache and sets up the redirects.
>
> -Original Message-
> From: Bill Stephenson 
> Sent: Friday, 24 April 2020 06:16
> To: user@couchdb.apache.org
> Subject: Re: can't get couchdb to work on https
>
> I’ve look at Linode, and I know a lot devs prefer their services. I moved
> to DO around 5 years ago I suppose now. Every now and then I consider
> switching, but that’d be a process.
>
> I don’t think I installed a web server on that droplet.
>
> One of the things I wanted to do was see if I could connect my apps to it
> that are running on a different VPS there, which I did with no problem. I’m
> pretty sure I made the snapshot right after I tested that and then played
> with the VPS for another week or so before shutting it off. Just before I
> shut it off I did an update & upgrade on my production CouchDB server and
> it upgraded CouchDB to 3.0. I really didn’t expect that but it went smooth
> as a baby’s butt so that’s what I’m using now,
>
> --,
>
> Bill
>
>
>
>
> > On Apr 23, 2020, at 10:59 PM, Bill Stephenson 
> wrote:
> >
> > Well, it shouldn’t muck anything up to try the Let’s Encrypt route, and
> it doesn’t cost anything.
> >
> > I have a Digital Ocean “snapshot” of an Ubuntu 18.04 server with CouchDB
> 3.0 & SSL installed on it I set up last month. I didn’t install anything
> else on it. I just wanted to go through the process and keep a snapshot so
> I could spin up a new server if I need one. Digital Ocean makes it easy to
> transfer ownership of a  “droplet” (VPS) so that’s another option you can
> consider. I think I installed on a $10 a month “droplet” (might have been
> $20) and those are easy to upgrade if you need something bigger.
> >
> >
> > Kindest Regards,
> >
> > Bill
> >
> >
> >
> >
> >> On Apr 23, 2020, at 10:06 PM, Travis Klein  wrote:
> >>
> >> I do my https to my proxy server then connect to couch using http
> locally. You could try that if you can’t get it to work
> >>
> >
>
>

RE: can't get couchdb to work on https

[Jonathan Aquilina]

With Lets encrypt if you have apache running they have a cert bot which 
automates the generation of the Certs and then adjusts the vhosts for apache 
and sets up the redirects.

-Original Message-
From: Bill Stephenson  
Sent: Friday, 24 April 2020 06:16
To: user@couchdb.apache.org
Subject: Re: can't get couchdb to work on https

I’ve look at Linode, and I know a lot devs prefer their services. I moved to DO 
around 5 years ago I suppose now. Every now and then I consider switching, but 
that’d be a process.

I don’t think I installed a web server on that droplet. 

One of the things I wanted to do was see if I could connect my apps to it that 
are running on a different VPS there, which I did with no problem. I’m pretty 
sure I made the snapshot right after I tested that and then played with the VPS 
for another week or so before shutting it off. Just before I shut it off I did 
an update & upgrade on my production CouchDB server and it upgraded CouchDB to 
3.0. I really didn’t expect that but it went smooth as a baby’s butt so that’s 
what I’m using now, 

--,

Bill 




> On Apr 23, 2020, at 10:59 PM, Bill Stephenson  
> wrote:
> 
> Well, it shouldn’t muck anything up to try the Let’s Encrypt route, and it 
> doesn’t cost anything. 
> 
> I have a Digital Ocean “snapshot” of an Ubuntu 18.04 server with CouchDB 3.0 
> & SSL installed on it I set up last month. I didn’t install anything else on 
> it. I just wanted to go through the process and keep a snapshot so I could 
> spin up a new server if I need one. Digital Ocean makes it easy to transfer 
> ownership of a  “droplet” (VPS) so that’s another option you can consider. I 
> think I installed on a $10 a month “droplet” (might have been $20) and those 
> are easy to upgrade if you need something bigger.
> 
> 
> Kindest Regards,
> 
> Bill 
> 
> 
> 
> 
>> On Apr 23, 2020, at 10:06 PM, Travis Klein  wrote:
>> 
>> I do my https to my proxy server then connect to couch using http locally. 
>> You could try that if you can’t get it to work
>> 
> 

Re: can't get couchdb to work on https

[Bill Stephenson]

I’ve look at Linode, and I know a lot devs prefer their services. I moved to DO 
around 5 years ago I suppose now. Every now and then I consider switching, but 
that’d be a process.

I don’t think I installed a web server on that droplet. 

One of the things I wanted to do was see if I could connect my apps to it that 
are running on a different VPS there, which I did with no problem. I’m pretty 
sure I made the snapshot right after I tested that and then played with the VPS 
for another week or so before shutting it off. Just before I shut it off I did 
an update & upgrade on my production CouchDB server and it upgraded CouchDB to 
3.0. I really didn’t expect that but it went smooth as a baby’s butt so that’s 
what I’m using now, 

--,

Bill 




> On Apr 23, 2020, at 10:59 PM, Bill Stephenson  
> wrote:
> 
> Well, it shouldn’t muck anything up to try the Let’s Encrypt route, and it 
> doesn’t cost anything. 
> 
> I have a Digital Ocean “snapshot” of an Ubuntu 18.04 server with CouchDB 3.0 
> & SSL installed on it I set up last month. I didn’t install anything else on 
> it. I just wanted to go through the process and keep a snapshot so I could 
> spin up a new server if I need one. Digital Ocean makes it easy to transfer 
> ownership of a  “droplet” (VPS) so that’s another option you can consider. I 
> think I installed on a $10 a month “droplet” (might have been $20) and those 
> are easy to upgrade if you need something bigger.
> 
> 
> Kindest Regards,
> 
> Bill 
> 
> 
> 
> 
>> On Apr 23, 2020, at 10:06 PM, Travis Klein  wrote:
>> 
>> I do my https to my proxy server then connect to couch using http locally. 
>> You could try that if you can’t get it to work
>> 
> 

RE: can't get couchdb to work on https

[Jonathan Aquilina]

Hi Bill,

I use one of their competitors linode and its very easy to upgrade and down 
grade as needed.

What is the web server that it comes with? 

-Original Message-
From: Bill Stephenson  
Sent: Friday, 24 April 2020 06:00
To: user@couchdb.apache.org
Subject: Re: can't get couchdb to work on https

Well, it shouldn’t muck anything up to try the Let’s Encrypt route, and it 
doesn’t cost anything. 

I have a Digital Ocean “snapshot” of an Ubuntu 18.04 server with CouchDB 3.0 & 
SSL installed on it I set up last month. I didn’t install anything else on it. 
I just wanted to go through the process and keep a snapshot so I could spin up 
a new server if I need one. Digital Ocean makes it easy to transfer ownership 
of a  “droplet” (VPS) so that’s another option you can consider. I think I 
installed on a $10 a month “droplet” (might have been $20) and those are easy 
to upgrade if you need something bigger.


Kindest Regards,

Bill 




> On Apr 23, 2020, at 10:06 PM, Travis Klein  wrote:
> 
> I do my https to my proxy server then connect to couch using http locally. 
> You could try that if you can’t get it to work
> 

Re: can't get couchdb to work on https

[Bill Stephenson]

Well, it shouldn’t muck anything up to try the Let’s Encrypt route, and it 
doesn’t cost anything. 

I have a Digital Ocean “snapshot” of an Ubuntu 18.04 server with CouchDB 3.0 & 
SSL installed on it I set up last month. I didn’t install anything else on it. 
I just wanted to go through the process and keep a snapshot so I could spin up 
a new server if I need one. Digital Ocean makes it easy to transfer ownership 
of a  “droplet” (VPS) so that’s another option you can consider. I think I 
installed on a $10 a month “droplet” (might have been $20) and those are easy 
to upgrade if you need something bigger.


Kindest Regards,

Bill 




> On Apr 23, 2020, at 10:06 PM, Travis Klein  wrote:
> 
> I do my https to my proxy server then connect to couch using http locally. 
> You could try that if you can’t get it to work
> 

Re: can't get couchdb to work on https

[Travis Klein]

I do my https to my proxy server then connect to couch using http locally. You 
could try that if you can’t get it to work

Sent from my iPhone

> On Apr 23, 2020, at 8:54 PM, Rene Veerman  wrote:
> 
> under couchdb 2.x, this all used to work like a charm
> not so in couchdb 3.x :(
> 
>> On Fri, Apr 24, 2020 at 4:53 AM Rene Veerman 
>> wrote:
>> 
>> i'm using the certificate files given to me by my certificate provider,
>> and i'm getting the following error in /var/log/couchdb/couchdb.log now :
>> 
>> [notice] 2020-04-24T02:21:18.335906Z couchdb@127.0.0.1 <0.288.0> 
>> rexi_buffer : cluster stable
>> [notice] 2020-04-24T02:45:24.371745Z couchdb@127.0.0.1 <0.14640.0>
>> 39b0035f50 82.161.37.94:5984 162.243.130.108 undefined GET / 200 ok 22
>> [error] 2020-04-24T02:50:46.365102Z couchdb@127.0.0.1 <0.17763.0>
>>  application: mochiweb, "Accept failed error",
>> "{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
>>[]}}}"
>> [error] 2020-04-24T02:50:46.365233Z couchdb@127.0.0.1 <0.17763.0>
>>  CRASH REPORT Process  (<0.17763.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: 1905
>> [error] 2020-04-24T02:50:46.442400Z couchdb@127.0.0.1 <0.17764.0>
>>  application: mochiweb, "Accept failed error",
>> "{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
>>[]}}}"
>> [error] 2020-04-24T02:50:46.442530Z couchdb@127.0.0.1 <0.17764.0>
>>  CRASH REPORT Process  (<0.17764.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: 987, stack_size: 27, reductions: 1918
>> [error] 2020-04-24T02:50:51.466683Z couchdb@127.0.0.1 <0.17765.0>
>>  application: mochiweb, "Accept failed error",
>> "{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
>>[]}}}"
>> [error] 2020-04-24T02:50:51.466870Z couchdb@127.0.0.1 <0.17765.0>
>>  CRASH REPORT Process  (<0.17765.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: 987, stack_size: 27, reductions: 1918
>> [error] 2020-04-24T02:51:21.500671Z couchdb@127.0.0.1 <0.18065.0>
>>  application: mochiweb, "Accept failed error",
>> "{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
>>[]}}}"
>> [error] 2020-04-24T02:51:21.500805Z couchdb@127.0.0.1 <0.18065.0>
>>  CRASH REPORT Process  (<0.18065.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: 987, stack_size: 27, reductions: 1920
>> 
>> 
>> On Fri, Apr 24, 2020 at 4:47 AM Bill Stephenson 
>> 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 

Re: can't get couchdb to work on https

[Rene Veerman]

under couchdb 2.x, this all used to work like a charm
not so in couchdb 3.x :(

On Fri, Apr 24, 2020 at 4:53 AM Rene Veerman 
wrote:

> i'm using the certificate files given to me by my certificate provider,
> and i'm getting the following error in /var/log/couchdb/couchdb.log now :
>
> [notice] 2020-04-24T02:21:18.335906Z couchdb@127.0.0.1 <0.288.0> 
> rexi_buffer : cluster stable
> [notice] 2020-04-24T02:45:24.371745Z couchdb@127.0.0.1 <0.14640.0>
> 39b0035f50 82.161.37.94:5984 162.243.130.108 undefined GET / 200 ok 22
> [error] 2020-04-24T02:50:46.365102Z couchdb@127.0.0.1 <0.17763.0>
>  application: mochiweb, "Accept failed error",
> "{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
> []}}}"
> [error] 2020-04-24T02:50:46.365233Z couchdb@127.0.0.1 <0.17763.0>
>  CRASH REPORT Process  (<0.17763.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: 1905
> [error] 2020-04-24T02:50:46.442400Z couchdb@127.0.0.1 <0.17764.0>
>  application: mochiweb, "Accept failed error",
> "{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
> []}}}"
> [error] 2020-04-24T02:50:46.442530Z couchdb@127.0.0.1 <0.17764.0>
>  CRASH REPORT Process  (<0.17764.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: 987, stack_size: 27, reductions: 1918
> [error] 2020-04-24T02:50:51.466683Z couchdb@127.0.0.1 <0.17765.0>
>  application: mochiweb, "Accept failed error",
> "{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
> []}}}"
> [error] 2020-04-24T02:50:51.466870Z couchdb@127.0.0.1 <0.17765.0>
>  CRASH REPORT Process  (<0.17765.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: 987, stack_size: 27, reductions: 1918
> [error] 2020-04-24T02:51:21.500671Z couchdb@127.0.0.1 <0.18065.0>
>  application: mochiweb, "Accept failed error",
> "{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
> []}}}"
> [error] 2020-04-24T02:51:21.500805Z couchdb@127.0.0.1 <0.18065.0>
>  CRASH REPORT Process  (<0.18065.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: 987, stack_size: 27, reductions: 1920
>
>
> On Fri, Apr 24, 2020 at 4:47 AM Bill Stephenson 
> 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 

Re: can't get couchdb to work on https

[Rene Veerman]

i'm using the certificate files given to me by my certificate provider, and
i'm getting the following error in /var/log/couchdb/couchdb.log now :

[notice] 2020-04-24T02:21:18.335906Z couchdb@127.0.0.1 <0.288.0> 
rexi_buffer : cluster stable
[notice] 2020-04-24T02:45:24.371745Z couchdb@127.0.0.1 <0.14640.0>
39b0035f50 82.161.37.94:5984 162.243.130.108 undefined GET / 200 ok 22
[error] 2020-04-24T02:50:46.365102Z couchdb@127.0.0.1 <0.17763.0> 
application: mochiweb, "Accept failed error",
"{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
[]}}}"
[error] 2020-04-24T02:50:46.365233Z couchdb@127.0.0.1 <0.17763.0> 
CRASH REPORT Process  (<0.17763.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: 1905
[error] 2020-04-24T02:50:46.442400Z couchdb@127.0.0.1 <0.17764.0> 
application: mochiweb, "Accept failed error",
"{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
[]}}}"
[error] 2020-04-24T02:50:46.442530Z couchdb@127.0.0.1 <0.17764.0> 
CRASH REPORT Process  (<0.17764.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: 987, stack_size: 27, reductions: 1918
[error] 2020-04-24T02:50:51.466683Z couchdb@127.0.0.1 <0.17765.0> 
application: mochiweb, "Accept failed error",
"{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
[]}}}"
[error] 2020-04-24T02:50:51.466870Z couchdb@127.0.0.1 <0.17765.0> 
CRASH REPORT Process  (<0.17765.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: 987, stack_size: 27, reductions: 1918
[error] 2020-04-24T02:51:21.500671Z couchdb@127.0.0.1 <0.18065.0> 
application: mochiweb, "Accept failed error",
"{error,{options,{keyfile,\"/opt/couchdb/etc/https/nicer.app--generated-private-key.txt\",\n
[]}}}"
[error] 2020-04-24T02:51:21.500805Z couchdb@127.0.0.1 <0.18065.0> 
CRASH REPORT Process  (<0.18065.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: 987, stack_size: 27, reductions: 1920


On Fri, Apr 24, 2020 at 4:47 AM Bill Stephenson 
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 = 

Re: can't get couchdb to work on https

[Bill Stephenson]

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 


test it at: https://YOUR.com:6984/_utils/

—

Kindest Regards,

Bill Stephenson
Tech Support
www.cherrypc.com 
1-417-546-8390




> On Apr 23, 2020, at 9:36 PM, Rene Veerman  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..