Closed marek-mazur closed 4 years ago
Seems to be every other week now.
@joshjordan At least we have live updates every time: https://twitter.com/railsassets ... oh wait ;-)
"In development, if you have issues with SSL certificates and security is not a priority, you can use the alternate endpoint http://insecure.rails-assets.org instead."
@marek-mazur did that "http://insecure.rails-assets.org" worked for u? For me it says: "Could not fetch specs from http://insecure.rails-assets.org"
@Teckden Yes. It helped.
@marek-mazur thanx for the reply. It seems that for some reason our dns servers in VPN have the old address for rails-assets in the cache :( I guess, need to wait extra time
Just faced this issue again.
Hope the solution will help someone: just add 192.241.135.61 rails-assets.org
to /etc/hosts and try curl https://rails-assets.org
.
Bypassed Route 53 and updated DNS directly - we're up again. See #459
"In development, if you have issues with SSL certificates and security is not a priority, you can use the alternate endpoint http://insecure.rails-assets.org instead."