hello @diana i would like to get some clarification on the credentials used to access the development build of your CHT application talked about here in the browser ? I have https://192-168-110-70.my.local-ip.co/ giving me the login UI

@cliff - I’m not sure if you’re on a different network now and that’s why it changed, but per your (super helpful \o/) ip a testing, your IP is 192.168.235.70 instead of 192.168.110.70. Can you test with https://192-168-235-70.my.local-ip.co and let us know if that is successful?

[image] cliff: credentials used to access the development build of your CHT application @cliff - initial credentials should be set based off of the environment variables passed into docker . If you copied and pasted from that page COUCHDB_USER=myadminuser -e COUCHDB_PASSWORD=myadminpass then…

[image] mrjones: @cliff - initial credentials should be set based off of the environment variables passed into docker . If you copied and pasted from that page COUCHDB_USER=myadminuser -e COUCHDB_PASSWORD=myadminpass then it would be myadminuser and myadminpass. Let us know if that worked! @m…

[image] cliff: Unexpected error while logging in. Please try again. If the credentials were incorrect, the message you would see is Incorrect user name or password. Please try again. (this is true for recent versions. Which version have you deployed?). Can you please look up medic-api logs ( d…

[image] diana: (this is true for recent versions. Which version have you deployed?). thanks @diana i have "version": "3.14.0", for medic in the package.json file [image] diana: Can you please look up medic-api logs ( details about how to get api logs ) and find the error there. The prob…

hi @cliff In the logs you shared, there is no indication of any login attempt (it actually looks like myadminuser is already logged in). Can you make sure that the request is making it to the server? Checking browser logs while trying to login could help you figure this out.

hello @mrjones @diana When obtaining a TLS certificate for CHT docker instance , the DNS fails with curl: (28) Failed to connect to 192-168-110-70.my.local-ip.co port 443: Connection timed out could this be an issue with local-ip.co HTTPS reverse-proxy used ? cliff@cliff-Latitude-5580:~/Documents/…

@cliff - I believe you have successfully obtained the TLS certificate as there are indeed no errors above the “If no errors output above, certificates successfully installed.” line. Further, according to the curl docs , error 28 is: Operation timeout. The specified time-out period was reached acco…

[image] mrjones: Can you confirm the IP of your machine is indeed 192.168.110.70? I’m guessing this is wrong. thanks @mrjones for your response when i run ip a in the terminal is get cliff@cliff-Latitude-5580:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group …

[image] mrjones: Can you test with https://192-168-235-70.my.local-ip.co and let us know if that is successful? @mrjones with https://192-168-235-70.my.local-ip.co/ am able to get the medic app

@cliff - wonderful! Thanks for letting us know you were successful.

Community Health Toolkit

Setting up the CHT development build

Development

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled