# Issue in Partner Management Portal v1.2.0.1-B2 - FIXED **URL:** \ **Category:** Platform\ **Created:** [March 27, 2023, 2:41pm UTC](https://community.mosip.io/t/issue-in-partner-management-portal-v1-2-0-1-b2-fixed/384 "2023-03-27T14:41:59Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![rcsampang](https://avatars.discourse-cdn.com/v4/letter/r/ecccb3/32.png) [@rcsampang](https://community.mosip.io/u/rcsampang)\ **Post date:** [March 28, 2023, 4:05pm UTC](https://community.mosip.io/t/issue-in-partner-management-portal-v1-2-0-1-b2-fixed/384/4 "2023-03-28T16:05:44Z")
Yes I agree. But somehow in my setup, it didn’t work as expected. I was only able to access and login the partner management portal when I have overridden the Helm charts. I really can’t explain but I was only able to fix the error in my MOSIP setup after doing the steps I stated above, which is basically just manually providing the values that should have been provided for in the installation script. The only difference I know of is that I am using the latest helm v3.11.2, is there an issue with that? I think in my case the --set flag did not override the supplied value, thus when I used values.yaml instead, it was able to provide the correct pmp host and api-internal host for my domain. --- _[View the full topic](https://community.mosip.io/t/issue-in-partner-management-portal-v1-2-0-1-b2-fixed/384)._