Dashboard RSS feeds 403

We are aware of an issue affecting machine retrieval of all content hosted at the main websites of freepbx.org and asterisk.org, including the RSS feeds used by default in the FreePBX Dashboard. You can test this yourself by trying wget on the command line:

wget https://www.freepbx.org/rss.xml
wget https://www.asterisk.org/blog/rss

…both of which are currently returning 403 for most (all ?) users. The working theory at this point is that the issue is related to the upstream global Cloudflare outage that started earlier today.

It works if you paste it into your browser… It has to be something deeper

1 Like

One of the main features of Cloudflare seems to be their check for bots. Maybe it was turned on for those URLs, which are operated by bots, albeit friendly ones.

2 Likes

That’s possible, but I find it highly unlikely it’s related to Cloudflare as it started after Cloudflare recovery, and there are no reports of any other issues with them right now

Well, Sangoma uses Cloudflare in front of those domains, and my RSS feeds are still broken in FreePBX Dashboard. How about y’alls ?
Screenshot_2025-11-19_09-58-09

Yeah same for me. I assume you don’t have access to manage the domains? If not- are the people who WOULD know aware?

Yes, this is being looked at internally at Sangoma.

Some ideas include:

  • special Cloudflare exceptions for the default feed URLs
  • new feeds-only subdomain that sits outside Cloudflare (requires changes to existing FreePBX systems)
  • waiting it out until Cloudflare addresses further the issue e.g. refreshing their trusted IP lists

I think firewall exceptions can be made with page rules

Wait… Does Sangoma have any enterprise Cloudflare support plan? That could come in handy.

Also another clue is that when pasting it into the browser it downloads a file with a random filename althought its contents are correct. I feel like I have a vague memory of it used to just show it in-browser.

Sangoma definitely has some Cloudflare plans, and it looks like this issue is resolved for some users. Putting a patch in shortly to update the default feeds to the following:

https://www.freepbx.org/feed/
https://www.asterisk.org/blog/feed/
1 Like

Can confirm issue is resolved here, Even without the FreePBX rss patch