spec123 A possible fix is ready, but it hasn't been deployed yet. I will post an update when we have more information or when this is solved.

    5 days later

    For those that have a software engineering background I have a workaround that allows the littlstar app to load the premium feed.

    1. Save a copy of the XML from the feed URL
    2. Use 'npm/npx serve' to serve this file from a local directory.
    3. Add the feed to littlstar using your private IP (eg. 192.168.0.2:5000/premium.xml)
    4. The feed will load successfully.

    I was surprised by this, there I was all ready to modify the XML and figure out the root cause... As it turns out, the feed is valid and not malformed. I'm guessing that there is a timeout issue when connecting to the actual SLR feed and the app gives up.

      SamSuppVR It's unlikely to help them guys really. This might:

      It does provide the insight that the feed generated in live is always valid when loaded from a local machine and littlstar is consistently able to process it every time.

      I suspect they are seeing the same behaviour in dev (ie. It just works for them) which is why it was missed and is hard as f**k to diagnose.

      I would suspect either:
      1. That your S3 bucket, Cloudfront or other CDN is encoding this in an odd way, or adding a HTTP header that littlstar doesn't like.

      1. There is some kind of performance issue with the request to the feed on the SLR side and littlstar actually times out during the request. Also explains why the free one works and a few weeks ago the issue was intermittent for the premium one.

      If I could be arsed I'd have wireshark set up on the network between the PS4 and and SLR environment and inspect and compare the HTTP request / responses between free/local/live.

      Also, if they need help testing with a real littlstar premium account give me a shout..

          SamSuppVR It's unlikely to help them guys really.

          This might:

          My workaround does provide the insight that the feed generated in prod is always valid when loaded from a local machine and littlstar is consistently able to process it every time.

          I suspect they already know that and are seeing the same behaviour in dev (ie. It just works for them) which is why it was missed and is hard as f**k to diagnose.

          I would suspect either:

          • That your S3 bucket, Cloudfront or other CDN is encoding this in an odd way, or adding a HTTP header that littlstar doesn't like.
          • That there is some kind of performance issue with the request to the feed on the SLR side and littlstar actually times out during the request. Also explains why the free one works and a few weeks ago the issue was intermittent for the premium one.

          If I could be arsed I'd have wireshark set up on the network between the PS4 and and SLR environment and inspect and compare the HTTP request/ HTTP response between free/premium and local/prod

          Also, if they need help testing with a real littlstar premium account give me a shout..

              2 months later

              this feature is the only reason i subscribed, and it's significantly more busted than these nuts

              a month later
              9 months later

              metrum666 Before loading the RSS feed in RAD, load it in a normal browser as the (custom) feed still has to be generated. RAD only reads the feed.