Curl error 92 on trying to add feed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
The report gives a reproducible feed URL and the cURL error 92 response, but no code path. Start by reproducing the add-feed flow against https://www.cbc.ca/webfeed/rss/rss-topstories and compare it with the working CLI request, then trace the app's feed-fetching HTTP client and its HTTP/2/cURL handling. Done means the feed can be added, or the fetcher falls back cleanly instead of surfacing a transport error.
Written by the indexing model from the issue text.
Description
IMPORTANT
Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)
- I have read the CONTRIBUTING.md and followed the provided tips
- I accept that the issue will be closed without comment if I do not check here
- I accept that the issue will be closed without comment if I do not fill out all items in the issue template.
Explain the Problem
When trying to add https://www.cbc.ca/webfeed/rss/rss-topstories the following error is displayed:
Transport error for https://www.cbc.ca/webfeed/rss/rss-topstories: cURL error 92: HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2) (see https://curl.se/libcurl/c/libcurl-errors.html) for https://www.cbc.ca/webfeed/rss/rss-topstories
Note that from the command line this seems to work correctly.
~$ curl -v --http2 https://www.cbc.ca/webfeed/rss/rss-topstories
Steps to Reproduce
Attempt to add https://www.cbc.ca/webfeed/rss/rss-topstories
System Information
- News app version: 28.7.0
- Nextcloud version: 34.0.5
- Cron type: (system cron/python updater/...) cron
- PHP version: 8.2.35
- Database and version: Mariadb 10.5
- Browser and version: Firefox Linux 159
- OS and version: Debian 12.15
- Dominant language
- PHP
- Stars
- 1k
- Forks
- 200
- Avg merge
- 20h 28m
- Merged PRs (30d)
- 32
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nextcloud/news
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
replace mkdocs with somethingMay be free again @Grotax claimed this 95 days ago, and no pull request is open. Open
nextcloud/news#3887 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
bug help wanted upstream
Difficulty 3/5 1-2 days Newbie friendliness 58/100
nextcloud/news#3840 · 1 comment ·
Maintainers usually reply within 1 day
-
bug upstream
Difficulty 3/5 1-2 days Newbie friendliness 52/100
nextcloud/news#3822 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
0. Needs triage 35-feedback bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 72/100
wpgenius/stackfolio#22 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Automattic/static-site-importer#3024 ·
Maintainers usually reply within 1 day
-
[6.0]: Uncaught TypeError: can't access property "value", event.chart.scales.x.ticks[4] is undefinedOpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
phpmyadmin/phpmyadmin#20626 ·
Maintainers usually reply within 1 day