apt fails to install from pmc-geofence.trafficmanager.net: 403 Forbidden about msphpsql

[skylord123]

@v-maximko just seeing if this issue was in fact now occurring again? or if we have some other issue unrelated. Seems like it could be though given other comments above.

From my experience and reading up from others: Microsoft struggles to keep their apt repo stable and online. There are numerous posts of people's CI/CD builds failing due to this issue.

Not sure if this is malicious or just gross incompetence but I find it hard to believe that a company with over 200 datacenters and a net worth exceeding 3 Trillion dollars would struggle this bad for any other reason.

[v-maximko]

Should be fixed now, can you try again?

[skylord123]

Yes this is working now. Do we know what happened?

[v-maximko]

There was a temporary problem with the repo that has now been resolved

[jimpatrickong]

I'm getting this same error today..how do I know if there is an issue with the package?

[hannesrd]

We are getting the same error in kubernetes again.
https://pmc-geofence.trafficmanager.net/debian/11/prod/pool/main/m/mssql-tools18/mssql-tools18_18.2.1.1-1_amd64.deb?geofence=true

curl also fails

[wes614]

@v-maximko just seeing if this issue was in fact now occurring again? or if we have some other issue unrelated. Seems like it could be though given other comments above.

E: Failed to fetch https://pmc-geofence.trafficmanager.net/ubuntu/16.04/prod/pool/main/m/mssql-tools/mssql-tools_17.8.1.1-1_amd64.deb?geofence=true Certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. Could not handshake: Error in the certificate verification.

[v-makouz]

@skylord123 @wes614 I tested these packages and was able to curl them without a problem, so not sure if it was intermittent or fixed already. If you're still getting the certificate error, can you try running openssl s_client -connect pmc-geofence.trafficmanager.net:443 and see if it shows Certificate chain?

We don't usually monitor closed issues, so even if it's a similar or same error as before, it's better to open a new one.

[wes614]

Thanks @v-makouz. It seems we've actually managed to get around this with the issue being related to our company's internal network security setup after we compared an openssl check from a few different machines. Appreciate the hustle by all :)