You get much higher quality answers if you enable us to reproduce the problem (sscce, mcve). As the question stands now, only guessing is possible. Please edit it to add the relevant details.
files not having the correct text encoding
PEM files in text form are ASCII, that can't be the problem.
just fine using "openssl
The Perl code might not use the same library as the command-line tool, please verify.
› openssl version › perl -mNet::SSLeay -E "say for Net::SSLeay->VERSION, sprintf q(%X), +Net::SSLeay::SSLeay"
If the certificate is in actual use, https://github.com/noxxi/p5-ssl-tools can be helpful.

What is the opinion of gnutls about the file?

› certtool -i < somefile.pem

In reply to Re: RSA.xs:194: OpenSSL error: no start line by daxim
in thread RSA.xs:194: OpenSSL error: no start line by cinergi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.