Uploaded image for project: 'apiman (API Management)'
  1. apiman (API Management)
  2. APIMAN-1202

Unable to publish after changing gateway endpoint to docker IP

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 1.3.x
    • 1.2.7.Final
    • Management UI
    • None
    • Hide
      1. docker pull apiman/on-wildfly10:latest
      2. docker run -ti -p 8443:8443 apiman/on-wildfly10:latest
      3. Login to Apiman
      4. Go to the admin section and change the gateway URL from localhost to the external IP-adres on which Docker is running. My example: 192.168.99.100
      5. Test the gateway with the new IP. See:
      6. Create a New Organization
      7. Create a new api with some random implementation and publish it.
      8. The stacktrace stacktrace.txt appears.
      Show
      docker pull apiman/on-wildfly10:latest docker run -ti -p 8443:8443 apiman/on-wildfly10:latest Login to Apiman Go to the admin section and change the gateway URL from localhost to the external IP-adres on which Docker is running. My example: 192.168.99.100 Test the gateway with the new IP. See: Create a New Organization Create a new api with some random implementation and publish it. The stacktrace stacktrace.txt appears.

      I started the "out of the box" docker image from: https://hub.docker.com/r/apiman/on-wildfly10/
      After Apiman is started I changed the gateway endpoint to match the endpoint that apiman is available on through docker.

      In my scenario that is: 192.168.99.100 instead of localhost.
      After changing the gateway I am unable to publish my api. I get a stacktrace in the UI: stacktrace.txt

        1. change-gatway-api.png
          change-gatway-api.png
          231 kB
        2. logfile.txt
          39 kB
        3. stacktrace.txt
          7 kB

              ewittman@redhat.com Eric Wittmann
              ton@finalist.nl Ton Swieb (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: