App Gallery fails to login to device

[XAG Admin]

One additional piece of information.  

Once you are able to add the device to your App Gallery Web Portal account, I would recommend re-installing the App Gallery App on to your device.  This should solve the 404 issue that you described in your initial post.  We have a known issue with a URL redirect that we are currently working to resolve.  

I hope that this helps.  Again, please let me know if you are still experiencing issues adding the device or with the App Gallery App. 

Thank you, 

XAS Moderator

[XAG Admin]

Hello. 

Thank you for the post. 

I would check the date/time/time zone settings for the device.  If the date/time and or time zone are off (by a few minutes) from the actual local time, this error could occur. 

After you have had a chance to check this, please let me know if this has resolved the error.  If it has not, I will investigate further. 

Thank you, 

XAS Moderator

[levangiech]

We recently received a new VersaLink B8045 to prep for installation. In attempting to connect it to App Gallery in order to install out support software, we received this error:

However, we have not changed the default login information for the device, so it is still admin/1111. We have confirmed this through two different computers successfully logging in to the device website, and through logging in to the device itself. We also tried to login to App Gallery through the machine itself, but received a 404 error immediately upon opening App Gallery.

As we first tried to login to the machine in this fashion after upgrading to the newest software (R19-04, 101.008.059.12100), we attempted a forced downgrade of the machine to the previous software (R19-02, 101.008.029.03810). This also failed to resolve the issue. We also reset the network controller to wipe any settings that may have accidentally interfered with the login data. Furthermore, we manually reset the admin password to 1111 to ensure that it had not somehow been changed. None of these attempts solved our issue.

What further steps could we take to fix this?