**jazeckel** wrote:

(In reply to C. Scott Ananian from comment #16)
> I'm guessing that one of these is prohibiting anonymous access to the API. 
> I bet it's not actually the case that it works when you use the server name,
> I bet that somehow you're actually accessing the wrong wiki in that case. 
> I'm not a mediawiki permissions expert though, so take what I say with a
> grain of salt.

Yes, this is exactly what happens -- it loads the content from the wrong wiki.

> If you are mucking with permissions, this link may be useful:
> https://www.mediawiki.org/wiki/Extension:
> VisualEditor#Linking_with_Parsoid_in_private_wikis

I had already set $wgVisualEditorParsoidForwardCookies = true as instructed in that portion.  I didn't uncomment the line about session cacheing because it didn't seem to make a difference.

> Yes, the 'localhost' part here has to match the string you set 
> $wgVisualEditorParsoidPrefix to.

Okay, thanks for letting me know that.  It wasn't clear from the installation/configuration instructions.

(In reply to C. Scott Ananian from comment #18)
> In particular, one running parsoid can service multiple different
> mediawikis.  They are distinguished by the $wgVisualEditorParsoidPrefix and
> corresponding localsettings.js.  For example, you should be able to visit
> your running parsoid instance on http://localhost:8080 (or whatever port you
> used) and then get different pages for:
> 
> http://localhost:8080/enwiki/Main_Page (links to wikipedia using 'enwiki'
> prefix)
> http://localhost:8080/localhost/Main_Page
> http://localhost:8080/foo/Main_Page
> 
> given
> 
> parsoidConfig.setInterwiki( 'localhost', 'some api endpoint' );
> parsoidConfig.setInterwiki( 'foo', 'some different api endpoint' );
> 
> Our docs could probably explain this better.  Suggestions welcome.

Thanks, that explains some more.  I have set them both to "auc" and now it's not loading data from the wrong wiki anymore, but it's timing out again.  Perhaps there is some other detail of configuration for a private wiki that is causing a problem.  Can I go into Parsoid's code and hard code a username and password and make a private account just for Parsoid to resolve this?