Talk:VisualEditor/Installation on a shared host

Jump to navigation Jump to search

About this board

Previous discussion was archived at Talk:VisualEditor/Installation on a shared host/Archive 1 on 2015-08-27.

Error at step 19, no composer.lock file

MGFlow58 (talkcontribs)

I have made sure that composer.lock is in .gitignore, however, when using ( git push heroku master ), i get an error saying the following:

remote: -----> PHP app detected                                                                                                                                                                                                                                                
remote:  !     ERROR: No 'composer.lock' found!                                                                                                                                                                                                                                
remote:  !                                                                                                                                                                                                                                                                     
remote:  !     A 'composer.lock' file was not found in your project, but there                                                                                                                                                                                                 
remote:  !     is a 'composer.json' file with dependencies inside 'require'.                                                                                                                                                                                                   
remote:  !                                                                                                                                                                                                                                                                     
remote:  !     The lock file is required in order to guarantee reliable and                                                                                                                                                                                                    
remote:  !     reproducible installation of dependencies across platforms and                                                                                                                                                                                                  
remote:  !     deploys. You must follow the Composer best practice of having                                                                                                                                                                                                   
remote:  !     your lock file under version control in order to deploy. The                                                                                                                                                                                                    
remote:  !     lock file must not be in your '.gitignore'.                                                                                                                                                                                                                     
remote:  !                                                                                                                                                                                                                                                                     
remote:  !     Please perform the following steps locally on your computer to                                                                                                                                                                                                  
remote:  !     resolve this issue before attempting another deploy:                                                                                                                                                                                                            
remote:  !     1) remove 'composer.lock' from file '.gitignore', if present                                                                                                                                                                                                    
remote:  !     2) if no 'composer.lock' exists, run 'composer update'                                                                                                                                                                                                          
remote:  !     3) stage the lock file changes using 'git add composer.lock'                                                                                                                                                                                                    
remote:  !     4) if you edited '.gitignore', also run 'git add .gitignore'                                                                                                                                                                                                    
remote:  !     5) commit the change using 'git commit'                                                                                                                                                                                                                         
remote:  !                                                                                                                                                                                                                                                                     
remote:  !     Please remember to always keep your 'composer.lock' updated in                                                                                                                                                                                                  
remote:  !     lockstep with 'composer.json' to avoid common problems related                                                                                                                                                                                                  
remote:  !     to dependencies during collaboration and deployment.                                                                                                                                                                                                            
remote:  !                                                                                                                                                                                                                                                                     
remote:  !     Please refer to the Composer documentation for further details:                                                                                                                                                                                                 
remote:  !                                                                                                                                                                                                                                    
remote:  !                                                                                                                                                                                                                   

I've tried for a long time to figure out what I am doing wrong, can anyone please help me? I've made sure to do all steps up to this one (except step 11 and 12 as my site is not https, i use godaddy). Additionally, the only file I have named composer is composer.json, but no composer.lock. Any help would be greatly appreciated! (talkcontribs)

same problem here :(

MGFlow58 (talkcontribs)

I'm kind of upset because it seems like a lot of extensions have trouble on a shared host, with this one it looked like I was actually getting somewhere but i feel the tutorial is outdated

NH35 (talkcontribs)

I generated that file (composer.lock) using composer. Everything was successful but I have error "Forbidden You don't have permission to access / on this server.".

What i changed in original instruction? I removed composer.lock line in config.yaml

My log file https://justpaste(dot)it/63ogi (talkcontribs)

I have the exact same problem. I managed to resolve the issue with "composer.lock", but unfortunately when I load the site, I receive the "Forbidden" error. Any idea?

Br shadow (talkcontribs)
Reply to "Error at step 19, no composer.lock file" (talkcontribs)

When i try to open the web app i get this

403 Forbidden


You don't have permission to access / on this server.

Logs :

[Tue Apr 02 17:45:11.600374 2019] [autoindex:error] [pid 139:tid 140463323920128] [client] AH01276: Cannot serve directory /app/: No matching DirectoryIndex (index.php,index.html,index.htm) found, and server-generated directory index forbidden by Options directive

Thanks in advance

NH35 (talkcontribs)
Reply to "Step 21"
NH35 (talkcontribs)

(RECOMMENDED) Then you need a config file to make Parsoid to work through HTTPS. Create file under


What if my hosting does not allow it (shared hosting)? (talkcontribs)

I managed after a hard time to get VE work with the help of heroku.

But when it's https I get the same error , can anyone please explain in details how to get the config file for https work ? ( I mean step 11 & 12 ) cuz I use cloudflare , where to create file ? ( the etc thing ? ) and how to get cert key and I am using cloudflare ?.

AhmadF.Cheema (talkcontribs) (talkcontribs)

Yeah I am talking about that part of the documentation , I don't understand how to get cert key and what etc file on the host or ? I am using cloudflare for ssl.

Qd p2 (talkcontribs)

You can change url app Heroku "https://..." to "http://.." (pass step 11 & 12 )

Qd p2 (talkcontribs)


'url' => '',

'domain' => 'localhost',

'prefix' => 'your wiki prefix',

'forwardCookies' => true

Reply to "https problem" (talkcontribs)

why the H ! it's bee, a year and a half without success !


apierror-visualeditor-docserver-http: HTTP 404

Jer Hughes (talkcontribs)

I followed the steps, and can even verify "Welcome to the Parsoid web service" is displayed (Step 20), but I get "Error loading data from server: apierror-visualeditor-docserver-http: HTTP 404" after I complete Step 21 and try to edit a page.

The directions say to use this format:

// URL to the Parsoid instance
'url' => '',
// Parsoid "domain", see below (optional)
'domain' => 'localhost',
// Parsoid "prefix", see below (optional)
'prefix' => 'your wiki prefix',

I tried:

'url' => '',
//'domain' => 'localhost',
//'prefix' => 'your wiki prefix',

'url' => '',
'domain' => 'localhost',
'prefix' => 'your wiki prefix',

'url' => '',
'domain' => '',
'prefix' => 'https',

'url' => '',
'domain' => '',
'prefix' => 'https',

Can someone elaborate on what these values are? And this page provides instructions for setting Parsoid up on Heroku, why would the Parsoid "domain" ever be 'localhost'? (talkcontribs)

I have the exact same problem with my wiki.

Creating a page is ok, though. (talkcontribs)

the same problem , I am so so so tired with it for 3 months :/ (talkcontribs)

I'm tired about this same problem too :( (talkcontribs)

Same for me...

John Harry Lau (talkcontribs)

Maybe need to install RESTBase

John Harry Lau (talkcontribs)
Reply to "apierror-visualeditor-docserver-http: HTTP 404"

Alternative Step 11 if "Login is currently incompatible with git bash/Cygwin/MinGW"

Wikidelo (talkcontribs)

When I tried heroku login I got this message:

Login is currently incompatible with git bash/Cygwin/MinGW

Googled it and tried

winpty heroku login

Worked for me. I hope it works for you too, if you have the same problem.

Reply to "Alternative Step 11 if "Login is currently incompatible with git bash/Cygwin/MinGW"" (talkcontribs)

Hi. VisualEditor is moving in my mediawiki... but how to add second mediawiki??

config.yaml (line 39-42)

# the URL of you mediawiki API endpoint.

uri: ''

uri: ''

# the "domain" is used for communication wiht Visual Editor

it's not moving second Mediawiki...

please tell me how to add...second api...

Reply to "How to add second Mediawiki ?" (talkcontribs)

Hi. What does  from inside the parsoid folder means? Should I type the commands in the command line?

AhmadF.Cheema (talkcontribs)

Yes, those git commands need to be run from the command line.

In your command prompt, run cd C:\parsoid\ after which, run the git commands.

OR a quick shortcut to open a command prompt inside a desired folder is to open that folder in Windows/File Explorer, type and enter cmd in the address bar of File Explorer, and it will automatically open a command prompt for that folder. (talkcontribs)

@AhmadF.Cheema, thanks for answering. When I try to run those commands (git init, add . and commit) it shows: Your branch is ahead of 'origin/master' by 1 commit.

AhmadF.Cheema (talkcontribs)

If I remember correctly, this is the expected behaviour. You should now try to follow the next two steps. (talkcontribs)

@AhmadF.Cheema: No, because after that I don't get to see Aborting commit due to empty commit message. Am I doing something wrong?

AhmadF.Cheema (talkcontribs)

Taking another look at the steps, you shouldn't be getting the "branch is ahead of 'origin/master' by 1 commit" message, since the previous steps did not involve any git commit command.

I think you should try from the beginning, you appear to have made some mistake in following the instructions.

Application error (logs provided) - please help

2 (talkcontribs)

Hi. I've followed instructions as much as I could, but I thing I've failed somewhere cause at the end I get "Application Error". Here is the log from the Heroku:

2017-11-07T10:21:36.379342+00:00 heroku[web.1]: State changed from crashed to starting
2017-11-07T10:21:39.142540+00:00 heroku[web.1]: Starting process with command `npm start`
2017-11-07T10:21:41.481200+00:00 app[web.1]: 
2017-11-07T10:21:41.481214+00:00 app[web.1]: > parsoid@0.8.0 start /app
2017-11-07T10:21:41.481215+00:00 app[web.1]: > service-runner
2017-11-07T10:21:41.481216+00:00 app[web.1]: 
2017-11-07T10:21:42.091411+00:00 app[web.1]: Error while reading config file: Error: ENOENT: no such file or directory, open '/app/config.yaml'
2017-11-07T10:21:42.105060+00:00 app[web.1]: 
2017-11-07T10:21:42.118185+00:00 app[web.1]: npm ERR! Linux 3.13.0-133-generic
2017-11-07T10:21:42.118757+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2017-11-07T10:21:42.119037+00:00 app[web.1]: npm ERR! node v6.11.5
2017-11-07T10:21:42.119306+00:00 app[web.1]: npm ERR! npm  v3.10.10
2017-11-07T10:21:42.119576+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2017-11-07T10:21:42.119795+00:00 app[web.1]: npm ERR! parsoid@0.8.0 start: `service-runner`
2017-11-07T10:21:42.119996+00:00 app[web.1]: npm ERR! Exit status 1
2017-11-07T10:21:42.120189+00:00 app[web.1]: npm ERR! 
2017-11-07T10:21:42.120345+00:00 app[web.1]: npm ERR! Failed at the parsoid@0.8.0 start script 'service-runner'.
2017-11-07T10:21:42.120499+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed.
2017-11-07T10:21:42.120653+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the parsoid package,
2017-11-07T10:21:42.120801+00:00 app[web.1]: npm ERR! not with npm itself.
2017-11-07T10:21:42.120970+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2017-11-07T10:21:42.121271+00:00 app[web.1]: npm ERR!     service-runner
2017-11-07T10:21:42.121489+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2017-11-07T10:21:42.121689+00:00 app[web.1]: npm ERR!     npm bugs parsoid
2017-11-07T10:21:42.121885+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2017-11-07T10:21:42.122079+00:00 app[web.1]: npm ERR!     npm owner ls parsoid
2017-11-07T10:21:42.122267+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2017-11-07T10:21:42.127673+00:00 app[web.1]: 
2017-11-07T10:21:42.127966+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2017-11-07T10:21:42.128142+00:00 app[web.1]: npm ERR!     /app/npm-debug.log
2017-11-07T10:21:42.251124+00:00 heroku[web.1]: State changed from starting to crashed
2017-11-07T10:21:42.236950+00:00 heroku[web.1]: Process exited with status 1
NH35 (talkcontribs)