Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restart UI Container leads to HTTP 301 #9186

Closed
nicomanzoni opened this issue Aug 17, 2023 · 4 comments
Closed

Restart UI Container leads to HTTP 301 #9186

nicomanzoni opened this issue Aug 17, 2023 · 4 comments

Comments

@nicomanzoni
Copy link

nicomanzoni commented Aug 17, 2023

Describe the bug

When installing APIM Version 4 on docker and restarting the Console UI or Portal UI container, after the restart trying to access either one leads to a HTTP 301 message and redirects to an empty page on port 8080. It is not dependant on the exposed Ports of the Console or Portal.

To Reproduce

Steps to reproduce the behaviour:

  1. Install APIM Version 4 with docker-compose, either Quick Install or Custom Install
  2. Start the compose with docker-compose
  3. Restart the gio_apim_management_ui container with docker restart gio_apim_management_ui
  4. Access Console UI on web

Expected behaviour

The Console UI loads normally.

Current behaviour

The request returns the HTTP message 301 "Moved permanently" and redirects to Port 8080, where no connection can be established.

Useful information

This issue occurs only with APIM Version 4. Tested on 3.20.xx and works as expected.

Environment

Docker version 24.0.2 APIM Version 4, image tag 4.

@gaetanmaisse
Copy link
Contributor

Did you try with the latest version of APIM 4.0? I recall some fixes on that side, so it's maybe already fixed in APIM 4.0.5

@nicomanzoni
Copy link
Author

Just tried it with version 4.0 published 28th Aug, still same case of when I initially start the stack it works, and after restarting the management_ui container it gets redirected.

@nicomanzoni
Copy link
Author

To add to this issue: Once the problem arises, deleting and recreating the UI container, in addition to emptying the browser cache, solves the problem, but only until the next container restart.

@gaetanmaisse
Copy link
Contributor

@nicomanzoni, we might have found the root cause! We are working on a fix right now, I will keep you posted

@gaetanmaisse gaetanmaisse changed the title [APIM] Restart UI Container leads to HTTP 301 Restart UI Container leads to HTTP 301 Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants