You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Installation Problems

ProblemPossible ReasonSolution
  • API Management will not start.
  • Docker deamon does not respond anymore.

The assigned resources for Docker for Windows or for the Docker Toolbox are not enough for API Management.

  1. Open your Docker Settings from windows context menu.
  2. Navigate to tab "Advanced".

  3. Increase the memory to at least 8192 MB:

You cannot login to API Management.

You have configured localhost for variable ENDPOINT in your .env file.

  • You cannot use localhost as endpoint. Please configure your full hostname e.g. api.acme-corp.com.
  • Your hostname must resolve to the IP of your server.
    localhost or 127.0.0.1 will not work, because this will resolve to localhost of your container.

  • Check if you have correctly configured your etc/hosts file on Windows or Linux. You can try this using the ping command.

    /etc/hosts
    # localhost name resolution is handled within DNS itself.
#	127.0.0.1       localhost
#	::1             localhost

192.168.99.100	api.acme-corp.com

After accessing the Login Page you see the error Invalid parameter: redirect_url.

The redirect URL is configured wrongly in Keycloak.

Change the Keycloak settings as described on Setting up API Management > Changing the Keycloak Settings.

Cannot run docker-compose on gateway container:
Docker-compose throws NoSuchFileException for e.g. jks files during build.

You are using Docker for Windows and you have changed your Windows password recently.

There is an mounting issue using Docker for Windows.

You can try this workaround:

  1. Open Docker settings.
  2. Click on the Shared Drives tab.
  3. Deselect your shared drives.
    Click Apply.
  4. Select the drives you want to share.
    Click Apply.
    Docker should prompt you to re-enter your credentials.
  5. Rerun docker-compose.

On this Page:
Related Documentation:

  • No labels