-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Refreshing repositories #90
Comments
This is generally an indication that something is wrong with the network. Could be a VPN app, a firewall, proxy, router... anything preventing ReaPack from connecting to SSL revocation servers. If you cannot find the root cause on your end, then you can disable "Verify the authenticity of SSL/TLS certificates" in ReaPack > Manage repositories > Options > Network settings to bypass the issue. (If you're in a corporate network and must connect through a specific proxy server, specify its address in the same Network settings window instead.) |
Thanks for helping, i'm using Portmaster, but, there's nothing blocked on the log, do you have any expertise on that? |
I'm not familiar with that app, but do make sure it's not blocking or interfering with REAPER in any way, including no SPN. The SSL certificate revocation servers for github.com are currently ocsp.sectigo.com, ocsp.usertrust.com and ocsp.comodoca.com. The error indicates it could start the HTTPS connection with github.com (so it's not fully blocked from internet) but could not reach one or more of those revocation servers. Disabling "Verify the authenticity of SSL/TLS certificates" in the settings will bypass that step altogether. |
I'm getting this error when refreshing repositories, any idea to solve?
The text was updated successfully, but these errors were encountered: