MongoDB Charts installed on localhost Windows 10, but cannot access through browser

MongoDB Atlas MongoDB Charts
1

I have successfully installed mongodbcharts with Docker, the service is active but cannot access it through the browser http: // localhost or http://127.0.0.1

2

Hi @Pierre-Yves_Touche,

Can you confirm you followed:
https://docs.mongodb.com/charts/current/installation/

Additionally please provide output of the commands in our troubleshooting guide:

Thanks
Pavel

3

Yes i confirm this installation and service is enable
I changed the local port to 8888 instead of 80 but nothing on url : http://localhost:8888

r5bcggfrejnk mongodb-charts_charts replicated 1/1 Quay *:443->443/tcp, *:8888->80/tcp

PS D:\chartsmongo> docker service logs r5bcggfrejnk
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ parsedArgs
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ installDir ('/mongodb-charts')
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ log
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ salt
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ productNameAndVersion ({ productName: 'MongoDB Charts Frontend', version: '1.9.1' })
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ gitHash (undefined)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ supportWidgetAndMetrics ('on')
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ tileServer (undefined)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ tileAttributionMessage (undefined)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ rawFeatureFlags (undefined)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ stitchMigrationsLog ({ completedStitchMigrations: [] })
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ featureFlags ({})
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ lastAppJson ({})
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ existingInstallation (false)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ tenantId ('b05dc81e-bb47-4583-a9e1-d0f413a4c330')
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ chartsMongoDBUri
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ tokens
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ encryptionKeyPath
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ stitchConfigTemplate
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ libMongoIsInPath (true)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ mongoDBReachable (true)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ stitchMigrationsExecuted ([ 'stitch-1332',  'stitch-1897',  'stitch-2041',  'migrateStitchProductFlag',  'stitch-2041-local',  'stitch-2046-local',  'stitch-2055',  'multiregion',  'dropStitchLogLogIndexStarted' ])
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ minimumVersionRequirement (true)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ stitchConfig
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ stitchConfigWritten (true)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ stitchChildProcess
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ indexesCreated (true)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ stitchServerRunning (true)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ stitchAdminCreated (false)
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✔ lastKnownVersion ('0.9.0')
mongodb-charts_charts.1.szg9zu143ddy@docker-desktop    |  ✖ existingClientAppIds failure: An error occurred authenticating: invalid username/password
5

Hi @Pierre-Yves_Touche -

The service won’t be accessible through a browser if it does not start successfully, which is what is happening here.

The “existingClientAppIds failure: An error occurred authenticating: invalid username/password” error seen in your logs can happen if the metadata database contains a previous installation of Charts, but the mongodb-charts_keys volume does not contain the required credentials. If you’re attempting a fresh installation, the easiest thing is to delete all data in the database and remove the Docker volume and start again.

Tom

1 Like
6

No errors in logs but no access to localhost…

7

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.