stuck on "Initial replication in progress..." when connecting to the database

[icsy7867]

Perhaps user error, and I have never used couch DB before. I am deploying via kubernetes, and I am not using the --link flag as this is deprecated.

Using curl, I can access the couchdb via http or HTTPS using the username/password I setup. I also verified that this works via CURL from the StorDown container itself, so I know things are connected/working.

After setting up the couchdb connection information, though, a modal pops up that says:
Initial replication in progress...

And it never goes away. So I am not sure what's going on here. Is there more to setup the DB itself other than just creating it through the web gui? Also, I noticed the default DB name in the StoreDown gui defaults to "StoreDown", but couchdb doesnt allow uppercase letters.

Also, while troubleshooting i noticed that kubectl logs couchdb (or docker logs couchdb) returns nothing, but if you set the logging the stderr, it logs for docker as appropriately.

[log]
writer = stderr

While note in the docs for storedown, you should mount your configuration settings as well:

/opt/couchdb/etc/local.d

This not only lets you preserve them, but you can also add these custom settings using vi/vim/nano/whatever easily as well.

--- Update
Still having issues, but it seems that it might be more about the system setup and not necessarily the DB itself. I get this error no matter what I try to do:

I think it might be because I am adding HTTPS via a traefik ingress and not the default HTTPS functionality, the JS is probably trying to do HTTP calls instead of HTTPS. Is there a way to force HTTPS calls without configuring the container for HTTPS?

[icsy7867]

Playing around with it more. It is a bit odd, but if I check the "Remember username and password" and leave the username and password blank, it seems to go through OK. But if I try to add my couch username/password that I setup with the environmental variables, it seems to get denied.

--
Another update. I thought I would try and incognito tab, and the blank auth no longer works, which makes me think the other "blank" auth is actually using cookie auth, and a previous cookie is just working. Still trying to figure out these settings.

--
Initial problem was an issue where the couchdb db was being accessed through the container network. This caused issues as I was going through http,.and storedown was https. This ticked off chrome. Also since it's mostly JavaScript, Im not sure those internal connections would be working anyways.

[icsy7867]

I believe everything is working as intended. A combination of kubernetes/docker networks, mixed HTTP/HTTPS errors and cookie authentication which seemed to make it look like a blank username/password on the DB was successfully authenticated.