Unable to import configs after upgrade to Expedition 1.1.84 -- "Failed"

[gb2057]

After upgrading with sudo apt-get update && sudo apt-get install expedition-beta, I can no longer import any config.

I have even tried starting from scratch with a fresh Ubunto 16.04 LTS VM.  I cannot import any config -- Palo Alto for my base, nor Cisco ASA configs. Even tried same configs which had imported successfully before the update to 1.1.84, they no longer import successfully. The tool has gone from extremely useful to not usable at all.

When I select a .xml to import the Palo Alto config (or any config to import), I immediately get a blank pop-up titled "Failed"

I have scoured the system for any error logs, nothing in /tmp, or /var/log/apache2/error.log or anywhere I can find.

Any tips? Here is a screenshot:

Thanks in advance for any assistance,

G

[lychiang · Accepted solution]

Hi @gb2057 I am not seeing that issue in my expedition 1.1.84, can you please check if there is any message in /tmp/error ?  Also try to clear the cookies in your browser and relaunch it. If you need further helps, please write email to fwmigrate@paloaltonetworks.com.  Thank you!

[gb2057]

Hi @lychiang 

Thank you for the response. You are correct it was client-side, it appears a Chrome extension was causing the issue. Testing an OVA that had an earlier version (known to work) I saw I had the same issue. I started Chrome "incognito" with all extensions disabled and everything works great once again. Not sure which specific extension, but issue was definitely my client browser and not any issue with Expedition tool. I went ahead and accepted your answer as a solution since it does infer it is client-side issue and version 1.1.84 does work as expected.

Thanks again!

[gb2057]

@lychiang fyi there was no error, nothing found in /tmp/error... I scoured the system for any logs, for all files modified in past few minutes, there was no clue in the Ubuntu system of any issue or at least I could not find anywhere to start. I thought it strange to not see any logs, because the error pop-up appears to be sent by Expedition itself, albeit there is no error message other than "Failed"

Thanks,

G