odpi / egeria

Egeria core
https://egeria-project.org
Apache License 2.0
808 stars 261 forks source link

ui server chassis - whitelabel error page #3892

Closed planetf1 closed 3 years ago

planetf1 commented 4 years ago

WHen launching the UI server chassis in any of the following ways, an attempt to go to https://host:8443 (or forwarded port) results in:

Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.

Thu Oct 15 14:21:24 GMT 2020
There was an unexpected error (type=Internal Server Error, status=500).

There are no useful audit events produced, or any log messages produced at default log level (or when setting LOGGING_LEVEL_ROOT to Info)

This occurs when

planetf1 commented 4 years ago

Note that when run in the last case, parms are also set for the location of the certs etc -- however in all case we see failures.

planetf1 commented 4 years ago

Also get this when following the new instructions for developer use in the ui server chassis spring dir

mvn spring-boot:run -Dspring-boot.run.folders=/path/to/libs/ -Dspring-boot.run.arguments="--theme=default --zuul.routes.ui.url=http://localhost:8081 --omas.server.name= --omas.server.url= --open.lineage.server.url= --open.lineage.server.name= --server.ssl.trust-store=./src/main/resources/truststore.p12"
sarbull commented 4 years ago

this is because there is no more static content in the ui-chassis-spring, no index.html, and you get that error due to the fact that there is no static server started in parallel and URL given as a parameter to the ui-chassis-spring

planetf1 commented 4 years ago

Thanks, suggest

sarbull commented 4 years ago

i'll add this to the README.md as a known issue

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

planetf1 commented 3 years ago

this is not occuring when the UI is correctly deployed - closing