openlmis-ref-distro icon indicating copy to clipboard operation
openlmis-ref-distro copied to clipboard

bad credentials

Open kerolayne opened this issue 1 year ago • 10 comments

I configured an instance following the steps indicated in a test environment, but the username and password do not return "bad credentials", how can I resolve this?

kerolayne avatar Sep 04 '24 15:09 kerolayne

Hi @kerolayne, could you please provide more details about the issue you're encountering?

mgrochalskisoldevelo avatar Sep 05 '24 10:09 mgrochalskisoldevelo

I configured it as described in the readme, and when using the credentials described in it, they show as not found. I'm attaching a printout with the error that appears when I try to log in. adm password Captura de tela 2024-09-05 112134

kerolayne avatar Sep 05 '24 10:09 kerolayne

In general to make application run it should be enough:

Clone Repository Run:

cp settings-sample.env settings.env

change ip's in settings.env to yours, for example http://192.168.0.23, then run:

docker compose pull
docker compose up

Once containers initialize wait around 5 minutes. Verify all containers are up and running with docker ps.

You can also verify if the local database contains demo data (for example administrator user). spring_profiles_active=demo-data,refresh-db should upload new data with each start. command: postgres -c 'max_connections=300' can be also set to the database service. image

It looks like random error and restart should help if everything is configured as mentioned above.

mgrochalskisoldevelo avatar Sep 05 '24 10:09 mgrochalskisoldevelo

@mgrochalskisoldevelo hello i use your steps and i still have this when try login

Image

please, are you know how can i fix that ?

@kerolayne are you found soluatiion for this error ? please help me

kalshagory2-cpu avatar Aug 04 '25 08:08 kalshagory2-cpu

@kalshagory2-cpu Please verify if all OpenLMIS microservices are running.

You can execute docker ps -a to see all containers - running and stopped - the only stopped olmis-related container should be -configuration.

Additionally, inspect the logs of the containers - docker logs --tail 100 <name> - especially _auth container and _referencedata - it should provide some tips on what went wrong.

pwargulak avatar Aug 04 '25 09:08 pwargulak

@pwargulak thanks this is my containers

                docker ps -a

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES fc5f951ff4ea openlmis/fulfillment:9.2.0 "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-fulfillment-1 67c1323cddd1 openlmis/requisition:8.4.0 "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-requisition-1 ad2f9875dd04 openlmis/cce:1.3.5 "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-cce-1 6de5319bc1df openlmis/buq:1.0.2 "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-buq-1 e94b8e933ed6 openlmis/referencedata:15.3.0-hotfix "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-referencedata-1 6fdd037f890d openlmis/report:1.4.0-hotfix "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-report-1 69ef9823f947 openlmis/hapifhir:2.0.4 "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-hapifhir-1 a1dc11a22e0b openlmis/auth:4.3.5 "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-auth-1 2b7850555e8d openlmis/notification:4.3.5 "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-notification-1 05df9b4e9276 openlmis/stockmanagement:5.2.0 "/wait-for-postgres.…" 41 minutes ago Up 41 minutes 8080/tcp openlmis-ref-distro-stockmanagement-1 e52c25b8823b openlmis/postgres:12-debezium "docker-entrypoint.s…" 41 minutes ago Up 41 minutes 5432/tcp openlmis-ref-distro-db-1 a9c7ccc3be4f openlmis/dhis2-integration:1.0.1 "/bin/sh -c ./run.sh" About an hour ago Up About an hour 8080/tcp openlmis-ref-distro-dhis2-integration-1 4974f31215f9 openlmis/diagnostics:1.1.4 "/bin/sh -c ./run.sh" About an hour ago Up About an hour 8080/tcp openlmis-ref-distro-diagnostics-1 e7407ebd7247 openlmis/rsyslog:3 "./startup.sh" About an hour ago Up About an hour 514/tcp, 514/udp openlmis-ref-distro-log-1 905270f2ea21 driesva/proftpd "/usr/local/sbin/doc…" About an hour ago Up About an hour 0.0.0.0:20-21->20-21/tcp, [::]:20-21->20-21/tcp openlmis-ref-distro-ftp-1 36ba5848ecd9 openlmis/nginx:6 "/home/run.sh" About an hour ago Up About an hour 0.0.0.0:8080->80/tcp, [::]:8080->80/tcp openlmis-ref-distro-nginx-1 e4ed008e7ebc openlmis/reference-ui:5.2.11 "/docker-entrypoint.…" About an hour ago Up About an hour 80/tcp openlmis-ref-distro-reference-ui-1 1f15cf58543f redis:3.2.12 "docker-entrypoint.s…" About an hour ago Up About an hour 6379/tcp openlmis-ref-distro-redis-1 088072f87eb0 gliderlabs/consul-server "/bin/consul agent -…" About an hour ago Up About an hour 8301-8302/tcp, 8301-8302/udp, 8600/tcp, 8600/udp, 0.0.0.0:8500->8500/tcp, [::]:8500->8500/tcp, 0.0.0.0:32852->53/tcp, [::]:32852->53/tcp, 0.0.0.0:32853->8300/tcp, [::]:32853->8300/tcp, 0.0.0.0:32854->8400/tcp, [::]:32854->8400/tcp openlmis-ref-distro-consul-1

all is running and give true status

this is logs for auth container

Image

and this is logs for referencedata

Image

please are you find any error ?

kalshagory2-cpu avatar Aug 04 '25 09:08 kalshagory2-cpu

Hi @kalshagory2-cpu, based on the logs you provided I don't see any issues at the first sight.

What could potentially help:

Instead of docker compose pull and docker compose up, try to run the application with docker compose up --build --force-recreate. You could also try to run the command with sudo: sudo docker compose up --build --force-recreate.

Then after 5 minutes you should be able to log in, please let me know if that helps.

mgrochalskisoldevelo avatar Aug 06 '25 15:08 mgrochalskisoldevelo

@mgrochalskisoldevelo

thanks for your tips but i still have same issues but after try login i get this log in reference data container

Image Image Image

can you see it and give me any advice please ?

kalshagory2-cpu avatar Aug 07 '25 08:08 kalshagory2-cpu

@kalshagory2-cpu I see the error for a first time, however could please try:

sudo docker ps sudo docker restart nginx_container_id and sudo docker restart reference-ui_container_id

mgrochalskisoldevelo avatar Aug 07 '25 11:08 mgrochalskisoldevelo

@mgrochalskisoldevelo now i see this error in log of auth container

Image

but when i use wrong password it give me it is wrong but when i use true i get token in this api 'http://127.0.0.1:8080/api/oauth/token?grant_type=password'

i wish if you provide me with you email to speak there and found way to help me please .

kalshagory2-cpu avatar Aug 07 '25 13:08 kalshagory2-cpu