Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

VLT Tool: The server localhost failed to respond

Avatar

Level 1

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.

1 Accepted Solution

Avatar

Correct answer by
Level 10

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

View solution in original post

5 Replies

Avatar

Level 10

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

Avatar

Level 1

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

Avatar

Level 10

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

Avatar

Correct answer by
Level 10

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