Ajay Arjunan

Same here, the SSL certificate needs to be properly created and installed for https://registry.bower.io/packages/ to get this resolved: 

As @mchrapek mentioned here:- https://github.com/bower/bower/issues/2608#issuecomment-1519835378, adding `"strict-ssl": false` to .bowerrc file made it worked **Edit: This is not a recommended approach, but for testing only.**

From what we have noticed, this issue seems to be happening in the servers/machines that was already performing bower commands, which has some SSL certificate caching present during the SSL...