Hi @durga.tukilogic ,
Could you please add more information on the error? It would be helpful if you can provide steps you did so that we can look into recreating the error. Also, are you using https or http? If you could provide full log of the error in console, it would be helpful too.
Same issue was showing on mine system. I had checked in firebox and it worked there. Issue still exist in chrome browser.
Experienced the same issue when accessing the login on Chrome, but Firefox browser should work just fine.
This is expected for self hosted SSL certificates - which is what the CHT generates by default.
To avoid this, you can use cht-docker-helper and access your instance through local-ip.
Hello @diana ,
I have encountered the above issue.
I have used cht-docker-helper in configuring my local instance.
Hi @Job_Isabai
Can you please expand the error you are seeing? Also, are you sure you’re accessing the instance via HTTPS and having a valid certificate?
This is a browser limitation, I’m afraid. To register service workers, you need to have a valid SSL certificate.
Hello @diana,
I am getting this error on my production server.
Client devices are able to login but replication process fails.
From the logs, am getting this:
[notice] 2024-11-07T10:41:30.829288Z couchdb@127.0.0.1 <0.29491.7> cfdf7b256c msfecare.msf.org 172.19.0.6 form2-cs1 GET /api/v1/replication/get-ids 404 ok 2
Please help
Hello @Job_Isabai
This is interesting.
/api/v1/replication/get-ids is an API endpoint, and it should never actually reach CouchDb. From this log entry, it seems that the request does reach CouchDb and returns a 404 - which is expected, CouchDb doesn’t have an api database.
We added /api/v1/replication/get-ids in 4.3.0. API proxying this path to Couch would indicate that API is not 4.3.0, but an earlier version, while your client device is on 4.3.0 or later.
Can you please confirm which version of the app you are running? Please check:
- admin upgrade page
- all docker container images
Have you tried to reinstall the app for the users who are getting this error?
Running on 4:12 version
chtuser@vmchecarelive:~/cht/compose$ cat cht-couchdb.yml
services:
couchdb:
image: public.ecr.aws/medic/cht-couchdb:4.12.0
volumes:
- ${COUCHDB_DATA:-./srv}:/opt/couchdb/data
- cht-credentials:/opt/couchdb/etc/local.d/
environment:
- “COUCHDB_USER=${COUCHDB_USER:-admin}”
- “COUCHDB_PASSWORD=${COUCHDB_PASSWORD:?COUCHDB_PASSWORD must be set}”
- “COUCHDB_SECRET=${COUCHDB_SECRET}”
- “COUCHDB_UUID=${COUCHDB_UUID}”
- “SVC_NAME=${SVC_NAME:-couchdb}”
- “COUCHDB_LOG_LEVEL=${COUCHDB_LOG_LEVEL:-info}”
restart: always
logging:
driver: “local”
options:
max-size: “${LOG_MAX_SIZE:-50m}”
max-file: “${LOG_MAX_FILES:-20}”
networks:
cht-net:
volumes:
cht-credentials:
networks:
cht-net:
name: ${CHT_NETWORK:-cht-net}
Hi @Job_Isabai
This is just the docker-compose file. It doesn’t guarantee that this is the running container, and this is only the CouchDb container.
Can you please share the full output of docker ps ?
Hi @Job_Isabai
It looks like all your containers were created 19h ago. Is that when you performed an upgrade?
When did you see the error that you’ve reported?
Yes afterwards, client devices reported the error.
Has the issue been resolved, or are you still getting reports from clients?
Have you tried replicating the issue in browser? Which version did you upgrade from?
Hello Diana,
I have reverted back to 4.5.
I have tested on browser, I will try to set up all the tablets afresh and let you know.
Reverting is not safe!!! You should never revert.
No I had a backup. I restored the VM to an earlier backup
Unless you wiped all devices, rolling back is still unsafe.