[Index Manager] TypeError: c.map is not a function

[saintusmarcus]

Environment

Docker

Version

0.15.3

Describe the problem

The index manager (and the calendar too I guess, might be related) were working perfectly fine for a day after installing homarr. Shortly after, index manager started having an infinite loading animation, throwing the following error in the console

[
  {
    "error": {
      "json": {
        "message": "Hostname/IP does not match certificate's altnames: IP: 192.168.1.100 is not in the cert's list: ",
        "code": -32603,
        "data": {
          "code": "INTERNAL_SERVER_ERROR",
          "httpStatus": 500,
          "path": "indexerManager.indexers",
          "zodError": null
        }
      }
    }
  },
  {
    "error": {
      "json": {
        "message": "Hostname/IP does not match certificate's altnames: IP: 192.168.1.100 is not in the cert's list: ",
        "code": -32603,
        "data": {
          "code": "INTERNAL_SERVER_ERROR",
          "httpStatus": 500,
          "path": "indexerManager.statuses",
          "zodError": null
        }
      }
    }
  }
]

After adding

    environment:
      NODE_TLS_REJECT_UNAUTHORIZED: 0

to the homarr config, the widget turned pink and is reporting

TypeError: c.map is not a function

Logs

No response

Context

No response

Please tick the boxes

• [X] I confirm that I attached the proper logs
• [X] I've read the docs
• [X] I've checked for duplicate issues
• [X] I've tried to debug myself

[github-actions[bot]]

Hi 👋. Thank you for submitting your first issue to Homarr. Please ensure that you've provided all nessesary information. You can use the three dots > Edit button to update your post with additional images and information. Depending on the current volume of requests, the team should get in conact with you shortly.

[SeDemal]

Although there is an improper amount of error handling from what I can see, your issue should be fixable. There an error because you cannot map something that isn't an array, which would be the case if what's returned is not one. And it would not be one only if the api call wasn't returning properly.

From what I can gather from the info here, you might be having issue with networking between your apps. Seeing as you do get an error page, either your prowlarr's api handling has crashed (I'm guessing you checked that already but a restart wouldn't hurt) or you may be using a reverse proxy that can't route to the app? not quite sure there.

[saintusmarcus]

You're 100% correct, it was an issue with my nginx reverse proxy. Swapping https://local.ip/app to http://local.ip:port/app fixed the issue. Thanks!