Can't add the feed

[m0nhawk]

When I'm trying to add this feed: https://www.perell.com/blog?format=rss, I get the error:

We couldn't find that feed. Try again.

It's accessible from the Docker container and I'm not sure how to further debug and fix it:

$ docker-compose exec stringer curl https://www.perell.com/blog?format=rss
<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Site-Server v6.0.0-26812-26812 (http://www.squarespace.com) on Sat, 07 Nov 2020 00:11:17 GMT
--><rss ...

Will be thankful for pointers on this one.

[MattiaDucci]

Same problem for me...

[guidopetri]

Upgrading to the latest versions of the dependency gems worked for me. Steps are:

• log in as stringer user
• update rbenv (cd ~/.rbenv; git pull; cd plugins/ruby-build; git pull; cd ~)
• rbenv rehash
• cd ~/stringer; git pull
• gem update bundler
• bundle upgrade
• restart stringer (if via systemd, then logout and sudo systemctl restart stringer.target; if running in foreground then just Ctrl+C and restart with foreman)

In particular, I was adding a different Squarespace RSS feed, which was giving me the same error. Your feed works for me too now.

[guidopetri]

@mockdeep I think this can be closed once one of the other two users confirm it works for them.

[mockdeep]

Hi @m0nhawk @MattiaDucci are you still seeing this issue?

[brentcetinich]

The problem happens for me too, but for a different feed. However they both have TLS certificate issued by lets encrypt (Chain looks like this (ISRG Root X1 --> R3)

It seems that the new lets encrypt CA is not in the trust store.

The error I get is

stringer | OpenSSL::SSL::SSLError error occurred with: https://perell.com/feed/': SSL_connect returned=1 errno=0 state=error: certificate verify failed`

I am running on the docker image and I can't seem to find where .rbenv is.

[mockdeep]

@brentcetinich I'm not sure I'll get a chance to look into this soon, but if you manage to make any progress I'll be happy to look over a PR. We don't install rbenv in the docker image, so you'll need to set it up yourself, or another Ruby version manager.