Can you review the server error logs to find the causes of the errors?

You can use a network sniffer (e.g. wireshark) to capture the traffic between your system and the server. You might find some clues by comparing successful and failed accesses. Even with HTTPS, not everything is encrypted.

There are tools that might allow you to inspect the HTTPS exchange with the server. If Firefox browser works, you might be able to use some of its debugging features to find out what is happening. Otherwise, there are proxy servers which might allow you to inspect the exchange (e.g. fiddler. Ultimately, you could brute force decrypt the traffic, thought this might take some time.

Might cookies be required by the server?

In reply to Re: LWP - 500 Internal Error by ig
in thread LWP - 500 Internal Error by oalvi

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.