hey 5I have hosted a FreshRSS container, everythings working good but I cant get the API to work with tailscale or cloudflare tunnels on any app, be it Reeder or net news wire. (fever or google)
Is there anything I can do to force the API to publish on the tailscale IP of the device for freshrss to work with mobile apps? am I doing something wrong?
Or is there any other rss containers that I can host to get rss onto a mobile app utilizing tailscale? I can’t open any ports and as such am forced to utilize tailscale or cloudflare tunnels. help/suggestions appreciated. Thanks
I host a RSSHub container that I route through a Cloudflare tunnel to a subdomain. It works like a charm in multiple different apps I use.
Yea I was able to get it to work with cloudflare tunnels. The api needs a correct domain and not an IP once I realized that it clicked for me. posting it as a comment above for others to find if they ever want to.
I set this up a week ago. Not sure if this is the best practice approach but it’s been working fine for me.
In FreshRSS my API url is just the default local address. 192.168… whatever it may be. Tailscale assigns an specific address to each machine, so on my RSS client (Reeder) I use the server’s Tailscale address (plus internal port and /api/). As long as Tailscale is active on your server, and active on your client, any traffic to a Tailscale address should be routed via Tailscale automatically.
Happy to provide screenshots via DM if this doesn’t make sense. Also happy to change my setup if someone tells me I could be doing things better.
I haven’t tried with an app yet I just connect to the tail scale ip of freshrss and view it in a browser. I’ll try and app and see if there’s issues.
I’ve being dealing recently with issues related to DNS resolution in docker containers. Are you using by any chance pihole as well?
for anyone looking for the answer. I was able to get it working see below: I was able to get tailscale working after reading many comments it all started to click in my mind and I realized it needed a full url say blabla.local/api… so i was able to adguard home add a dns entry for blabla.local using my tailscale device ip. Reverse proxy on the device aiming the tailscale ip to blabla with the port. Then i found a comment in github comments of old issues the dev mentioned in the data folder of the config files you can change the ip that the api listens so i just changed from local ip to tailscale ip refreshed and it all worked. With no issue to my home browser but api working with tailscale on mobile.
damn, that seems awfully complicated just to connect to your RSS reader hahah
