Hello 🙂, Hopefully just a quick question. Can a PactBroker communicate on a private network via private endpoints? At my company, we're exploring pact broker connectivity. If we set the web app to public we can access the pact broker, however setting it to private returns a forbidden response. Is there any app config settings we need to be aware of for network connectivity? We've followed the pact docs to spin a pact broker up. My ops team have looked at the network side of things and cannot see any firewall or other network issues. So we're a bit confused and are looking for guidance to help move things along 🙂. Any help would be greatly appreciated and thank you for your support! 🙂

private network via private endpoints

what does this mean exactly?

Thank you for the quick reply! That's good to know thank you! If we set the pact broker to communicate via a public address we can browse and login successfully and we get a pact broker landing page. If we access the pact broker URL within a private network e.g. not accessible to the outside world. We can browse to it and enter login details, then we receive a forbidden response. I'll go back to my ops team if its the network and investigate. My ops team wanted to validate if there's a app config setting we need to be aware off to access the pact broker via a private network? Thanks again for the help and your patience Matt! 😀

If you had a screenshare/logs to share, that might help with some pointers. Sometimes there are proxies and things that mess with URLs

Thank you! Will give that a try and let you know. Thanks again!