Deploying Web App Builder App to Custom URL - App Not Loading

I have been trying to deploy a simple web app to our website for the last two days, but have not been able to get it to load. I have gone through the process several times, but I must be missing something. The web app (http://www.webapptestbed3.epd-pgh.com/) displays the loading bars for a bit and then times out.

Here is what I have done so far:

1. Installed Web App Builder 2.8

2. Registered web App Builder

3. Opened Web App Builder and created a simple web app that points to a map and data on our ArcGIS Online account that is all shared publicly. The Web App successfully launches from within Web App Builder.

9. I tried adding each AppId in the config.json file, saving, and replacing via the FTP, but neither worked.

I am still only getting the loading screen when I go to http://www.webapptestbed3.epd-pgh.com/. I feel like I have followed all the instructions perfectly – and I know the Web App Builder install and proxy are working correctly. What am I doing wrong?

If you move your proxy to the external web server you should be good to go. Normally you would want your WAB App to be in s sub folder of your web server though so you can have more than one site on your web server. So instead of webapptestbed3.edp-pgh.com/ it would be webapptestbed3.edp-pgh.com/something/

If you are using AGOL and not on premise Portal then your portal url can be http OR https so just switch to using http for the url (in your main config.json).

1. That's what I thought, but all the instructions seemed to indicate otherwise. Would uploading the DotNet to http://www.webapptestbed3.epd-pgh.com/ solve this problem? Or should it be somewhere else outside the WebApp's folder?

2. I did not realize this would be an issue. Does this mean the domain we host the app on must be https? Our portal is standard ArcGIS Online.

If you move your proxy to the external web server you should be good to go. Normally you would want your WAB App to be in s sub folder of your web server though so you can have more than one site on your web server. So instead of webapptestbed3.edp-pgh.com/ it would be webapptestbed3.edp-pgh.com/something/

If you are using AGOL and not on premise Portal then your portal url can be http OR https so just switch to using http for the url (in your main config.json).