Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The provided URL for unscii took me to a domain purchase page so I swapped it for a different one that I found. I tried the unscii-8 font and verified it worked.
I was getting the error
Failed: 500 Can't verify SSL peers without knowing which Certificate Authorities to trust.withLWP::UserAgent. The solution I found was to useMozilla::CA. I looked intoCrypt::SSLeayand it looks like it is only maintained for legacy code. I also saw a couple of mentions ofNet::SSLandIO::Socket::SSLbut both of those seem to not have hostname validation.Dank,
Jordan