News app ignoring port in nc http proxy configuration

[Szwendacz99]

IMPORTANT

Read and tick the following checkbox after you have created the issue or place an x inside the brackets ;)

• [ x] I have read the CONTRIBUTING.md and followed the provided tips
• [x ] I accept that the issue will be closed without comment if I do not check here
• [ x] 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

My nextcloud is using forward http proxy to reach public internet. The proxy address together with tcp port is specified both in HTTPS_PROXY env variable and in config.php. The proxy uses http, and port is 80 so at first I was not specifying port, as it is the default for protocol, but then whole Nextcloud had trouble connecting to the public https, with error that it cannot connect to proxy with port 1080. I have no idea where it got that port from, but when I specified the port 80 in configuration, almost everything started to work, and use the proxy correctly. Everything except News app, which still tries to use port 1080 in cron and fails. I am not sure if this is problem with News app or with cron, but I dont see any other Nextclouds components having the issue right now. My whole setup is based on custom container images, running in kubernetes.

Steps to Reproduce

Explain what you did to encounter the issue

1. Setup http forward proxy working on http and port 80
2. Configure the proxy address in nextcloud, specifying port
3. Configure some rss news
4. Wait until warnings appear in log about being unable to connect to the proxy address with port 1080

System Information

• News app version: 25.1.0
• Nextcloud version: 30.0.4
• Cron type: "system cron"
• PHP version: 8.3.14
• Database and version: Postgres 17.2
• Browser and version:
• OS and version:

Contents of nextcloud/data/nextcloud.log

Paste output here

Contents of Browser Error Console

Read http://ggnome.com/wiki/Using_The_Browser_Error_Console if you are unsure what to put here

Paste output here

[wofferl]

tcp/1080 is the default socks proxy port
Did you at first only use ip without http://?

The setting normally looks like:
'proxy' => 'http://192.168.0.1:8080',

If you have set it correct, it's maybe a caching problem. Have you tried restart your web server.

[Szwendacz99]

my config is:
'proxy' => 'http://<k8s-cluster-internal-domain>:80'

Restarting pod that contains httpd, php and cron loop does not help. Not sure what cache could be cleaned there and how.