I can not install Material Icons from package - 502 Bad Gateway

[irradev]

Duplicates

• I have searched the existing issues

Latest version

• I have tested the latest version

Steps to reproduce 🕹

No response

Current behavior 😯

No response

Expected behavior 🤔

No response

Context 🔦

error An unexpected error occurred: "https://registry.yarnpkg.com/@mui/icons-material/-/icons-material-5.10.9.tgz: Request failed "502 Bad Gateway"".

LOG:

Arguments:
C:\dev\node.exe C:\Users\asriel\AppData\Roaming\npm\node_modules\yarn\bin\yarn.js add @mui/icons-material --network-timeout 100000

Yarn version:
1.22.19

Node version:
16.15.1

Platform:
win32 x64

Trace:
Error: https://registry.yarnpkg.com/@mui/icons-material/-/icons-material-5.10.9.tgz: Request failed "502 Bad Gateway"
at ResponseError.ExtendableBuiltin (C:\Users\asriel\AppData\Roaming\npm\node_modules\yarn\lib\cli.js:696:66)
at new ResponseError (C:\Users\asriel\AppData\Roaming\npm\node_modules\yarn\lib\cli.js:802:124)
at Request. (C:\Users\asriel\AppData\Roaming\npm\node_modules\yarn\lib\cli.js:66215:16)
at Request.emit (node:events:527:28)
at Request.module.exports.Request.onRequestResponse (C:\Users\asriel\AppData\Roaming\npm\node_modules\yarn\lib\cli.js:141767:10)
at ClientRequest.emit (node:events:527:28)
at HTTPParser.parserOnIncomingClient (node:_http_client:631:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
at TLSSocket.socketOnData (node:_http_client:494:22)
at TLSSocket.emit (node:events:527:28)

npm manifest:
{
"name": "d-landing",
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint"
},
"dependencies": {
"@emotion/cache": "^11.10.3",
"@emotion/react": "^11.10.4",
"@emotion/server": "^11.10.0",
"@emotion/styled": "^11.10.4",
"@mui/material": "^5.10.10",
"next": "12.3.1",
"react": "18.2.0",
"react-dom": "18.2.0"
},
"devDependencies": {
"@types/node": "18.11.3",
"@types/react": "18.0.21",
"@types/react-dom": "18.0.6",
"eslint": "8.25.0",
"eslint-config-next": "12.3.1",
"typescript": "4.8.4"
}
}

Your environment 🌎

npx @mui/envinfo

  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

Browser: Chrome

System:
OS: Windows 10 10.0.19045
Binaries:
Node: 16.15.1 - C:\dev\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.11.0 - C:\dev\npm.CMD
Browsers:
Chrome: Not Found
Edge: Spartan (44.19041.1266.0), Chromium (106.0.1370.52)
npmPackages:
@emotion/react: ^11.10.4 => 11.10.4
@emotion/styled: ^11.10.4 => 11.10.4
@mui/base: 5.0.0-alpha.102
@mui/core-downloads-tracker: 5.10.10
@mui/material: ^5.10.10 => 5.10.10
@mui/private-theming: 5.10.9
@mui/styled-engine: 5.10.8
@mui/system: 5.10.10
@mui/types: 7.2.0
@mui/utils: 5.10.9
@types/react: 18.0.21 => 18.0.21
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
typescript: 4.8.4 => 4.8.4

[oliviertassinari]

It sounds a bit related to #12432 but different. I sounds like a simple network error, so to close.