Jump to content

Talk:Citoid/2020

Add topic
From mediawiki.org

Previous archives are at /Archive 1

"could not make a citation for you" every time

[edit]

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.


Hi. I'm getting this error with Citoid and I can't figure out what's wrong. I checked the instructions on the extension page and the suggestions didn't change anything, except the API says:

{

   "batchcomplete": "",
   "pages": {}


}
Reception123 (talk) 06:33, 4 April 2020 (UTC)Reply

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

How can the citoid service use https without referencing SSL certificates in the node server?

[edit]

My wiki uses https. Thus, it seems that I need to set wgCitoidServiceUrl to also use https.

When I use https $wgCitoidServiceUrl, I get an ssl error. If I run "curl hxxps://localhost:1970/?doc" on the server, I get:

curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number

Looking into the app.js code, it doesn't look like it has any functionality to use https, so I don't understand how this can possibly work. If I modify app.js to create a server using require('https') instead of 'http', and pass an additional parameter to my certificate and key when createServer() is called, then it works fine.

Surely I must be missing something since I'm sure many implementations have this working over https. Could anyone help clarify?

Also, it's a bit unclear in the instructions, but I assume that $wgCitoidServiceUrl needs to be set to use the actual server name and not localhost, since the connection seems to be made client-side (e.g. $wgCitoidServiceUrl = "hxxps://mywiki.org:1970/api")?

Thanks for any advice in advance. Chrishel (talk) 02:00, 21 April 2020 (UTC)Reply

You might get more help if you copy this post to the MediaWiki Project:Support desk. Whatamidoing (WMF) (talk) 23:01, 26 April 2020 (UTC)Reply
Just to follow up with this, I did get this working by manually setting up stunnel to open a new https port to tunnel requests to citoid over http. Here's the gist of what I did:
Install stunnel
sudo apt-get install stunnel4
Create a stunnel configuration file for citoid:
sudo nano /etc/stunnel/citoid.conf
Add the following block to the end of the file:
cert = /path/to/certificates/fullchain.pem
key = /path/to/certificates/privkey.pem
[citoid]
accept = 1971
connect = 1970
Restart stunnel
sudo systemctl restart stunnel4.service
(Optionally) configure stunnel to start automatically
sudo nano /etc/default/stunnel4
Add new line with ENABLED=1 above line with FILES directive. Save and close the file. Chrishel (talk) 03:26, 29 October 2020 (UTC)Reply
I tried in your way but in the site at "localhost:1971/?doc", site cannot GET anyway. How can I solve that problem? 1.229.241.11 (talk) 20:25, 28 November 2020 (UTC)Reply

Are there any easier ways of adding sources to Citoid/Zotero?

[edit]

Hello folks,

Looking at Citoid#Troubleshooting the citoid service, are there any other ways editors could contribute appropriate citation information to integrate into Citoid? Pushing non-technical contributors to this isn't likely to get many results... :-) Ed [talk] [en:majestic titan] 05:34, 25 September 2020 (UTC)Reply

The metadata is scraped either directly from the website or from an external database (i.e. crossref) so it is indeed quite technical. We do have a few community members who contribute to the zotero repository but as far as I know it's in the singe digits :). You can report problems either on Phabricator (https://phabricator.wikimedia.org/tag/citoid/) or directly to the translators repo, but handling of reported issues is quite slow. Mvolz (WMF) (talk) 09:04, 25 September 2020 (UTC)Reply