Mailtrain issue with RSS feed from Wordpress, both on the same Cloudron server
-
@eggeek you can't update this on your own, as the path in the container is read only. In the end this requires either an app update, and updated base image or (and this would have other benefits) just let the containers mount
/etc/sslfrom the host.@fbartels Thanks for your response. I'm not sure if it's related to that root certificate expiration, I just think it's linked because it was working begining of last week and today I see this error message.
I just don't know how to mount that local folder on this instance, do you know where I can find any documentation on that ?
-
@fbartels Thanks for your response. I'm not sure if it's related to that root certificate expiration, I just think it's linked because it was working begining of last week and today I see this error message.
I just don't know how to mount that local folder on this instance, do you know where I can find any documentation on that ?
-
@fbartels you are probably raising a valid point about the freshness of the certs coming from
ca-certificatespackage. So the/etc/sslmounting trick might be quite useful.In this case however I am not so sure this is the issue, at least it didn't solve it refreshing that. Also other clients like curl have no issue to connect to an external site. So I think this is somehow related to the node10 version we have to use since the last stable mailtrain version we use is so old.
-
@fbartels you are probably raising a valid point about the freshness of the certs coming from
ca-certificatespackage. So the/etc/sslmounting trick might be quite useful.In this case however I am not so sure this is the issue, at least it didn't solve it refreshing that. Also other clients like curl have no issue to connect to an external site. So I think this is somehow related to the node10 version we have to use since the last stable mailtrain version we use is so old.
@nebulon said in Mailtrain issue with RSS feed from Wordpress, both on the same Cloudron server:
the last stable mailtrain version we use is so old
It looks like there has been a V2 available for quite some time now, perhaps time to package that up?
This is the latest release:
https://github.com/Mailtrain-org/mailtrain/releases/tag/v2.20210609.0 -
I wonder if this is because older node releases have trouble with the newer Let's Encrypt authority ? Related to https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
@girish said in Mailtrain issue with RSS feed from Wordpress, both on the same Cloudron server:
I wonder if this is because older node releases have trouble with the newer Let's Encrypt authority ? Related to https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
Could be, or at least something's related as you already know we're experiencing the same now with Joplin, which is preventing synchronization.
Andy
-
@nebulon said in Mailtrain issue with RSS feed from Wordpress, both on the same Cloudron server:
the last stable mailtrain version we use is so old
It looks like there has been a V2 available for quite some time now, perhaps time to package that up?
This is the latest release:
https://github.com/Mailtrain-org/mailtrain/releases/tag/v2.20210609.0 -
@jdaviescoates right, only last time I checked, it was a complete rewrite without a migration path. So essentially like a new project sharing the name. So might be worth looking at again, but that wont fix this immediate issue.
@nebulon true, it is a rewrite and won't solve this immediate issue, but it should still be packaged. I created a separate thread about that here:
https://forum.cloudron.io/topic/5769/time-to-package-mailtrain-v2
