We're using Creative Exchange Live gulp task to upload FE Assets but at the moment it is keep failing by giving 403 error status message.

I have followed the Sitecore documentation on setting up at this link.

  1. Enabled the file \App_Config\Include\z.Feature.Overrides and enable the z.SPE.Sync.Enabler.Gulp.config.disabled for overriding default config to enable MediaUpload, MediaDownload and RestfulV2.
  2. Using sitecore\admin account as it defaults to Sitecore admin and checked if it's enable by checking config value for
            <add Permission="Allow" IdentityType="User" Identity="sitecore\username" />

After that run the Gulp task and it gave us the error as below. enter image description here

Anyone ever had this issue? If so how can I fix this issue?


  • Hi and welcome to Sitecore Community. Have you also modified ThemeRoot/gulp/config.js and set proper server url under server options section? – Peter Procházka Apr 19 at 5:18
  • Also please add HTML of Answer with error message to your question in textual way so it's easily searcheable in Google. Image won't be – Peter Procházka Apr 19 at 6:25
  • Hello @PeterProcházka, thanks for the advice, I will try to be more detailed and clear next time. As for the problem we have changed OOTB files a little bit and reduced the script smaller in size and included user and server configs in gulpfile.js itself. And the script gets user details either from variable in the file or if not gets from user input. Server URL is also setup properly and the request went to server url and get no authorization error for the FE assets and then since we have 5 try policy for the user it gets locked after 5th request. – Tumendelger Apr 19 at 6:34
  • Does it pass the username/pswd correctly ? Can you a run a wireshark trace to see that. Also, check if the username/pswd is correctly picked up from the serverconfig.json & config.js – Abhay Dhar Apr 19 at 7:25
  • Hello @AbhayDhar, yes it is passing user name and password correctly. Interestingly I have created support case to Sitecore and they ran the codebase in their test env to reproduce the issue, but all worked without issue. Now I am thinking something is happening in our local environment setup which is causing the issue. It's just bit painful to debug. – Tumendelger Apr 29 at 1:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.