ER-wizard-WireGuard icon indicating copy to clipboard operation
ER-wizard-WireGuard copied to clipboard

Upload Failed

Open alanpaschoal opened this issue 1 year ago • 7 comments

Hi Guys! I am getting this error when I try to upload the latest .tar file. Upload Failed

alanpaschoal avatar Sep 04 '24 20:09 alanpaschoal

Same here

notnavindu avatar Sep 30 '24 06:09 notnavindu

Not working on Infinity Router With 1.6 or 1.7 Builds

ctv99 avatar Sep 30 '24 20:09 ctv99

I'm getting it too on EdgeRouter Infinity ER-8-XG, running firmware version v2.0.9-hotfix.6

SanfordYoder avatar Sep 30 '24 20:09 SanfordYoder

with chrome upload didn't work but worked with edge browser

cristianbuzle avatar Oct 04 '24 11:10 cristianbuzle

I got it uploaded with Waterfox (firefox fork), however, now the UI is very slow and unreliable. Some tabs won't load.

stephen-azure avatar Oct 24 '24 00:10 stephen-azure

With Google Chrome, same problem, with Firefox 128.5.0esr (64-bit), perfect. image

azagramac avatar Dec 30 '24 23:12 azagramac

The problem is in the fileuploader.min.js file on the routers. In _getIframeContentJSON() there's this check on the response from the upload endpoint:

"<pre" == $innerHTML$$.slice(0, 4).toLowerCase() && "</pre>" == $innerHTML$$.slice(-6).toLowerCase() && ($innerHTML$$ = $doc$$.body.firstChild.firstChild.nodeValue);

on the failing browsers, the $innerHTML$$ value is <pre>{"path": "/tmp/tmpqJcMmQ0", "success": true}</pre><div class="json-formatter-container"></div>; the code isn't expecting the <div> tags on the end and so the 2nd check fails, meaning the $innerHTML$$ is never redefined to valid JSON.

You can bypass it by setting a breakpoint in the browser on the check line, and when it hits remove the <div>.* from the response by setting $innerHTML$$= '<pre>....</pre>' in the console and it'll process the upload correctly.

scourge411 avatar Apr 15 '25 02:04 scourge411

Falling back to Safari for the upload did the trick for me

suomi35 avatar Jun 15 '25 05:06 suomi35

Thank you @scourge411 for this detailed debugging! I was looking for the cause and a possible way to work around that but didn't find any solution. As far as I know, this is/was a known issue at Ubiquiti with EdgeOS v2. Since EdgeOS v3 was released I would ask to upgrade, and try again. I didn't try yet but got told that the issue was fixed.

vchrizz avatar Aug 13 '25 21:08 vchrizz