-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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: rison decoder error: missing ':' #75957
Comments
@jujis008, could you share the Kibana URL that is being loaded? this error means that state in Error handling will be improved in next major version, so Kibana would still load in case when state in query params is corrupted. |
Pinging @elastic/kibana-app-arch (Team:AppArch) |
@Dosant Exactly as you analyzed, here I found why this error happens, you can see the query below query:Transaction%20Controller666, the parameters contains a blank space which encoded by URL automatically, so that lead to not properly serialized. if I replace space to _ is working good... I cannot share the URL, but I could share the parameters in URL as following, |
@jujis008, I think if there is a special symbol, it has to be wrapped with |
@Dosant Yeah, wrapping with |
Closing, as error handling is improved in: #74264 |
I'm still seeing this error on elastic cloud instances. We are sending two separate clusters metrics to this elastic search cluster. One of the clusters monitoring works fine and other one errors and redirects to this other working cluster. Here is the url: Edit: We just upgraded to 7.10 version. |
Hi @mantrala, This is going to be fixed in 7.10.1 by #83987 as a workaround for 7.10.0, wrap
|
Thanks @Dosant that worked. |
Kibana version: 7.8.0
Elasticsearch version: 7.8.0
Server OS version: Linux
Browser version: Chrome 84.0.4147.125
Browser OS version: Mac OSX
Original install method (e.g. download page, yum, from source, etc.): Download from elastic.co
Describe the bug: Error: rison decoder error: missing ':'
Steps to reproduce:
Using iframe loading existing dashboard from kibana, there might be some kind of blank space caused the issue, we did use encodeComponentURI to decode the result, but for load data the issue happens
Expected behavior: load data correctly
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered: