Webhook fails when using an alternative port in the url

XMLWordPrintable

      I have been trying for the past few days to set up a webhook to our Jenkins server and we had our Jenkins server using 4210 for https instead of 443. Our server url is https://jenkins.companyname.com:4210.

      My webhook kept failing with NET_ERR with no discernible reason to the failure. As a test I changed our Jenkins server to run behind port 443 and the hook then succeeded. The successful url was https://jenkins.companyname.com.

      Are webhooks supposed to work with custom port numbers? If not is there a timeline to update them so hooks can post to alternative ports if needed? In further testing I have verified my URL is valid and does post to Jenkins using a hook in GitHub.

        1. FailedHooks.PNG
          15 kB
          raffledoocious

            Assignee:
            Dan Tao
            Reporter:
            raffledoocious
            Votes:
            9 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated:
              Resolved: