Have you tried 192.168.4.100:8080/recipes/default/tiddlers.json? Can you access it? Also try 192.168.4.100:8080/recipes/default/tiddlers.json?filter=[tags[]] . This is the easiest way to know if your server is providing API.
I think extension it self is working, you can try use it with TidGi Desktop https://tidgi.fun/ , if you are not a technical person. Or you can start a new post in the forum about this issue, because I think it is not relevant to clipper extension now.
I can access both these urls from Firefox.
I got the following 2 warnings about your plugin after going to about:debugging#/runtime/this-firefox (in the address bar). Not sure if this could be related:
After clicking on “Examiner” I got these details:
I also disabled most of Firefox security and privacy settings to make sure they were not interfering.
Still no success. Anyway if I find anything I’ll post it here in case someone else would face the same issue.
Thank you.
I see, this is OK, I also have this in about:debugging#/runtime/this-firefox , but note that my uuid is b022af37-6fb5-4c06-9ca2-76b205b10447, if this isn’t unique for each user, then you might not using latest version v0.6.0 ?
Usually it can load your tags list in the config, so you can add default plugins, is that work for you? I can confirm it works with my TidGi app’s HTTP API on my Mac.
I tried my local IP http://10.100.1.117:5217/, and it show the same error! So maybe for security, Firefox block the request to any other server, you can only send request to the localhost.
So the solution is, You need to use http://localhost:xxx instead of ip like https://192.168.4.100:8080/
Anyway, at least it works with TidGi app, that is it originially designed for.
Is it related with CORS?
The error is NS_ERROR_GENERATE_FAILURE(NS_ERROR_MODULE_SECURITY, SSL_ERROR_RX_RECORD_TOO_LONG), means it try to use https for security.
So maybe if you don’t use TidGi app’s free localhost http API, you will need to setup a HTTPS for your remote server API. http:// is only for localhost, for remote you will need “s” in https://192.168.4.100:8080/
This is what I guess, I don’t have such server to test now.
SOlution:
You need to use http://localhost:xxx instead of ip like https://192.168.4.100:8080/
Is there any way to set a username and a password to save the clip to a password protected tiddlywiki instantiation?
@linonetwo Your last comment remembered me that I have the Firefox https everywhere plugin activated, so I deactivated it and tried again.
No success. 
Changing http to https means I need a proxy server on the nodejs server. I don’t really have such a need as this server isn’t exposed to the Internet, only local lan.
Still I may install one and test this later. Thank you for following up.
It might be Firefox’s limination, even on my PC and local TidGi, changing localhost to ip will prevent it working.
So maybe firefox only support localhost connection or https ip connection.
So it is best to use TidGi app on PC directly.
This only support local nodejs server, but a local nodejs server don’t need to set up password.
It should be easy to support encrypted login. TW has recently added token authentication support.
@linonetwo I tried the extension in firefox. But it failed to connect to my tidgi desktop wiki. I had enabled HTTP APIs in the workspace config
You need to use http://localhost:xxx instead of ip like https://192.168.4.100:8080/
@linonetwo I tried those, Its showing Adding , Add success notifications. But I can’t find any of them in my recent list of tiddlers
So http://localhost:xxx does solve your problem?
I haven’t encounter this, you could inspect the you could add a tag and check if it is under the tag.
Oh, I just think, you might not have SSE. On TidGi Desktop, we have build-in SSE to push change from server to the client. But in plain old nodejs wiki, it doesn’t have such a good thing.
I am actually using tidgi mac application
yes there error message has disappeared, but i couldn’t find the clipped contents in my wiki
Then you could right click - Current workspace - “Open in Git application” , and check if the .tid file is added, and just not sync to the frontend.
But on my side, I checked it will immediately show in the Sidebar - Recent tab. Don’t know what happened on your side. Maybe you could right click - Current workspace - “Open in browser”, check if nodejs server works. Or use Postman app to check nodejs server’s PUT route works or not https://tiddlywiki.com/#WebServer%20API%3A%20Put%20Tiddler PUT http://localhost:5226/recipes/default/tiddlers/testtest
It won’t show on Recent tab because this new tiddler doesn’t have created field. (seem to be an old bug in old version?) In Firefox version that I use now, it will have created modified field included.
Sorry for the delay in reply. My laptop was down for a few days due to battery issues.
I couldnt find the .tid file getting created anywhere in the wiki folder.
You could try PUT with postman app like I screenshot above, test it is nodejs server’s problem or webclipper’s problem, I screenshot it just for you.
I’m using firefox, I can only say firefox version is working, perhaps Chrome version is broken.
I am using Firefox.
Will use the Postman app and see
Edit:
What url should I type in the PUT box. My wiki path is "C:\Users\username\OneDrive\my-wiki-core"
I tried this url in postman app
PUT http://localhost:10.0.0.7:5213/tiddlers/test121
Should be http://localhost:5213/tiddlers/test121
Use the one you put in the webclipper extension as prefix, it should be like http://localhost:5213
