We recently had a customer who deployed a new UAT environment as a single server deployment where it was not possible to connect to the AsteaMobileCustomizer website. The error they were seeing in Chrome was a 404 error and also:
Using this topic as a basis for troubleshooting written by Andrew d’Antonio:
We found there were references to other servers in the redis-windows.conf and redis-sentinel.conf files than the single server. The global.xml was set up correctly, the mobilecustomizer config.json also was correct.
The problem was how redis functions with master, slave relationships. One server serves as a master and other redis servers act as slaves & fallback retaining the server information for each server that was part of the redis configuration.
Changing only the two redis configuration on the single server environment was not sufficient to disconnect the external servers from the other environments as at one point in time in the past, they all were connected in a multi-server environment.
To resolve this, it was necessary to ensure that ALL the servers referenced in the redis conf files were turned off even if that server was not supposed to be part of the environment. If this is not done, Redis will restore the server information again from the remote servers if you only modify the single server redis configuration even if you are sure the global.xml, config.json, etc. are correct.
After all Redis cache services were stopped, we modified the redis configuration files on ALL servers so they no longer had references to the other redis cache servers where not appropriate.
Please see below redis-sentinel.conf file as an example where the only redis cache service we wanted was on the 10.44.0.67 server.
In the redis-windows.conf, we removed the reference to 10.44.0.64 as it was external to the single server environment:
While we kept the cache services off, we reconfigured the external servers’ versions of the redis conf files appropriate for their topology. (e.g. the 10.44.0.64 server was also supposed to be a single server deployment so removed references to any other servers).
Then we started the cache services and verified no unwanted server references were in the the conf files.
This cleared up the access to the AsteaMobileCustomizer website. Reason for this is that the mobile customizations are stored in the redis databases thus connecting to the site was reading information from wrong locations, etc.
In short, it is necessary to look at all the servers mentioned in the respective redis conf files even if they are not supposed to be a part of the single server environment.