API Portal 5.x
The issue is expected when using a self-signed certificate in API Portal.
Internet Browsers such as Chrome, are unlikely to trust self-signed certificate.
The correct solution would be to Create and Sign Certificates in Portal (this is a must in production).
However, if that is not an option or the Portal is not a production system, you can simply allow Chrome to trust the self-signed certificate.
To do so: