-
Notifications
You must be signed in to change notification settings - Fork 87
script webpage is down #487
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
Comments
An ICM has been created for this internally |
Thanks @baronfel, this is blocking all of our .NET builds, we have workarounds but the impact is wide reaching |
It's also has been tracked here: dotnet/runtime#104230 |
For the sake of others reading this, a workaround (courtesy of @martincostello) is to use the following urls while the dotnet subdomain is down: |
Similar reports on other repos/sites for tracking/correlation: |
Apologies for the inconvenience. We are currently working on this and I'll update all issues once it's resolved. |
Issue is now resolved. Let us know if you're still having trouble. |
EDIT: this link is back as of ~40 minutes ago Just a heads up that links like these still fail: edit: which redirects to: This is generated when running a .NET app without the correct runtime installed:
|
Yes, we were missing one more service update. |
Uh oh!
There was an error while loading. Please reload this page.
https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.sh
https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.ps1
HTTP Error 500.30 - ASP.NET Core app failed to start
Common solutions to this issue:
The app failed to start
The app started but then stopped
The app started but threw an exception during startup
Troubleshooting steps:
Check the system event log for error messages
Enable logging the application process' stdout messages
Attach a debugger to the application process and inspect
The text was updated successfully, but these errors were encountered: