2

I'm trying to perform the command to deploy my application to a remote CM server

jss deploy app --includeContent --includeDictionary

but I receive the following error

Sending package sitecore\package\internal-portal.1598564849342.manifest.zip to http://internal.local:44001/sitecore/api/jss/import...
Unexpected response from import service:
Status message: Forbidden
Body: Invalid authentication.

Has anyone ran into this problem before? Other posts talking about "Forbidden" statuses had different body messages.

Here's some other details

  • My CM server is running from a Docker container on my laptop with port 80 mapped to 44001.
  • I've executed a jss deploy config and manually copied the 2 config files from my local App_Config/Include/zzz to the server's C:\inetpub\wwwroot\App_Config\Include\zzz
  • Given the sitecore\JSS Import Service Users full permissions to the /sitecore item and all it's descendants.
    enter image description here
  • Here's my scjssconfig.json
    enter image description here
  • In my hosts file, I have internal.local mapped to 127.0.0.1

Thanks in advance! :)

Improve this question
2
  • 2
    As you are using docker containers, this is what you need to do. github.com/Sitecore/jss/issues/369
    – Vincent Lui
    Commented Aug 27, 2020 at 22:22
  • Thanks Vincent. I'll have to give that a try. Hopefully Sitecore will release a fix soon though since that's quite a hacky workaround. The thread says they were aiming for JSS 14, but I the issue is still open and I don't see anything mentioned in the release notes about fixing it.
    – KingTwinkie
    Commented Aug 27, 2020 at 22:37

1 Answer 1

Reset to default
-1

Try

jss deploy app --includeContent --includeDictionary --acceptCertificate test

Once you run above, you will get error message saying expected certificate (something like F3:AC:61:. ... . . . . ) but recieved test

Now again run jss deploy app --includeContent --includeDictionary --acceptCertificate F3:AC:61:. ... . . . .

Improve this answer
1
  • 2
    The endpoints from the OP are not HTTPS. This is a specific issue with docker as it does not take into consideration of the port number.
    – Vincent Lui
    Commented Aug 28, 2020 at 8:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.