ModuleManager fails with ambiguous error on systems without LWP SSL support #154

SaberUK opened this Issue May 28, 2012 · 3 comments


None yet
4 participants

SaberUK commented May 28, 2012

On systems without LWP SSL support, ModuleManager fails with the following error:

Could not retrieve

I suspect that this error is caused by lack of SSL support. I also suspect that to fix this error, Crypt::SSLeay is required.

Not using SSL doesn't seem to be an option as GitHub appears to force SSL.


attilamolnar commented Jul 26, 2012

yeah, github forces SSL so we could update the error message for now to give a hint about missing LWP SSL support

Syloq commented Sep 27, 2012

Installing the Debian package libcrypt-ssleay-perl fixed the issue for Debian installs. So what ever the equivalent is for other distros would be helpful.


Shawn-Smith commented Sep 27, 2012

It would probably be easier to just remove the module manager and make a third-party folder that submodules from the inspircd-extras repo.

satmd added a commit to satmd/inspircd that referenced this issue Jun 1, 2014

Fix ModuleManager failing when:
- LWP::Simple is not installed.
- Crypt::SSLeay or IO::Socket::SSL are not installed.

This fixes #154.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment