-
Notifications
You must be signed in to change notification settings - Fork 269
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
Error loading Registry UI on https #1120
Comments
My best guess based on the information you've provided is that the UI is trying to talk to the API via a non-SSL connection. Likely your browser is denying that. The way this works is that when the UI loads it is configured with the URL of the API it should use. The server tries to generate an appropriate URL for the API based on the HTTP request from the client, but that doesn't always work (it depends on your deployment configuration). So in this case my guess is that the server is failing to properly figure out the API URL. You can fix this by overriding the value using the You can confirm this diagnosis by going here: http://schema-registry-dev.autodesk.com/ui/config.js That is the UI configuration I mentioned above. When I run the app locally mine looks like this: var ApicurioRegistryConfig = {
"mode" : "prod",
"artifacts" : {
"type" : "rest",
"url" : "http://localhost:8080/api"
},
"ui" : {
"url" : "http://localhost:8080/ui",
"contextPath" : "/ui"
},
"features" : {
"readOnly" : false
}
}; Note the |
@EricWittmann That worked, thank you ! Is there more documentation to customize the app? Like the logo, heading, styling etc? I see how to override the quarkus params and how to set the UI read only. Is there anything more that I might have overlooked? |
Unfortunately Studio is not currently designed to be skinnable. You could probably make some minor changes like the masthead logo and background image by providing your own images (perhaps by intercepting the HTTP requests for those resources and providing customized ones). But I think that's the best you could do. :( |
Hello,
I tried deploying the image "apicurio/apicurio-registry-mem:1.3.1.Final" (in memory version) on AWS ECS Fargate for demo purpose. I fronted the UI using ALB on HTTP and HTTPS. The UI loads fine on http, but I notice the following error when I try to browse on https. I haven't tried the PostgreSQL image yet, which is what I actually plan to use in prod.
The text was updated successfully, but these errors were encountered: