Webclipper fails to connect to client #561
I've updated Joplin to version 1.0.95 and installed the clipper chrome extension
There was some error creating the note: Could not find clipper service. Please make sure that Joplin is running and that the clipper server is enabled. My attempt to clip a page failed with the following message:
There are a number of possible issues, it is windows afterall, but I have been unable to isolate the issue.
I am able to telnet from the local machine:
It would be great if the Web Clipper extension had a "test connectivity" button and/or some sort of configuration that allowed for a user to specify the address, port, and notebook to save to. Unless the clipper extension wrote directly to the WebDAV target and bypassed the local app.
The text was updated successfully, but these errors were encountered:
That's odd, especially since it seems the service is running. Did you get a message from the firewall to ask you to allow access for Joplin?
Also could you check if you can access the server via http?
Yes indeed, I will make the connectivity status clearer in the next version.
I can't get the webclipper to connect with my Joplin. Using the latest addon to firefox and 1.0.99. I use Firefox nightly. The curl test (above) works from both windows cmd.exe and wsl linux. Here is the debug data from the console window from the time I clicked debug Joplin and then opened the clipper.
Note that the webclipper is started in Joplin on port 41184 but I don't see that port tried in the above log.