Replies: 1 comment 3 replies
-
Hi, maintainer of Apiman here. A small amount of investigative digging would be needed, as there can be several causes for this — usually security-related or Docker networking quirks (CORS, network, Keycloak tweaks, etc). Are you a BPL support customer? If so, I'd be more than happy to spin up a support call for you to figure it out. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have been struggling to expose API Man to the public internet from my IP Addresses (instead of localhost) and running into some weird issues.
I am using the API Man Docker Compose Quick Start for version 3.1.3 Final
In the
.env
file I setI then took down the container
and then restarted the container
When I try to navigate to
http://my_ip_address:8080/apimanui
I get redirected to
http://my_ip_address:8080/realms/apiman/protocol/openid-connect/auth?response_type=code&client_id=apimanui&redirect_uri=http%3A%2F%2Fmy_ip_address%3A8080%2Fapimanui&state=5b1b91be-3029-4859-9d8d-e674b68347c3&login=true&scope=openid
and a refused to connect errorWhen I go to the portal url I get a white screen and connection refused errors

It's not a Firewall issue:
I tried searching the docs and this forum but could not find anything to helpful.
Has anyone else experienced this issue before / can someone please help me resolve it?
Beta Was this translation helpful? Give feedback.
All reactions