this will be due to your wiremock server using a self-signed certificate that chrome does not recognise. it may be possible for you to configure chrome to trust a self-signed certificate but i do not know how off the top of my head. it's also possible to use wiremock as a browser proxy over http. this is a much simpler option and has no additional security concerns generally. more info here
https://wiremock.org/docs/proxying/#browser-proxying-of-https.