I've been getting 403 errors for over a month now when attempting to fetch a stream's playlist link via Link mode - Get the m3u8 from a TwitchTracker/StreamsCharts URL. It happens regardless on whether I use StreamsCharts or Twitch Tracker.
[ERROR tbf::interface] HTTP status client error (403 Forbidden)
EDIT: If I had to guess, this is because we don't support Cloudflare. I pulled the requests I made when browswing to TwitchTracker and StreamsCharts and used them in Bruno to see what could be wrong. I didn't send the cookies and it 403ed, but when I included them it was okay with a 200 status code. I can only assume this is because both sites now rely on CF and send CF cookies with their requests, hence the 403ing.
Possible solutions:
- Headless browsing to help bypass CF
- Replace existing sites with Sullygnome
- You can reference
https://sullygnome.com/api/tables/channeltables/streams/<days>/... but the issue with this is that you would be checking through the returned list of streams to find the matching one with the URL you've been given. This is because they also have CF enabled when visiting the URL of an actual stream instead of just a channel page or their API.
- Not ideal for the implementation, but also, they request not to be scrapped and perhaps this will go against their request (as per their FAQ)
I've been getting 403 errors for over a month now when attempting to fetch a stream's playlist link via
Link mode - Get the m3u8 from a TwitchTracker/StreamsCharts URL. It happens regardless on whether I use StreamsCharts or Twitch Tracker.EDIT: If I had to guess, this is because we don't support Cloudflare. I pulled the requests I made when browswing to TwitchTracker and StreamsCharts and used them in Bruno to see what could be wrong. I didn't send the cookies and it 403ed, but when I included them it was okay with a 200 status code. I can only assume this is because both sites now rely on CF and send CF cookies with their requests, hence the 403ing.
Possible solutions:
https://sullygnome.com/api/tables/channeltables/streams/<days>/...but the issue with this is that you would be checking through the returned list of streams to find the matching one with the URL you've been given. This is because they also have CF enabled when visiting the URL of an actual stream instead of just a channel page or their API.