You can specify your own CA for internal certs:  set NODE_EXTRA_CA_CERTS=C:\\path\\to\\certificate.pem

--no-publish is likely fine for your use case. You're sending the incorrect auth for that namespace as indicated in the error:  401 (Unauthorized) --> › "The supplied authentication is invalid" I'd recommend checking that you're using the correct namespace auth token for staging. 

No, I don't think that would be necessary if you're not blocking any traffic. I posted it as many customers have strict outbound rules and need to open each domain individually. 

It is possible those are not currently utilized but reserved for future use. Here's the full list of our domains:{wildcard}.adobeio-static.net {wildcard}.adobeioruntime.net {wildcard}.adp.adobe.io addons.adobe.com adobe-addons.com adobe-runtime.com adobeio-static.net adobeioruntime.net adp-installse...

@Amit_Zulphe - yes, aio communication is all over port 443. 

Are you asking how to pass the username/password from the UI input to the action itself and wait for the auth response?

Hi @_Clodo_ Is it possible you are creating a new project with a previously used name? Can you try with a unique name and see if you still get the issue? -Patrick