

The first command is successful and sends a 301 result however, the second command throws a 404 error and thus redirects me to the 404 Not Found page. Good morning! Thank you for the quick reply 1.

If you’ve since restarted/destroyed the containers, run docker ps to get the new ID for medic-os. Using the ID above from docker ps we’ll use 7ab7bed30eaa.

Check that couchdb is up and running: Ideally from your Ubuntu terminal this should work curl -k However, if it doesn’t, try getting shell on your container to test.Or, just go crazy and post lots of log data, better too much than too little This call may show a lot of log data, so we’re looking for anything that shows an error. If you do see this, try going to (not the “s” in https!). The second should send you the HTML for the login form for the CHT. That first command should not actually send a 404, but a 301 to redirect you to the https URL. The output of both curl -I and curl -kI I want to confirm what server is running there and what info it’s sending.Let’s see what’s going on with the server. When I run the same docker command on my local dev instance, I get the same output. Specifically, you have two containers running medic-os and haproxy and medic-os is listening on the right ports. Thanks for the report! That all looks correct. Both for the blank local setup and setup with test data.
#404 not found nginx 1.4 6 ubuntu windows 10#
I tried the exact same steps on a Windows 10 machine with WSL2 installed and it worked.
#404 not found nginx 1.4 6 ubuntu how to#
I am hoping its a trivial that I might have overlooked.Īfter installing all of the required resources and following all implementation steps, I cannot access the application on the browser ( How To Reproduce The Issue I am having problems with setting up either a blank or CHT Maternal & Newborn Health Reference application onto my local machine.
