Also getting error:

RemoTraC:1 Refused to apply style from ‘https://remotrac.caredx.com/RemoTraC/sCSS/48.0/sprites/1580155678000/Theme3/default/gc/common.css’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.

Also I’ve confirmed this is a v2 issue. I partially rebuilt the page in skuid v1 and it works. I love you guys but this is really aggravating. 

Jack, we’ll be reaching out to you directly to take a closer look. Thank you for bringing this to our attention.

Thanks, I’ve had to adjust repro links to accommodate that this site is live:

To see the error in the console go to https://remotrac.caredx.com/apex/RemoTraC_PatientIntake

It’s trying to load the same page as at https://xynmanagement.secure.force.com/RemoTraC/apex/RemoTraC_PatientIntake

Also you can see that  https://remotrac.caredx.com/apex/RemoTraC_PatientIntake_v1 works fine, using a skuid v1 page instead

Hi Jack, I just wanted to close the loop on this post. We checked in with you, investigated, and couldn’t reproduce the issue ourselves. You believe this was likely the result of an internal org setup detail - updating that resolved the issue for you. If you have further trouble with this though, please let us know!

Thanks for your quick help Mark. The issue seems to have been with the SSL, at least this is the only thing that changed between when it worked and when it didn’t. Everything seemed fine with the SSL but when I checked the site at https://www.sslshopper.com/ssl-checker.html it got a mild error that the SSL needed an intermediate/chain SSL added on. I had to re-download the SSL certificate from GoDaddy, and take the certifcate and paste it on top of the text in the bundle file, then upload that new file. That cleared the error on ssl checker. It was a few hours later I checked if the v2 page was working and it was, so I assume the SSL was the reason. The only browser that minded when the intermediate/chain wasn’t added to the SSL was an old version of Firefox on Windows, but maybe something in that blocked what skuid needed to load the page.