Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-5712

Bamboo repository IP field does not allow to enter IPv6 addresses

      The validation fails if a IPv6 address is entered. Also, having IPv6 enabled, breaks Bamboo IP Whitelisting.

      The following error is returned when the build is triggered:

      <errors>
      <error>Build request for plan "My Plan" originated from 127.0.0.1,0:0:0:0:0:0:0:1 which is not an allowed address (one of[, 127.0.0.1]).</error>
      </errors>

      Workaround

      If IPv6 is enabled on the Bamboo server, it can be disabled to workaround this issue.

            [BAM-5712] Bamboo repository IP field does not allow to enter IPv6 addresses

            This bug is critical for me since it does not allow to add any trigger.

            When I call curl http://127.0.0.1/api/rest/updateAndBuild.action?buildKey=ABC-DEFG I always get the message:

            <error>Build request for plan "Dummy - Dummy Plan" originated from 127.0.0.1,0:0:0:0:0:0:0:1 which is not an allowed address (one of[, 127.0.0.1]).</error>

            But I am unable to add 127.0.0.1,0:0:0:0:0:0:0:1 to the IP addresses list ("Trigger IP addresses" field under "Plan configuration >> Triggers" tab). I have the problem when I add an IP from any network (at home, work, customer, other server etc.)

            This completely blocks the usage of hooks since it does not work for any configuration and there is no workaround.

            Andre Sturm added a comment - This bug is critical for me since it does not allow to add any trigger. When I call curl http://127.0.0.1/api/rest/updateAndBuild.action?buildKey=ABC-DEFG I always get the message: <error>Build request for plan "Dummy - Dummy Plan" originated from 127.0.0.1,0:0:0:0:0:0:0:1 which is not an allowed address (one of [, 127.0.0.1] ).</error> But I am unable to add 127.0.0.1,0:0:0:0:0:0:0:1 to the IP addresses list ("Trigger IP addresses" field under "Plan configuration >> Triggers" tab). I have the problem when I add an IP from any network (at home, work, customer, other server etc.) This completely blocks the usage of hooks since it does not work for any configuration and there is no workaround.

            Is there any workaround to whitelist IPv6 address?

            Valery Sarkisov added a comment - Is there any workaround to whitelist IPv6 address?

              Unassigned Unassigned
              ukuhnhardt Ulrich Kuhnhardt [Atlassian]
              Affected customers:
              8 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: