-
Notifications
You must be signed in to change notification settings - Fork 271
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
Report expected location of registry backend in UI #5388
Comments
Thank you for reporting an issue! Pinging @EricWittmann to respond or triage. |
@simonepm Have same issue with Kubernetes deployments. When looking into the browser's inspector I saw, that the UI pod requests the browser to directly call the configured Kubernetes internal service URL, which fails of course. Maybe there's a config parameter where URL rewriting / proxying can be configured, but didn't found it in the documentation yet. @EricWittmann Do you have any additional links or information? Thanks a lot in advance! Used versions:
|
Ack, I didn't see this until today! Sorry about that. Typically if you can reach the API via curl but not in the UI then you have a CORS issue. You'll need to configure I would recommend starting with |
In this case you need to configure the UI to know where to find the API. This is done by configuring the UI pod/deployment using this env var:
Set that to the external URL of your registry-api service. Reference: https://github.com/Apicurio/apicurio-registry/blob/main/ui/.docker-scripts/create-config.cjs#L9 If you look at the |
@EricWittmann Thanks for your response! What I did: Have deployed the apicurio-registry in Kubernetes and created a service for accessing the API. Then I deployed the UI pod and configured the What I've seen so far: Calling the URL of the UI ingress brings the same output as @simonepm has shown. When I open the network inspector console of the browser I saw, that the browser tries the URL Maybe I miss something here and would appreciate any help! Thanks! /edit/ |
@EricWittmann Have already played around with this parameter with no effect. I guess if I'd setup a public resolvable API-URL and set the CORS header accordingly, it'll work. |
Feature or Problem Description
With v3, there is the possibility of users not configuring the UI correctly and getting message:
Connection to the Registry server failed (could not reach the server). Please check your connection and try again, or report this error to an admin.
When clicking help, this modal is displayed:
Proposed Solution
On one of the screens, show the user the current configuration, ie where the UI expects to connect to, eg localhost:8080
Additional Context
The text was updated successfully, but these errors were encountered: