Problem subscribing to feed on custom port

[alexei]

Hi I’m trying to subscribe to an atom feed (a self-hosted wallabag instance), the feed url is of the form

xxx//media.example.org:8282/feed/alexei/0/unread

(I’ve replaced ‘http:’ with ‘xxx’ since new users can’t post links apparently

When I try and subscribe I get the error:

Couldn’t download the specified URL: ; 7 Failed to connect to media.example.org port 443: Connection refused

why is tt-rss trying to connect to port 443? It should be connecting to 8282.

doing curl -I xxx//media.example.org:8282/feed/alexei/0/unread gives

HTTP/1.1 200 OK
Server: nginx
Content-Type: application/atom+xml
Connection: keep-alive
Cache-Control: no-cache, private
Date: Fri, 15 Jan 2021 10:56:00 GMT

and curl xxx//media.example.org:8282/feed/alexei/0/unread returns the feed so the wallabag instance is doing what it should, it seems and error on tt-rss side

[fox]

you won’t be able to use non-standard ports.

https://community.tt-rss.org/t/rss-bridge-with-tt-rss/3866

in general its a good idea to search for a similar problem before making a new thread.

[alexei]

Thanks, I had dismissed that thread as it was talking mainly about rss-bridge. The following is more helpful for anybody else searching on why custom ports are disallowed:

https://community.tt-rss.org/t/heads-up-several-vulnerabilities-fixed/3799