-
-
Notifications
You must be signed in to change notification settings - Fork 74
https proxy settings #211
Comments
I released 2.62. You can select HTTPS for proxy schema. Perhaps that solves it. |
@sintasy did you try this? Can I close it? |
Soo.. Thanks for your response. Now I have next exception:
I've try to find root cause of this in my proxy, but so far unsuccessfully. |
Perhaps you should use another port: |
As I understand in my case http proxy used as https. Bitbucket java_opts contains:
And server send request through proxy without errors(I'am sure because in the network level server have access only to proxy). |
Looks like you start the server with proxy properties and then invoke "mytargeturl". And that invocation will be through the proxy from the properties. Correct? If you avoid specifying a proxy in the plugin, and instead start the server with the properties, perhaps that will give the same results? |
Nope, it's first thing that I've try. Just getting timeout. As I understand httpclient doesn't use proxy settings from java_opts or system environment.
You can reproduce this case if run Bitbucket with java_opts (-Dhttp/s.proxyHost and -Dhttp/s.proxyPort) setting to any non-existent proxy server that must return a timeout. After that try to send any request through Pull request notifications plugin. This request will be successfully delivered, without timeout. It will mean you don't use proxy settings from java_opts. |
Hello, We are also facing the same problem with Unrecognized SSL message error 👎 Can you please help how to solve this, we have installed v3.15 of pull-request notifier plugin over bitbucket v5.1.5. |
Hi. We have the same issue. It seems the used httpclient-4.5.1 does not like calling https-URLs via an http-proxy. But it should :) |
It's definitely a bug, if I change the endpoint url from |
Hi! I try use notification to https webhook trought proxy, but getting exception. Question is it possible?
[{"headers":[],"method":"POST","name":"Notification","postContent":"{\"text\": \":peka:\"}","projectKey":"TST","proxyPort":8080,"proxyServer":"myproxy","repositorySlug":"tst-repo","triggerIfCanMerge":"ALWAYS","triggerIgnoreStateList":[],"triggers":["COMMENTED","OPENED"],"url":"https://mywebhook","uuid":"2fe61472-0fcd-4951-bfe2-74a4b9150591","postContentEncoding":"NONE"}]
The text was updated successfully, but these errors were encountered: