argh....

i edited couchdb local.ini and changed all 5984 references (found only 1,
in [chttpd]) to the new port,
i added a [https] section just to be sure,
then removed the log, restarted couchdb, and it still is stuck at
ERR_CONNECTION_TIMED_OUT, and still serving from 5984?!.......

but, i see in the local.ini a discrepancy between the entries provided by
that tutorial i followed, and the defaults provided in local.ini (all
commented out at the moment of course)

i'll try some sane simple values to see if that fixes it.
will get back to you all.



root@albatross:/opt/couchdb/etc# vi local.ini
root@albatross:/opt/couchdb/etc# rm /var/log/couchdb/couchdb.log
root@albatross:/opt/couchdb/etc# service couchdb restart
root@albatross:/opt/couchdb/etc# cat /var/log/couchdb/couchdb.log
[info] 2019-08-12T07:08:18.106610Z [email protected] <0.9.0> --------
Application couch_log started on node '[email protected]'
[info] 2019-08-12T07:08:18.109939Z [email protected] <0.9.0> --------
Application folsom started on node '[email protected]'
[info] 2019-08-12T07:08:18.137549Z [email protected] <0.9.0> --------
Application couch_stats started on node '[email protected]'
[info] 2019-08-12T07:08:18.137706Z [email protected] <0.9.0> --------
Application khash started on node '[email protected]'
[info] 2019-08-12T07:08:18.141724Z [email protected] <0.9.0> --------
Application couch_event started on node '[email protected]'
[info] 2019-08-12T07:08:18.141841Z [email protected] <0.9.0> --------
Application hyper started on node '[email protected]'
[info] 2019-08-12T07:08:18.145279Z [email protected] <0.9.0> --------
Application ibrowse started on node '[email protected]'
[info] 2019-08-12T07:08:18.148331Z [email protected] <0.9.0> --------
Application ioq started on node '[email protected]'
[info] 2019-08-12T07:08:18.148448Z [email protected] <0.9.0> --------
Application mochiweb started on node '[email protected]'
[info] 2019-08-12T07:08:18.153703Z [email protected] <0.212.0> --------
Apache CouchDB 2.3.1 is starting.

[info] 2019-08-12T07:08:18.153790Z [email protected] <0.213.0> --------
Starting couch_sup
[notice] 2019-08-12T07:08:18.160498Z [email protected] <0.96.0> --------
config: [features] pluggable-storage-engines set to true for reason nil
[info] 2019-08-12T07:08:18.226737Z [email protected] <0.212.0> --------
Apache CouchDB has started. Time to relax.

[info] 2019-08-12T07:08:18.226844Z [email protected] <0.212.0> --------
Apache CouchDB has started on http://0.0.0.0:5986/
[info] 2019-08-12T07:08:18.226957Z [email protected] <0.9.0> --------
Application couch started on node '[email protected]'
[info] 2019-08-12T07:08:18.227047Z [email protected] <0.9.0> --------
Application ets_lru started on node '[email protected]'
[notice] 2019-08-12T07:08:18.247452Z [email protected] <0.276.0> --------
rexi_server : started servers
[notice] 2019-08-12T07:08:18.250459Z [email protected] <0.280.0> --------
rexi_buffer : started servers
[info] 2019-08-12T07:08:18.250560Z [email protected] <0.9.0> --------
Application rexi started on node '[email protected]'
[info] 2019-08-12T07:08:18.278049Z [email protected] <0.9.0> --------
Application mem3 started on node '[email protected]'
[info] 2019-08-12T07:08:18.278152Z [email protected] <0.9.0> --------
Application fabric started on node '[email protected]'
[info] 2019-08-12T07:08:18.295076Z [email protected] <0.9.0> --------
Application chttpd started on node '[email protected]'
[info] 2019-08-12T07:08:18.304512Z [email protected] <0.9.0> --------
Application couch_index started on node '[email protected]'
[info] 2019-08-12T07:08:18.304536Z [email protected] <0.9.0> --------
Application couch_mrview started on node '[email protected]'
[info] 2019-08-12T07:08:18.304620Z [email protected] <0.9.0> --------
Application couch_plugins started on node '[email protected]'
[notice] 2019-08-12T07:08:18.345689Z [email protected] <0.96.0> --------
config: [features] scheduler set to true for reason nil
[info] 2019-08-12T07:08:18.359523Z [email protected] <0.9.0> --------
Application couch_replicator started on node '[email protected]'
[info] 2019-08-12T07:08:18.364887Z [email protected] <0.9.0> --------
Application couch_peruser started on node '[email protected]'
[info] 2019-08-12T07:08:18.373893Z [email protected] <0.9.0> --------
Application ddoc_cache started on node '[email protected]'
[info] 2019-08-12T07:08:18.382525Z [email protected] <0.9.0> --------
Application global_changes started on node '[email protected]'
[info] 2019-08-12T07:08:18.382551Z [email protected] <0.9.0> --------
Application jiffy started on node '[email protected]'
[info] 2019-08-12T07:08:18.386369Z [email protected] <0.9.0> --------
Application mango started on node '[email protected]'
[info] 2019-08-12T07:08:18.392097Z [email protected] <0.9.0> --------
Application setup started on node '[email protected]'
[info] 2019-08-12T07:08:18.392126Z [email protected] <0.9.0> --------
Application snappy started on node '[email protected]'
root@albatross:/opt/couchdb/etc#
root@albatross:/opt/couchdb/etc# cat local.ini
; CouchDB Configuration Settings

; Custom settings should be made in this file. They will override settings
; in default.ini, but unlike changes made to default.ini, this file won't be
; overwritten on server upgrade.

[couchdb]
;max_document_size = 4294967296 ; bytes
;os_process_timeout = 5000

[couch_peruser]
; If enabled, couch_peruser ensures that a private per-user database
; exists for each document in _users. These databases are writable only
; by the corresponding user. Databases are in the following form:
; userdb-{hex encoded username}
;enable = true
; If set to true and a user is deleted, the respective database gets
; deleted as well.
;delete_dbs = true
; Set a default q value for peruser-created databases that is different from
; cluster / q
;q = 1

[chttpd]
port = 7984
bind_address = 0.0.0.0
; Options for the MochiWeb HTTP server.
;server_options = [{backlog, 128}, {acceptor_pool_size, 16}]
; For more socket options, consult Erlang's module 'inet' man page.
;socket_options = [{sndbuf, 262144}, {nodelay, true}]

[httpd]
; NOTE that this only configures the "backend" node-local port, not the
; "frontend" clustered port. You probably don't want to change anything in
; this section.
; Uncomment next line to trigger basic-auth popup on unauthorized requests.
;WWW-Authenticate = Basic realm="administrator"

; Uncomment next line to set the configuration modification whitelist. Only
; whitelisted values may be changed via the /_config URLs. To allow the
admin
; to change this value over HTTP, remember to include
{httpd,config_whitelist}
; itself. Excluding it from the list would require editing this file to
update
; the whitelist.
;config_whitelist = [{httpd,config_whitelist}, {log,level}, {etc,etc}]
bind_address = 0.0.0.0
enable_cors = true

[https]
bind_address = 0.0.0.0
enable_cors = true

[cors]
origins = *

[query_servers]
;nodejs = /usr/local/bin/couchjs-node /path/to/couchdb/share/server/main.js

[couch_httpd_auth]
; If you set this to true, you should also uncomment the WWW-Authenticate
line
; above. If you don't configure a WWW-Authenticate header, CouchDB will send
; Basic realm="server" in order to prevent you getting logged out.
; require_valid_user = false

; ssl]
;enable = true
;cert_file = /full/path/to/server_cert.pem
;key_file = /full/path/to/server_key.pem
;password = somepassword
; set to true to validate peer certificates
;verify_ssl_certificates = false
; Set to true to fail if the client does not send a certificate. Only used
if verify_ssl_certificates is true.
;fail_if_no_peer_cert = false
; Path to file containing PEM encoded CA certificates (trusted
; certificates used for verifying a peer certificate). May be omitted if
; you do not want to verify the peer.
;cacert_file = /full/path/to/cacertf
; The verification fun (optional) if not specified, the default
; verification fun will be used.
;verify_fun = {Module, VerifyFun}
; maximum peer certificate depth
;ssl_certificate_max_depth = 1
;
; Reject renegotiations that do not live up to RFC 5746.
;secure_renegotiate = true
; The cipher suites that should be supported.
; Can be specified in erlang format "{ecdhe_ecdsa,aes_128_cbc,sha256}"
; or in OpenSSL format "ECDHE-ECDSA-AES128-SHA256".
;ciphers = ["ECDHE-ECDSA-AES128-SHA256", "ECDHE-ECDSA-AES128-SHA"]
; The SSL/TLS versions to support
;tls_versions = [tlsv1, 'tlsv1.1', 'tlsv1.2']
[daemons]
httpsd = {couch_httpd, start_link, [https]}

[ssl]
port = 7984
key_file = /opt/couchdb/etc/https/server.key
cert_file = /opt/couchdb/etc/https/server.crt

; To enable Virtual Hosts in CouchDB, add a vhost = path directive. All
requests to
; the Virual Host will be redirected to the path. In the example below all
requests
; to http://example.com/ are redirected to /database.
; If you run CouchDB on a specific port, include the port number in the
vhost:
; example.com:5984 = /database
[vhosts]
;example.com = /database/

; To create an admin account uncomment the '[admins]' section below and add
a
; line in the format 'username = password'. When you next start CouchDB, it
; will change the password to a hash (so that your passwords don't linger
; around in plain-text files). You can add more admin accounts with more
; 'username = password' lines. Don't forget to restart CouchDB after
; changing this.
[admins]
;admin = mysecretpassword

On Mon, Aug 12, 2019 at 9:05 AM Rene Veerman <[email protected]>
wrote:

> ehm, after actually reviewing the log, perfectly good clue here of course :
>
>  [email protected] <0.212.0> -------- Apache CouchDB has started on
> http://0.0.0.0:5986/
>
> i had thought adding the SSL entries into local.ini would get it to start
> at the new port 7984, but apparently it didn't.
> i'll dig though the /opt/couchdb/etc/local.ini a bit more and see if i can
> get this fixed.
>
>
>
> On Mon, Aug 12, 2019 at 8:59 AM Rene Veerman <[email protected]>
> wrote:
>
>> reboot didn't fix the current hurdle, but specifying port forwarding on
>> my ADSL modem for the new port (i use 7984) did.
>>
>> however, now itś stuck at ERR_CONNECTION_TIMED_OUT.
>>
>> the latest section from /var/log/couchdb/couch.log doesnt seem to provide
>> any clues :(
>>
>> [notice] 2019-08-12T06:04:14.673813Z [email protected] <0.4798.27>
>> 65e2162c62 nicer.app:5984 185.187.30.14 undefined GET /_utils 301 ok 1
>> [notice] 2019-08-12T06:04:14.695236Z [email protected] <0.4798.27>
>> cd4ffc2166 nicer.app:5984 185.187.30.14 undefined GET /_utils/ 200 ok 2
>> [notice] 2019-08-12T06:06:03.085467Z [email protected] <0.6569.27>
>> 257ab05f63 nicer.app:5984 52.37.222.213 undefined GET /_utils 301 ok 1
>> [notice] 2019-08-12T06:06:03.315609Z [email protected] <0.6569.27>
>> 3621c6854c nicer.app:5984 52.37.222.213 undefined GET /_utils/ 200 ok 1
>> [notice] 2019-08-12T06:06:25.366783Z [email protected] <0.6908.27>
>> 2ec33dbcc6 nicer.app:5984 91.134.17.243 undefined GET /_utils 301 ok 1
>> [notice] 2019-08-12T06:07:22.535578Z [email protected] <0.7843.27>
>> 8662824c37 nicer.app:5984 54.184.144.236 undefined GET /_utils 301 ok 0
>> [notice] 2019-08-12T06:07:22.751996Z [email protected] <0.7843.27>
>> ac911eb586 nicer.app:5984 54.184.144.236 undefined GET /_utils/ 200 ok 2
>> [notice] 2019-08-12T06:12:16.640911Z [email protected] <0.12693.27>
>> 9b69eba61a nicer.app:5984 54.71.187.124 undefined GET / 200 ok 0
>> [info] 2019-08-12T06:39:30.789946Z [email protected] <0.9.0> --------
>> Application couch_log started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.792784Z [email protected] <0.9.0> --------
>> Application folsom started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.817069Z [email protected] <0.9.0> --------
>> Application couch_stats started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.817176Z [email protected] <0.9.0> --------
>> Application khash started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.820921Z [email protected] <0.9.0> --------
>> Application couch_event started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.821029Z [email protected] <0.9.0> --------
>> Application hyper started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.824456Z [email protected] <0.9.0> --------
>> Application ibrowse started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.827372Z [email protected] <0.9.0> --------
>> Application ioq started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.827488Z [email protected] <0.9.0> --------
>> Application mochiweb started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.832332Z [email protected] <0.212.0> --------
>> Apache CouchDB 2.3.1 is starting.
>>
>> [info] 2019-08-12T06:39:30.832394Z [email protected] <0.213.0> --------
>> Starting couch_sup
>> [notice] 2019-08-12T06:39:30.837888Z [email protected] <0.96.0> --------
>> config: [features] pluggable-storage-engines set to true for reason nil
>> [info] 2019-08-12T06:39:30.894792Z [email protected] <0.212.0> --------
>> Apache CouchDB has started. Time to relax.
>>
>> [info] 2019-08-12T06:39:30.894867Z [email protected] <0.212.0> --------
>> Apache CouchDB has started on http://0.0.0.0:5986/
>> [info] 2019-08-12T06:39:30.894958Z [email protected] <0.9.0> --------
>> Application couch started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.895124Z [email protected] <0.9.0> --------
>> Application ets_lru started on node '[email protected]'
>> [notice] 2019-08-12T06:39:30.912905Z [email protected] <0.276.0>
>> -------- rexi_server : started servers
>> [notice] 2019-08-12T06:39:30.915501Z [email protected] <0.280.0>
>> -------- rexi_buffer : started servers
>> [info] 2019-08-12T06:39:30.915627Z [email protected] <0.9.0> --------
>> Application rexi started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.936926Z [email protected] <0.9.0> --------
>> Application mem3 started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.937025Z [email protected] <0.9.0> --------
>> Application fabric started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.949042Z [email protected] <0.9.0> --------
>> Application chttpd started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.956206Z [email protected] <0.9.0> --------
>> Application couch_index started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.956264Z [email protected] <0.9.0> --------
>> Application couch_mrview started on node '[email protected]'
>> [info] 2019-08-12T06:39:30.956351Z [email protected] <0.9.0> --------
>> Application couch_plugins started on node '[email protected]'
>> [notice] 2019-08-12T06:39:30.985904Z [email protected] <0.96.0> --------
>> config: [features] scheduler set to true for reason nil
>> [info] 2019-08-12T06:39:30.995484Z [email protected] <0.9.0> --------
>> Application couch_replicator started on node '[email protected]'
>> [info] 2019-08-12T06:39:31.000076Z [email protected] <0.9.0> --------
>> Application couch_peruser started on node '[email protected]'
>> [info] 2019-08-12T06:39:31.006933Z [email protected] <0.9.0> --------
>> Application ddoc_cache started on node '[email protected]'
>> [info] 2019-08-12T06:39:31.014647Z [email protected] <0.9.0> --------
>> Application global_changes started on node '[email protected]'
>> [info] 2019-08-12T06:39:31.014666Z [email protected] <0.9.0> --------
>> Application jiffy started on node '[email protected]'
>> [info] 2019-08-12T06:39:31.018184Z [email protected] <0.9.0> --------
>> Application mango started on node '[email protected]'
>> [info] 2019-08-12T06:39:31.021359Z [email protected] <0.9.0> --------
>> Application setup started on node '[email protected]'
>> [info] 2019-08-12T06:39:31.021378Z [email protected] <0.9.0> --------
>> Application snappy started on node '[email protected]'
>> [notice] 2019-08-12T06:39:35.965491Z [email protected] <0.361.0>
>> -------- couch_replicator_clustering : cluster stable
>> [notice] 2019-08-12T06:39:35.969095Z [email protected] <0.410.0>
>> -------- Started replicator db changes listener <0.511.0>
>> [notice] 2019-08-12T06:39:45.913542Z [email protected] <0.280.0>
>> -------- rexi_buffer : cluster stable
>> [notice] 2019-08-12T06:39:45.913703Z [email protected] <0.276.0>
>> -------- rexi_server : cluster stable
>> [notice] 2019-08-12T06:47:14.794554Z [email protected] <0.10180.0>
>> 3fcceb3ed8 nicer.app 211.249.40.7 undefined GET / 200 ok 15
>> [notice] 2019-08-12T06:47:44.520588Z [email protected] <0.10682.0>
>> 4431b5d248 nicer.app 211.249.40.7 undefined GET /_utils 301 ok 0
>> [info] 2019-08-12T06:48:18.458569Z [email protected] <0.9.0> --------
>> Application couch_log started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.461608Z [email protected] <0.9.0> --------
>> Application folsom started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.487711Z [email protected] <0.9.0> --------
>> Application couch_stats started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.487819Z [email protected] <0.9.0> --------
>> Application khash started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.491437Z [email protected] <0.9.0> --------
>> Application couch_event started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.491537Z [email protected] <0.9.0> --------
>> Application hyper started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.494813Z [email protected] <0.9.0> --------
>> Application ibrowse started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.497644Z [email protected] <0.9.0> --------
>> Application ioq started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.497750Z [email protected] <0.9.0> --------
>> Application mochiweb started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.502341Z [email protected] <0.212.0> --------
>> Apache CouchDB 2.3.1 is starting.
>>
>> [info] 2019-08-12T06:48:18.502407Z [email protected] <0.213.0> --------
>> Starting couch_sup
>> [notice] 2019-08-12T06:48:18.524658Z [email protected] <0.96.0> --------
>> config: [features] pluggable-storage-engines set to true for reason nil
>> [info] 2019-08-12T06:48:18.624645Z [email protected] <0.212.0> --------
>> Apache CouchDB has started. Time to relax.
>>
>> [info] 2019-08-12T06:48:18.624729Z [email protected] <0.212.0> --------
>> Apache CouchDB has started on http://0.0.0.0:5986/
>> [info] 2019-08-12T06:48:18.624851Z [email protected] <0.9.0> --------
>> Application couch started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.624953Z [email protected] <0.9.0> --------
>> Application ets_lru started on node '[email protected]'
>> [notice] 2019-08-12T06:48:18.642495Z [email protected] <0.275.0>
>> -------- rexi_server : started servers
>> [notice] 2019-08-12T06:48:18.646679Z [email protected] <0.279.0>
>> -------- rexi_buffer : started servers
>> [info] 2019-08-12T06:48:18.646872Z [email protected] <0.9.0> --------
>> Application rexi started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.685318Z [email protected] <0.9.0> --------
>> Application mem3 started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.685455Z [email protected] <0.9.0> --------
>> Application fabric started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.696917Z [email protected] <0.9.0> --------
>> Application chttpd started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.703354Z [email protected] <0.9.0> --------
>> Application couch_index started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.703435Z [email protected] <0.9.0> --------
>> Application couch_mrview started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.703521Z [email protected] <0.9.0> --------
>> Application couch_plugins started on node '[email protected]'
>> [notice] 2019-08-12T06:48:18.759977Z [email protected] <0.96.0> --------
>> config: [features] scheduler set to true for reason nil
>> [info] 2019-08-12T06:48:18.770425Z [email protected] <0.9.0> --------
>> Application couch_replicator started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.774887Z [email protected] <0.9.0> --------
>> Application couch_peruser started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.781655Z [email protected] <0.9.0> --------
>> Application ddoc_cache started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.789317Z [email protected] <0.9.0> --------
>> Application global_changes started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.789335Z [email protected] <0.9.0> --------
>> Application jiffy started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.792422Z [email protected] <0.9.0> --------
>> Application mango started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.795476Z [email protected] <0.9.0> --------
>> Application setup started on node '[email protected]'
>> [info] 2019-08-12T06:48:18.795496Z [email protected] <0.9.0> --------
>> Application snappy started on node '[email protected]'
>> [notice] 2019-08-12T06:48:23.712238Z [email protected] <0.361.0>
>> -------- couch_replicator_clustering : cluster stable
>> [notice] 2019-08-12T06:48:23.719034Z [email protected] <0.410.0>
>> -------- Started replicator db changes listener <0.511.0>
>> [notice] 2019-08-12T06:48:33.643031Z [email protected] <0.279.0>
>> -------- rexi_buffer : cluster stable
>> [notice] 2019-08-12T06:48:33.643085Z [email protected] <0.275.0>
>> -------- rexi_server : cluster stable
>> root@albatross:~#
>>
>> On Mon, Aug 12, 2019 at 8:46 AM Rene Veerman <[email protected]>
>> wrote:
>>
>>> ok i followed the instructions at
>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=48203146
>>> and after restarting the couchdb service, with a self-signed key,
>>> iḿ now stuck at ERR_ADDRESS_UNREACHABLE
>>> which is really puzzling to me.
>>>
>>> i'll try the good old reboot just to be sure, and then, stomach
>>> permitting, i'll use the CA Signed Cert path it also offers.
>>> god how i hate https ;)
>>>
>>> output of following those instructions is :
>>> root@albatross:/opt/couchdb/etc/https# ls
>>> nicer.app--generated-csr.txt  nicer.app--generated-private-key.txt
>>> root@albatross:/opt/couchdb/etc/https# openssl
>>> OpenSSL> ^C
>>> root@albatross:/opt/couchdb/etc/https# openssl genrsa -out server.key
>>> 2048
>>> Generating RSA private key, 2048 bit long modulus (2 primes)
>>> ....+++++
>>> ..+++++
>>> e is 65537 (0x010001)
>>> root@albatross:/opt/couchdb/etc/https# ls
>>> nicer.app--generated-csr.txt  nicer.app--generated-private-key.txt
>>>  server.key
>>> root@albatross:/opt/couchdb/etc/https# openssl -req -new -key
>>> server.key -out server.csr
>>> Invalid command '-req'; type "help" for a list.
>>> root@albatross:/opt/couchdb/etc/https# openssl req -new -key server.key
>>> -out server.csr
>>> Can't load /root/.rnd into RNG
>>> 139976184963520:error:2406F079:random number
>>> generator:RAND_load_file:Cannot open
>>> file:../crypto/rand/randfile.c:88:Filename=/root/.rnd
>>> You are about to be asked to enter information that will be incorporated
>>> into your certificate request.
>>> What you are about to enter is what is called a Distinguished Name or a
>>> DN.
>>> There are quite a few fields but you can leave some blank
>>> For some fields there will be a default value,
>>> If you enter '.', the field will be left blank.
>>> -----
>>> Country Name (2 letter code) [AU]:NL
>>> State or Province Name (full name) [Some-State]:Noord-Holland
>>> Locality Name (eg, city) []:Amsterdam
>>> Organization Name (eg, company) [Internet Widgits Pty Ltd]:NicerApp
>>> Organizational Unit Name (eg, section) []:.
>>> Common Name (e.g. server FQDN or YOUR name) []:nicer.app
>>> Email Address []:[email protected]
>>>
>>> Please enter the following 'extra' attributes
>>> to be sent with your certificate request
>>> A challenge password []:{NOTINCLUDED}-
>>> An optional company name []:.
>>> root@albatross:/opt/couchdb/etc/https# openssl x509 -req -sha256 -days
>>> 1095 -in server.csr -signkey server.key -out server.crt
>>> Signature ok
>>> subject=C = NL, ST = Noord-Holland, L = Amsterdam, O = NicerApp, CN =
>>> nicer.app, emailAddress = [email protected]
>>> Getting Private key
>>> root@albatross:/opt/couchdb/etc/https# cd ..
>>> root@albatross:/opt/couchdb/etc# gedit local.ini
>>> ^C
>>> root@albatross:/opt/couchdb/etc# vi local.ini
>>> root@albatross:/opt/couchdb/etc# service couchdb restart
>>>
>>>
>>>
>>> On Mon, Aug 12, 2019 at 8:06 AM Rene Veerman <[email protected]>
>>> wrote:
>>>
>>>> i added the DNS records over a week ago, and got regular traffic to
>>>> apache at the default https port to work.
>>>> it's just couchdb that i can't use when using that domain name.
>>>>
>>>> and no, this server is hosted at my home behind a ADSL line, godaddy as
>>>> registrar and afraid.org as DNS provider.
>>>>
>>>> On Mon, Aug 12, 2019 at 8:04 AM Jonathan Aquilina <
>>>> [email protected]> wrote:
>>>>
>>>>> Https is enforced on your server is this server in google cloud?
>>>>>
>>>>> Regards,
>>>>> Jonathan Aquilina
>>>>> Owner managing director
>>>>>
>>>>> Phone (356) 20330099
>>>>> Mobile (356) 78857942
>>>>>
>>>>> Email [email protected]
>>>>> ________________________________
>>>>> From: Rene Veerman <[email protected]>
>>>>> Sent: Monday, August 12, 2019 8:02:52 AM
>>>>> To: [email protected] <[email protected]>
>>>>> Subject: Re: running couchdb on a .app domain (https enforced)
>>>>>
>>>>> doesn't a host file just translate names to IP addresses, without
>>>>> specifying anything about ports?
>>>>> i've never read or heard about a hosts file or a DNS setup for that
>>>>> matter,
>>>>> specifying anything about ports.
>>>>>
>>>>> i think it has something to do with the fact that on .app, https is
>>>>> enforced by the TLD registrar (which is google).
>>>>> but i have no clue on how to fix it.
>>>>>
>>>>> could it be that couchdb itself needs a HTTPS certificate specified?
>>>>> i did some googling, and found
>>>>>
>>>>> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=48203146
>>>>> ,
>>>>> which i'll try to implement in a little while, at the moment my
>>>>> stomach is
>>>>> killing me if i sit at the desk, for some reason..
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Aug 12, 2019 at 7:56 AM Per Torstensson <
>>>>> [email protected]>
>>>>> wrote:
>>>>>
>>>>> > If you are running the server from the same network as your client,
>>>>> could
>>>>> > it be that you need to add manual entries in your host file?
>>>>> >
>>>>> > -Per
>>>>> >
>>>>> > > 12 aug. 2019 kl. 07:49 skrev Rene Veerman <[email protected]
>>>>> >:
>>>>> > >
>>>>> > > root@albatross:/home/rene/data1/htdocs/nicer.app# tail
>>>>> > > /var/log/couchdb/couchdb.log
>>>>> > > [notice] 2019-08-12T03:46:47.333273Z [email protected]
>>>>> <0.28155.22>
>>>>> > > 90ff2d612e nicer.app 211.249.40.12 undefined GET /_utilsit 401 ok 0
>>>>> > > [notice] 2019-08-12T04:06:30.916355Z [email protected]
>>>>> <0.15768.23>
>>>>> > > 1b0a651329 nicer.app 211.249.40.12 undefined GET /_utils 301 ok 0
>>>>> > > [notice] 2019-08-12T04:07:28.715744Z [email protected]
>>>>> <0.16715.23>
>>>>> > > a02251ebab nicer.app:5984 23.226.211.152 undefined GET /_utils 301
>>>>> ok 0
>>>>> > > [notice] 2019-08-12T04:07:28.988497Z [email protected]
>>>>> <0.16715.23>
>>>>> > > 9762923dd4 nicer.app:5984 23.226.211.152 undefined GET /_utils/
>>>>> 200 ok 1
>>>>> > > [notice] 2019-08-12T04:07:30.186957Z [email protected]
>>>>> <0.16726.23>
>>>>> > > 35abe0105d nicer.app:5984 23.239.180.202 undefined GET
>>>>> > > /_utils/dashboard.assets/img/couchdb-logo.png 200 ok 1
>>>>> > >
>>>>> > > it seems others can connect to my couchdb, but i can't....
>>>>> ?!#!@@$!@ ;)
>>>>> > >
>>>>> > > and even when browsing to http://nicer.app:5984/_utils from the
>>>>> machine
>>>>> > it
>>>>> > > runs on, i get stuck at 'establishing secure connection'.
>>>>> > >
>>>>> > > On Mon, Aug 12, 2019 at 6:07 AM Jonathan Aquilina <
>>>>> > [email protected]>
>>>>> > > wrote:
>>>>> > >
>>>>> > >> Check the server itself the domain has nothing to do with it is
>>>>> there
>>>>> > >> anything useful maybe in the logs?
>>>>> > >>
>>>>> > >>
>>>>> > >>
>>>>> > >> -----Original Message-----
>>>>> > >> From: Rene Veerman <[email protected]>
>>>>> > >> Sent: Monday, 12 August 2019 06:06
>>>>> > >> To: [email protected]
>>>>> > >> Subject: Re: running couchdb on a .app domain (https enforced)
>>>>> > >>
>>>>> > >> if i browse to https://nicer.app:5984/_utils, it's stuck at
>>>>> > 'Establishing
>>>>> > >> secure connection', then fails with 'server took too long to
>>>>> respond'.
>>>>> > :(
>>>>> > >>
>>>>> > >> On Mon, Aug 12, 2019 at 6:03 AM Jonathan Aquilina <
>>>>> > [email protected]
>>>>> > >>>
>>>>> > >> wrote:
>>>>> > >>
>>>>> > >>> That is correct usually DNS just points a domain or subdomain to
>>>>> the
>>>>> > >>> server then you can use any port you want for example
>>>>> > >>>
>>>>> > >>> https://DOMAIN:PORT/_utils for example if you want to access
>>>>> fauxton
>>>>> > >>>
>>>>> > >>> Regards,
>>>>> > >>> Jonathan
>>>>> > >>>
>>>>> > >>> -----Original Message-----
>>>>> > >>> From: Rene Veerman <[email protected]>
>>>>> > >>> Sent: Monday, 12 August 2019 05:46
>>>>> > >>> To: [email protected]
>>>>> > >>> Subject: Re: running couchdb on a .app domain (https enforced)
>>>>> > >>>
>>>>> > >>> as far as i know, DNS only connects a domain name to an ip
>>>>> address,
>>>>> > >>> not to any specific port.
>>>>> > >>> there's certainly no option at afraid.org to set it.
>>>>> > >>>
>>>>> > >>> On Sun, Aug 11, 2019 at 9:20 PM Peter J Krawetzky
>>>>> > >>> <[email protected]>
>>>>> > >>> wrote:
>>>>> > >>>
>>>>> > >>>> So it seems you are using freedns.  Couldn't you just create a
>>>>> new
>>>>> > >>>> entry like couchdb.nicer.app and point it to the couchdb server
>>>>> and
>>>>> > >>>> port?PeterSent from my Verizon, Samsung Galaxy smartphone
>>>>> > >>>> -------- Original message --------From: Rene Veerman <
>>>>> > >>>> [email protected]> Date: 8/11/19  11:58  (GMT-05:00) To:
>>>>> > >>>> [email protected] Subject: Re: running couchdb on a .app
>>>>> > >>>> domain (https enforced) i don't know much about DNS, other than
>>>>> how
>>>>> > >>>> to set it from my domainregistrar to a DNS provider (i use
>>>>> > >>>> afraid.org), and have the followingrecords there :11
>>>>> > >>>> subdomainsnicer.app [ add ]<
>>>>> > >>>>
>>>>> https://freedns.afraid.org/subdomain/edit.php?edit_domain_id=1290281
>>>>> > >>>>> irc.nicer.app<
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643169>
>>>>> > >>>> (*G*) *NotYet Configured.*nicer.app <
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643167>
>>>>> > >>>> (*G*) A 82.161.37.94nicer.app <
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643168>
>>>>> > >>>> (*G*) MX 10:seductiveapps.comftp.nicer.app<
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643166>
>>>>> > >>>> (*G*) A82.161.37.94imap.nicer.app<
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643171>
>>>>> > >>>> (*G*) A82.161.37.94lib.nicer.app<
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643174>
>>>>> > >>>> (*G*) A82.161.37.94mail.nicer.app<
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643165>
>>>>> > >>>> (*G*) A82.161.37.94media.nicer.app<
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643173>
>>>>> > >>>> (*G*) A82.161.37.94smtp.nicer.app<
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643170>
>>>>> > >>>> (*G*) A82.161.37.94tnp.nicer.app<
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643172>
>>>>> > >>>> (*G*) A82.161.37.94www.nicer.app<
>>>>> > >>>> https://freedns.afraid.org/subdomain/edit.php?data_id=18643164>
>>>>> > >>>> (*G*) A82.161.37.94traffic to regular apache at the https port
>>>>> does
>>>>> > >>>> work by the way.i'd love to hear more about what to adjust in
>>>>> what
>>>>> > >>>> file.coz now i'm still stuck :(On Sun, Aug 11, 2019 at 5:52 PM
>>>>> Peter
>>>>> > >>>> J Krawetzky < [email protected]>wrote:> You either need a
>>>>> DNS
>>>>> > >>>> definition on your network or an entry in the local> host's
>>>>> file on
>>>>> > >>>> the couch server PeterSent from my Verizon, Samsung Galaxy>
>>>>> > >>>> smartphone> -------- Original message
>>>>> > >>>> --------From: Rene Veerman <> [email protected]> Date:
>>>>> 8/11/19
>>>>> > >>>> 11:35  (GMT-05:00) To:> [email protected] Subject:
>>>>> running
>>>>> > >>>> couchdb on a .app domain (https> enforced) i can connect to
>>>>> > >>>> localhost:5984/_utils, but not to> nicer.app:5984/_utilsit's the
>>>>> > >>>> same machine.how do i get couchdb to work on> a .app domain and
>>>>> be
>>>>> > >>>> addressable by that.app domain name?thanks in advance> for any
>>>>> help
>>>>> > >>>> you
>>>>> > >>> can provide.
>>>>> > >>>
>>>>> > >>
>>>>> >
>>>>>
>>>>

Reply via email to