That's for the update. The problem we (maybe others) is with our corporate
firewalls - at some point the name is lost so they end up having to build
rules for each of the mirror'd ip's, That is probably why we are getting
the 503 is that it's not making out of our network and been blocked since
(replies inline)
On Thu, 21 Apr 2016, Mark Diskin wrote:
> Over the last few days I'm getting 503 now.
>
> Looks like a AWS server is now is there an updated list of mirror sites
> since we have to have each one allowed in our networking security/firewall
> rules.
Correct, I've migrated
Over the last few days I'm getting 503 now.
Looks like a AWS server is now is there an updated list of mirror sites
since we have to have each one allowed in our networking security/firewall
rules.
nslookup 52.91.151.148
Server: 10.165.20.21
Address:10.165.20.21#53
