@diana , i want to setup the cht-gateway and connect it to my local instance ie https://192-168-0-103.my.local-ip.co/ but the app is thorwing error URL not responding in expected way . Note that i acces my instance from a browser with the above url

@mozzy - Thanks for the update and the confirmation that the error is in the chain. Did you double check that you you added the intermediate cert before copying the default.crt file to the container? Is there another nginix, or any other web server, with this *.openelis-global.org cert that you can…

@mozzy This will be the case in the next major version 4.0. coming later this year.

@mozzy - You are correct that the medic-os image on docker hub has not been updated recently. It ships with 3.9.1 However, you can follow these steps to update your instance to 3.13. Assuming your URL is https://192-168-0-103.my.local-ip.co/: Login as admin Go to the Admin menu in the upper right…

@diana , i set up a CHT test instance on AWS , and installed some valid certificates . This works fine on all browsers but the CHT-gateway Andorid app still throws SSL connection failed while the cht android app throws ‘Unable to contact server’ see Chrome validates the certificate [image]

May be you could find these Nginix logs useful error-ssl.log 2022/01/14 08:44:00 [error] 460#0: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 41.210.146.124, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:5988/", host: "cht.openelis-global.…

Thanks for reporting, @mozzy I tried your host on my mobile device using CHT-Android and I’m getting the same error. I’m also getting the an error when I try to access the URL on Firefox on my Android device, Chrome works however. Pasting the whole Java error here for reference: 2022-01-14 14:31…

Hi @mozzy . I noticed you’ve switched out the certificate on cht.openelis-global.org to be the local-ip.co one: echo |openssl s_client -connect cht.openelis-global.org:443 | openssl x509 -noout -dates depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1 verify return:1 …

Thanks @mrjones . [image] mrjones: If this is the case, then to remove the TLS errors, you can use https://44-228-97-26.my.local-ip.com as your URL. Yeah. i did that as a quick work round for the mean time ,as i was trying to debug why my certs fail to validate on Android. so temporalily we…

@mrjones , Thats true , when i install back the *. openelis-global.org cert and i try to verify it i get depth=0 C = US, postalCode = 98195, ST = Washington, L = Seattle, street = 4545 15th Ave NE, O = University of Washington, OU = UW-IT, CN = *.openelis-global.org verify error:num=20:unable…

[image] diana: Indeed there’s a typo in the route (/api/v1/sms/radpidpro/incoming-messages) so please hello @diana Am trying to integrate rapidpro with cht however am getting { "code": 400, "error": "Message was not saved" } [Screenshot from 2022-01-27 11-36-48]

Hi @cliff Please share API logs to see more details about what is going on. Alternatively, please share the contents of your POST body.

Community Health Toolkit

Connecting sms gateway to local CHT instance

Development

sms

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled