Inacurate error message

[nil0x42]

trilium-web-clipper/trilium_server_facade.js

Lines 179 to 185 in a952c1b

	catch (e) {
	console.log("Sending request to trilium failed", e);
	toast('Your request failed because we could not contact Trilium instance. Please make sure Trilium is running and is accessible.');
	return null;
	}

Any exception is catched, and returns this message about "failing to contact trilium instance".
So any bug or issue is mistaken by the user as a network error.
A consequence of this is loosing potential people posting issues here, and making debug more difficult.
An easy way to access e error should be easily viewable, in order to ease debugging and posting of issues.

I personally just has this kind of issue, and not being very aware of how javascript works, i'm not even capable of finding where the output of 'console.log()' is.
(i was trying to send a page to trilium from a specific site and it doesn't work, while still working on other sites)