Hi Bjørn,

On the surface, this looks like a configuration issue as when I look at the IFS environment for your code I am able to access the AsteaMobileCustomizer.

Can you see if you have the website visible on your mobile server’s IIS Manager?

Is the NLB/ARR routing the request to connect also set up to handle the path to where mobile is deployed for the url for AsteaMobileCustomizer.  From your screen above, it seems to do it for AsteaMobileEdge.

For testing, can you also try the IP Address where mobile is deployed instead of mobil.waterlogic.no?

On the new profile you created for Denmark is mobile integration enabled? 

I would also review the config.json file in the AsteaMobileEdge\AsteaMobileCustomizer\app_data\ folder.  Are the URL’s there correct?

Thanks, Phil

I have not tried to access the Mobile Customizer in our live environment after go-line on 10.01.

I have looked over this, and compared to our UAT - the site is visible IIS Manager, but I get the same error if I try to browse it (with regular address, IP, or localhost).

There are 2 differences between UAT and live: UAT is on one server, while live as a Mobile server and an Alliance server. Also - live it setup with https only, while UAT is http

A bit more: in the config,json the local IP is defined. If I change this to the IP of the Alliance server, I get 

A question that arises is if it’s possible to move a customization manually from UAT to live environment?

Just to answer my own question: yes, it is very easy to move the files from UAT to Production environment - I just moved the folder with the customization (and renamed it), and used an address reflecting the change

Hi Bjorn,

Yes you should move Customizer customizations from UAT to Prod within the same version.  I just answered that way on the other topic you raised about this specifically.

Though most people would export from UAT to have a proper file for import and not copy the folder directly. This way you have a proper backup. 

In the AsteaMobileEdge\AsteaMobileEdgeServices\, back up the web.config and do a comparison of the comparison between the UAT where it is working and Prod Mobile server where it is not working.

I suspect there are some configurations in there that may not be correct; e.g. Redis host servers or perhaps something else but let’s see if you align them that it then works.

After updating the file, do IISRESET on the mobile server.

Try accessing the AsteaMobileCustomizer website again.

We have sent across to you, Bjørn, recommended changes to the web.config in the AsteaMobileEdgeServices folder based on trying to use https: through the entire communication chain. Hopefully this works now.