Problems installing v2.0, compatibility with 1.3?

[TracySchloss]

I downloaded WAB version 2.0, but I'm having problems getting it initialized.  I thought maybe it didn't like the AppID I had created for WAB1.3, so I registered a new App.

I installed 2.0 in a new directory and I'm not too concerned about keeping both versions up and running.    I just want 2.0 to load.  I got as far as the dialog that asked about my AGOL Url and my AppId.  Once I click continue, I'm getting a mixed content kind of message

init.js:1241 Mixed Content: The page at 'https://mymachineNameishere:3344/webappbuilder/?id=2' was loaded over HTTPS, but requested an insecure script 'http://mylocation.arcgis.com/sharing/rest/portals/self?f=json&token=MF3yCXU…W_ZZRpQjvSGeen&callback=dojo_request_script_callbacks.dojo_request_script0'. This request has been blocked; the content must be served over HTTPS.

That's as far as I get.  I don't remember having this problem starting up 1.3,  but maybe I've just forgotten. 

[RobertScheitlin__GISP]

Tracy,

  Did you use http or https for the portal url when you first launched WAB 2.0? Did you use the same http or https when you registered the app in your orgs AGOL content?

[TracySchloss]

I tried both and both are registered.  I just noticed that Chrome was telling me it was attempting to load mixed content.  I told it it was OK and now it's working. The symbol is such a light gray I didn't even notice it.

[RobertScheitlin__GISP]

Tracy,

   If you did mix http and https when you started the app you can go to [install dir]\server\ and delete the signininfo.json file (it will be recreated when you launch again and go back thought the portal url and app id dialog).

[TracySchloss]

That would be a good suggestion for someone else, but I tried that a couple times before I posted.

[RobertScheitlin__GISP]

There is some reason you are getting a mixed content error. If you use https when you set the portal url then WAB will use https from that point forward. And if you used https for the app registration url and the redirect url then I don't see how you are getting this error.