Closed Cygon closed 2 years ago
This may have to do with the Apache proxy configuration after all.
If I open the container's port and perform the change on http://horizon.home:21618/
directly (no Apache proxying), it works.
Maybe the Apache configuration shown in the Trilium Wiki incorrectly proxies this special case. Almost seems as if the %2F should be un-URL-encoded but isn't. This Apache issue (not necessarily related) has given me a few things to experiment with: https://bz.apache.org/bugzilla/show_bug.cgi?id=34602
Hi, same issue is described here
I faintly remember this being discussed also elsewhere with more information but can't find it now. I think it was some buggy behavior of Apache, but it could be changed with some config IIRC. I'm not sure if it's the bugzilla item you linked or not.
To avoid these kind of issues, 0.49 will have type and MIME in the body instead of in URL.
Preflight Checklist
Trilium Version
0.48.7
What operating system are you using?
Other Linux
What is your setup?
Server access only
Operating System Version
Gentoo Linux stable
Expected Behavior
I expect to be able to change a node's type by opening its type dropdown and selecting any type.
Actual Behavior
When I attempt to change a node's type to any type that specified a mime type in its PUT request, I get the following error message:
("Error when calling PUT notes//type/mermaid/mime/text%2Fmermaid: error - Not Found")
Additional Information
I am running Trilium on NodeJS v14.17.6, served via an Apache 2.4.48 proxy using the recommended proxy setup:
This is equivalent to the recommended proxy setup but omits the http to https redirect (I'm running Trilium in my home network only).
The backend log shows the following (I switched once to the 'book' type, once to the 'render' type and finally attempted to switch to the 'mermaid diagram' type, which failed):