I am having issues running a lightweight PB application called CRH that has been deployed to a remote Amazon AWS server.  The app was built with PB 2021 build 1288 and uses SQL Server for the database.  The deployment goes fine and I can download and install the Cloud App Launcher (CAL) on the client machine (my laptop).  I can run the application on the server itself w/o issue and when I enter the external IP address of the server in chrome on my laptop, I get the IIS default page.  So the server is reachable and running normally.  The AWS server is Windows Server 2019 and the client is running Windows 10.

When I download the CAL, I get a Windows Defender warning but am able to continue past this and install it.  It shows up in Control Panel as part of my installed programs.  Thinking a security issue might be the issue and after reading other posts in this forum, I did the following:

1. Signed the exe with a Comodo code signing cert
2. Signed the CAL with a Comodo code signing cert
3. Selected the Embedded Manifest option
4. I'm using the Default_WithoutService option

None of the above have helped.  When I look at the properties of the exe and CAL, I can see my cert attached.  What happens is that after the CAL installs, nothing happens when I click 'Start Application' button.  Doing so pops up a dialog where I have two options -- 'Open App Launcher' or 'Cancel'. Clicking either does nothing other than close the popup.  If I hover my mouse over the 'Start the Application' button, you will see the following flash in the lower left of the browser:

cloudapp://http://http://34.233.170.139/CRH

If I move the mouse off the button it will just flash 'Connecting...' over and over.  I need to validate that a PB app will run properly when deployed to a remote server via PowerClient (and ultimately PowerServer) so any help with would be greatly appreciated.

Note:  I also tried running the application in chrome on a new pristine laptop and it didn't work there either -- same issue.  I've redeployed the app several times after wiping things out on the AWS server and have rebooted the server several times as well.  No joy...

Thanks, Tom