VLT Tool: The server localhost failed to respond | Community
Skip to main content
December 18, 2015
Solved

VLT Tool: The server localhost failed to respond

  • December 18, 2015
  • 5 replies
  • 2181 views

Hi

I've been trying to install the VLT tool on OSX El Capitan.  I have actually successfully installed the tool. But when I try to checkout the repository I get the following error:

 

$ vlt --credentials admin:admin co --force http://localhost:4502/crx
Checkout http://localhost:4502/crx/server/-/jcr:root/ with local files using root at /Users/charlievaughan2/Documents/Work/Pearson/pearson_git/jcr_root
Connecting via JCR remoting to http://localhost:4502/crx/server
[ERROR] checkout: org.apache.jackrabbit.vault.vlt.VltException: Unable to mount filesystem
caused by: javax.jcr.RepositoryException: org.apache.commons.httpclient.NoHttpResponseException: The server localhost failed to respond
caused by: org.apache.commons.httpclient.NoHttpResponseException: The server localhost failed to respond

 

Part of the reason I was installing the VLT tool was because the AEM Brackets Extension for the Brackets IDE is also not syncing for me. See my bug report on https://github.com/Adobe-Marketing-Cloud/aem-sightly-brackets-extension/issues/66 .

I'm thinking these two issues could be related where something on the AEM instance is preventing the two tools from connecting to the server?

I'm not sure what I can do to diagnose this further. Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

sounds like you are using custom authentication handler. please disable them & verify. Or firewall restriction try http://www.aemstuff.com/#article971

5 replies

smacdonald2008
December 18, 2015

Looks like the tool is not really supported on this OS. See this other community discussion for details.  

December 18, 2015

If you read the blog post linked to in the discussion, the problems seem to be limited to Audition CC and are now fixed.

smacdonald2008
December 18, 2015

This may be a new bug  - i asked support to look at this thread. 

Sham_HC
Sham_HCAccepted solution
December 18, 2015

sounds like you are using custom authentication handler. please disable them & verify. Or firewall restriction try http://www.aemstuff.com/#article971

January 7, 2016

This is still an issue.