Cannot sync with CouchDB about tempo HOT 4 CLOSED

I finally got CouchDB installation working properly by setting up HAproxy as a reverse proxy as recommended on CouchDB docs. As a bonus, my other services on that machine are all now available via my own domain name, and secured by TLS using Cloudflare DNS and free HTTPS certificate. Syncing like a champ now.

from tempo.

After more investigating, I found that the cookie sent by CouchDB is not being set because of the SameSite=Lax setting, which is the default. I went into CouchDB settings and added the following key [couchdb_httpd_auth] same_site = None This changed the cookie's SameSite attribute, but Vivaldi is still not setting the cookie because Secure is not set on the cookie. This seems to be an issue with running a CouchDB on localhost with http instead of https. Looking into possible solutions.

from tempo.

Yes, I think running CouchDB on a local, non https URL can cause issues with synchronisation, especially if you are using Tempo from a public, https URL. Similar issue: https://stackoverflow.com/questions/68609006/cookie-authentication-couchdb-on-localhost

If I remember correctly, this did work when both CouchDB and Tempo were served locally. Would you mind trying this, e.g running Tempo in development (instructions at https://github.com/agateblue/tempo#project-setup) and see if it works that way?

from tempo.

Thank you for letting us now :)

from tempo.