-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import shouldn't fail when a pod certificate is invalid #8300
Comments
diaspora.eigenlab.org uses a self signed, expired certificate. So this should not be used. The diaspora service is down. |
Reopen, because it seems that migration stops if a pod is not fetchable. In this case, by SSL problem. |
Should a rescue 'OpenSSL::SSL::SSLError' be added to the 'entity_importer.rb
? |
No, And this is actually weird, in this case it's a (1ec0314 was merged 10 days ago, this issue is newer, but maybe the test was done before that or before updating with this fix included?) |
That test has been done the 8th of September with the commits from #8274 at that time. |
OK, as far as I can see that PR didn't contain that fix at this time, but it should be fixed now, so closing this. |
Then it’s very likely that the change was not included. (And why I did not see this issue)
… Am 28.09.2021 um 16:35 schrieb Fla ***@***.***>:
That test has been done the 8th of September with the commits from #8274 at that time.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
DiasporaFederation::Discovery::DiscoveryError: Failed to fetch https://diaspora.eigenlab.org/.well-known/webfinger?resource=acct:vcuculo@diaspora.eigenlab.org for vcuculo@diaspora.eigenlab.org: Faraday::SSLError: SSL_connect returned=1 errno=0 state=error: certificate verify failed (self signed certificate)
See full stack trace:
https://gist.githubusercontent.com/Flaburgan/beb704a006ae1a299f4e1caf11bd70c2/raw/e1a7729bd002dbe42171172a0a830f279151fa91/Import%2520from%2520diasp.org
The text was updated successfully, but these errors were encountered: