Both sides.

The script you are using to fetch data from the server expects JSON back, and croaks if it does not get it.
That part could be improved with Error/Warning detection and handling.

The server side code that runs on the hosting service is what provides a response to a request from your clinet script.
That should also behave itself when JSON is requested, and provide a JSON-only response.
Apparently, it is not doing so in this case - it is sending an HTML style warning message.
You can blame (lack of) documentation for this, and/or poor design/coding/testing.

        ...Disinformation is not as good as datinformation.               Don't document the program; program the document.

In reply to Re^3: Malformed JSON Error Piwigo by NetWallah
in thread Malformed JSON Error Piwigo by kiteboywales

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.