-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Failure to flash from balena dashboard #3778
Comments
the flash from the dashboard works with versions 1.7.8 and later |
Ok, good to know. Because from what I see, the latest I can download is 1.5.115 |
Where do you see 1.5 as latest? https://github.com/balena-io/etcher/releases/download/v1.7.9/balenaEtcher-Setup-1.7.9.exe |
On the main page: |
Well, that is weird, thanks for pointing it out. |
No worries. Thanks for helping me with the Releases link. I tried to find it myself, but what I found redirected me to the main page, haha. |
The Etcher website sometimes points to an old version if you have JavaScript turned off? (which has happened in several issues here previously) EDIT: When I do view->source on the Etcher webpage, I see e.g. |
Cross-site policy blocked to fetch the right version, and it fallbacks to 1.5 |
...or some people run things like NoScript #2833 (comment) |
We can't fix what some people run 😅 , |
Etcher version: 1.5.115
Operating system and architecture: Windows 10 (x64)
Image flashed: Raspberry Pi 4
What do you think should have happened: After I click on the flash button in balena dashboard I expected balena etcher to open and start flashing the correct image on the disk.
What happened: After I click on the flash button in balena dashboard, balena etcher opens and shows the following error:
Do you see any meaningful error information in the DevTools?
{"stack":"Error: ENOENT: no such file or directory, open 'C:\\WINDOWS\\system32\\%7B%22method%22%3A%22POST%22%2C%22url%22%3A%22https%3A%2F%2Fapi.balena-cloud.com%2Fdownload%3FappId%3D1944541%26deviceType%3Draspberrypi4-64%26version%3D2.98.33[...]
The text was updated successfully, but these errors were encountered: