Cannot Login using medic account

Technical Support
21

Hi @Marcelo_De_Guzman !

I saw your comment about changing the password for the medic user. The best path forward is to follow Diana’s advice about updating the password. My forum post you cited has great step by step instructions on how to do this.

Please give these a steps a try one at a time and report back if you get stuck on a specific step.

2 Likes
23

Hi @diana and @mrjones ,

Thanks for the advice,

It was already resolve for the problem which is the medic administrator password, @binod teach me on how to do it using this forum RECOVER COUCHDB Password.

And the remaining problems are :

  1. The data is not syncing automatically from couchdb to AWS, so that, when in dbeaver it is not also updated unless, it needs to go to the terminal and login using ssh account, then go to cd /srv/cht-couch2pg and run “docker-compose --env-file couch2pg.env -d”

  2. We have an staging website to test first the app and then once the update was approved it should be push to the production. But, right now, when we access the staging website it shows 404 Not Found nginx/1.13.6

24

I think it might be a good idea to spin up these remaining two issues into their own topics so that they can be documented and tackled separately. I have created new topics for each of the two issues:

26

Hi @diana , @binod

I am re-opening this issue due to our test-flourish (or another medic) is not accessible by login the username and password.

This is the couchdb logs
[info] 2024-05-21T14:56:46.696355Z couchdb@127.0.0.1 <0.9.0> -------- Application couch_index started on node ‘couchdb@127.0.0.1’
[info] 2024-05-21T14:56:46.696547Z couchdb@127.0.0.1 <0.9.0> -------- Application couch_mrview started on node ‘couchdb@127.0.0.1’
[info] 2024-05-21T14:56:46.696792Z couchdb@127.0.0.1 <0.9.0> -------- Application couch_plugins started on node ‘couchdb@127.0.0.1’
[notice] 2024-05-21T14:56:46.796983Z couchdb@127.0.0.1 <0.96.0> -------- config: [features] scheduler set to true for reason nil
[info] 2024-05-21T14:56:46.848421Z couchdb@127.0.0.1 <0.9.0> -------- Application couch_replicator started on node ‘couchdb@127.0.0.1’
[info] 2024-05-21T14:56:46.864623Z couchdb@127.0.0.1 <0.9.0> -------- Application couch_peruser started on node ‘couchdb@127.0.0.1’
[info] 2024-05-21T14:56:46.885001Z couchdb@127.0.0.1 <0.9.0> -------- Application ddoc_cache started on node ‘couchdb@127.0.0.1’
[info] 2024-05-21T14:56:46.912183Z couchdb@127.0.0.1 <0.9.0> -------- Application global_changes started on node ‘couchdb@127.0.0.1’
[info] 2024-05-21T14:56:46.912235Z couchdb@127.0.0.1 <0.9.0> -------- Application jiffy started on node ‘couchdb@127.0.0.1’
[info] 2024-05-21T14:56:46.923315Z couchdb@127.0.0.1 <0.9.0> -------- Applicatioroot@5ee5967fa9a9:/srv#

27

These logs are from May 21, and they say nothing about the problem.

If this hasn’t been solved yet, please share the latest API and sentinel logs.