-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
Print an explicit error message when the URI is too long (414) #853
Comments
It's probably because Excalidraw is a verbose textual format. You got an HTTP Error 414 (URI Too Long) from kroki.io (or your kroki instance) right? You can change the max uri length using the I tried your diagram on an local Kroki instance with |
Still doesn't work for me :( Where can I find log files or the http error, as I don't see any 414 error. I'm starting the excalidraw docker with this: Here is the contents of /etc/kroki.env:
|
@rrrevin you should define the |
I did that as well. This is the docker startup for the main server; they all reference the same env file: |
Figured this out. Turns out there were two issues. The one you pointed out above (KROKI_MAX_URI_LENGTH) and a system that came up with the same IP as the kroki server. All working now. Thanks all. |
Glad you figured it out! 👏🏻 Unfortunately, I think we cannot log an explicit message because the max URI length check is somehow "low level". I think the exception is thrown by Netty (the underlying network library used by Vert.x): I will dig a bit further to see if we somehow can catch the 414 error in order to print a friendly error message (we could even suggest to increase the max URI length using the |
… too long (414)
… too long (414)
… too long (414)
… too long (414)
I'm using wiki.js with the kroki add-in enabled. I can get a ton of diagrams working, but this one will not render. It was created using the excalidraw website itself (https://excalidraw.com). But when I try to render it using the kroki excalidraw docker image.. it fails. All of my other excalidraw diagrams work using the same docker.. just this one doesn't.
Don't know where to find logs to help unfortunately, I just know I get nothing back from the docker for this one diagram. Anyone have an idea?
It should look like this:
The text was updated successfully, but these errors were encountered: