Heya Marcus, Newly created databases are admin-only by default in 3.0 (which is different from 2.x):
https://blog.couchdb.org/2020/02/26/the-road-to-couchdb-3-0-security/ <https://blog.couchdb.org/2020/02/26/the-road-to-couchdb-3-0-security/> So you’ll have to make an authenticated request against /dbname/_all_docs or change that database’s _security object, if you want to make the database publicly readable. SSL should not play into this, as you’re getting an error message transmitted via SSL. I just note that you showed a `http://` <http://`/> and not a `https://` <https://`/> request. Best Jan — > On 10. Mar 2020, at 11:39, Marcus Bieber <[email protected]> wrote: > > Hi everyone, > > I have a dev environment with CouchDB 2.3.1 which is running well. > I have an admin and no ssl. > So calls like http://1xx.1xx.xxx.xx:5984/dbname/_all_docs are no problem. > > So now I wanted to setup the live server. CouchDB 3.0 with ssl and an admin. > Running fine. > Replication worked. > Now I get on the same call: > > { > "error": "unauthorized", > "reason": "You are not authorized to access this db." > } > > Did I miss / forget something. > Is this a problem caused by changes in 3.0 or could this be a problem of the > ssl? > > Can someone help me please. > > Thanks in advance and kind regards > Marcus > -- Professional Support for Apache CouchDB: https://neighbourhood.ie/couchdb-support/
