Downgraded to 2.4.0 and it works. Was not aware of the Helm v2 or earlier requirement at http://developer.avid.com/cert/feature-pack-installation/docs-public/build.html

I think I've found the cause. The localhost certificate used by cloudux-starter-kit does not have a "Subject Alternative Name" as chrome reports in the screenshot I posted. This causes chrome to block all calls to https://localhost, this then crashes the proxy server. A solution that works is setting the #allow-insecure-localhost chrome

Hi there, Running a plug-in app going to localhost gives me this error on chrome: I mostly ignore this error but the plug-in has been crashing and Media Central constantly reports a" NET::ERR_CERT_COMMON_NAME_INVALID " error to the console. I want to rule this out as the source of the crash. How do I fix this problem? Edit: Wanted to add more

It's 3.7.1

I see, thanks Tilman. For the 3rd option, did you purchase an extra cloudux instance like mentioned here ?

Hi there, I was testing the cloudux-starter-kit feature pack build process and I ran into this error I followed the instructions on this cloud-ux-starter-kit page and put in all the neccessay information in the project. Any idea what's happening here? -Kenneth

Hi Michael, Tried this out and no matter the machine I use it says " Error: listen EADDRNOTAVAIL: address not available". Could you explain how the Cloudux-starter-kit tries to create the proxy on the proxyhost provided?

Yup looks like it works. On another note, is it possible to use typescript in the react app created by cloudux starter kit?

Hi there, I'm working on a media central cloud ux plug-in and I'd like to setup a testing environment so other members of my dev team can see a testing version of the plug-in as it's developed. I would also like to setup CD/CI for this testing version. I came across this tutorial called "CI / CD - how to deployment from docker registry"

I see, I think a Connector service won't be neccessary for what I'm trying to do. Turns out I'll needed is the right CORS policy on the API server. Thanks for your help :)