Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to install a self-signed CEP extension using ExManCmd.exe. #24

Open
6 tasks
RockWithBoA opened this issue Mar 25, 2020 · 1 comment
Open
6 tasks

Comments

@RockWithBoA
Copy link

Topic

This is an issue regarding:

  • The guides contained within this repo.

Versions

  • ZXPSignCmd 4.1.1
  • ExManCmd: downloaded from this page.
  • CEP 8
  • Photoshop CC 2018
  • Windows 7/10

Description of the issue

Installing a self-signed ZXP extension using command line command:

E:\Desktop\ExManCmd_win\ExManCmd.exe /install CepTest01.zxp

But it returns the following error:

Installing extension with file path = CepTest01.zxp
Failed to install, status = -402!

Proposed solution or attempted solutions that failed

Resigned and confirmed there is not any error reported when packaging the extension using ZXPSignCmd.

The certificate used and the self-signed CEP extension are attached.
certf_ext.zip

@ErinFinnegan
Copy link
Contributor

Hi there!

This is something that the CEP team is investigating; it seems specific to Windows and Photoshop. Here are the notes I've got:

Node doesn't allow the self-signed certificate authorized connections. It is recommended to use a proper SSL Cert from a trusted source.

Although for development we could use a few flags for node to bypass these checks(Try: rejectUnauthorize = false; Check https://stackoverflow.com/questions/45088006/nodejs-error-self-signed-certificate-in-certificate-chain )

Conclusion:
Please use a trusted certificate in production & try rejectUnauthorize = false for developments purposes to bypass this problem.

I know that certificates from an authorized source can be excessively expensive, so I'm hoping the CEP is able to solve this issue soon.

I the meantime, please try the workaround mentioned above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants