New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails to add a feed with Internal Server Error #2579
Comments
I've also been getting errors lately, namely these two:
and for https://blog.joaograssi.com/rss:
The first site seems to somehow have configured their SSL wrong, I don't know what's wrong with the second one though. It seems to be a standard feed generated by Hugo, and there's a title for the whole feed AND for every single post as far as I can tell. News App: 24.0.0 |
Similar issue:
I'm pretty sure my SSL conf is solid, I have a Let's Encrypt certificate and browsers have no problem connecting to my Nextcloud instance. The only problem I can foresee is my cert being pretty recent, so solving this issue might just boil down to updating |
That means your server doesn't know how to verify the certificate that your server is presenting. You'll probably get the same if you |
Thanks for the hint ! Turns out I was actually supplying my apache conf with the standalone cert instead of the full chain. It's interesting how some softwares (such as firefox) are fine with this, while others (like cURL) are not. |
As a rule browsers will forgive almost anything since web developers all seem to follow a different standard. cURL will hold you to the standards though. |
Mozilla also provides it's own trust store for Firefox so it's not necessarily in sync with the OS. |
Explain the Problem
When I add some feeds I get an Internal Server Error. This happens only with some feeds, not all.
Steps to Reproduce
Explain what you did to encounter the issue
System Information
Contents of nextcloud/data/nextcloud.log
Contents of Browser Error Console
Read http://ggnome.com/wiki/Using_The_Browser_Error_Console if you are unsure what to put hereThe text was updated successfully, but these errors were encountered: