Failed to fetch feed
Failed to fetch feed "http://www.sitename.com/feed/". The resource could not be retrieved because of a client error with code 400
Server returned 36743 characters, of which 150 are below:
...
Cause
The server that hosts the RSS feed may be configured to check the request for a user agent (a piece of text that identifies the kind of software that is making the request) to check what kind of browser you are using. Since WP RSS Aggregator is not a browser, the server can get confused and reply with the above error.
Solution
As of version 4.8.2, WP RSS Aggregator will send a Chrome User Agent. This results in servers identifying WP RSS Aggregator as a Chrome browser.
If you are using a version older than 4.8.2, we encourage you to update to the latest version and set the Feed Request User Agent to empty. Additionally, you should also make sure that your individual feeds do not override this setting.
If you are using version 4.8.2 or later, you can get in touch with the owner of the server where the RSS feed is hosted and ask them why the request is being rejected.
We do not encourage changing the User Agent setting to try and bypass any security mechanisms that the server may have in place. The server reserves the right to block you or WP RSS Aggregator, and we should respect that. Changing the User Agent to circumvent such measures may lead to legal action being taken against you. WP RSS Aggregator will not be held liable for misuse of the User Agent setting.
Alternative Error
Failed to fetch feed “http://www.somesite.com/rss”. The resource could not be retrieved because of a client error with code 404.
Server returned 0 characters:
...
Cause
If you see an error similar to the one above and you are able to access the feed source in the browser, then it is possible that the server is responding in an unexpected way to the user-agent that is sent with each feed request.
Solution
To fix this, try using the user-agent sent by your browser. Click here to find out your browser's current user agent.