does pact allow us to update the default broker po...
# pact-js
c
does pact allow us to update the default broker port?
m
Chaitanya, please try googling it or better - searching on docs.pact.io Once you have found your answer, please try it out. If what you are trying hasn’t worked, please come back and explain what you are trying to do, what you’ve tried, and what’s not working. See howtoask
s
Please see this page for some tips on how to ask for help to get the best response from the community https://docs.pact.io/help/how_to_ask_for_help
c
iam trying to publish my sample pacts to my central broker and it is throwing error inside the pact library , I have googled it but could not find a relevant example. it errors on port as connection refused .
m
Please see the other thread where you have the problem. You think the problem is the port, but if you provide the logs as requested we might be able to understand the real root cause. Changing the port is as simple as updating the URI you are publishing to, but that may not be the real issue (I suspect it’s something else)
seeing the logs will give us visibility into your issue
Let’s keep this thread going, as the ask you have above relates to it
For context: I’m currently reasonably confident that the issue is a configuration problem with your pact broker, and the verbose logs will confirm that theory.
c
Copy code
"test:publish": "pact-broker publish ./pacts --consumer-app-version=1.0.1 --auto-detect-version-properties --broker-base-url=<https://ysi5tc076m.execute-api.eu-west-2.amazonaws.com:80> --broker-username user --broker-password pass --verbose"
I have tried this and the output I get is same as above
do u mean the way the broker is setup ? I can log into the broker url normally
do u think being in aws its restricted on access?? due to firewalls?
message has been deleted
this is my pact broker screen
m
that confirms the problem for me
note in the “Response body” section, the links are all
http
, but in the “Explorer” section (and presumably the address bar) it’s a secure
https
link? That’s why it’s publishing to port
80
and failing.