RemoteOrgSignupFailed: A fatal signup error occurred. Please try again.

Summary

This bug was discussed before but it appears to be back or was never fixed.

Steps To Reproduce:

$ sfdx force:org:create -f ./config/production-scratch-def.json --json --loglevel fatal

Expected result

New scratch org is created from production org shape. (We are on the pilot)

Actual result

{ "status": 1, "name": "RemoteOrgSignupFailed", "message": "A fatal signup error occurred. Please try again. If you still see this error, contact Salesforce Support for assistance.", "exitCode": 1, "commandName": "OrgCreateCommand", "stack": "RemoteOrgSignupFailed: A fatal signup error occurred. Please try again. If you still see this error, contact Salesforce Support for assistance.\n at signup.retrieveScratchOrgInfo (/home/paul/.local/share/sfdx/client/7.27.0-714f62f9c1/node_modules/salesforce-alm/dist/lib/org/scratchOrgInfoApi.js:312:21)", "warnings": [] }

Additional information

This was an earlier issue that was closed as fixed https://github.com/forcedotcom/cli/issues/142

SFDX CLI Version(to find the version of the CLI engine run sfdx --version): sfdx-cli/7.27.0-714f62f9c1 linux-x64 node-v10.15.3

SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core) @oclif/plugin-commands 1.2.3 (core) @oclif/plugin-help 2.2.1 (core) @oclif/plugin-not-found 1.2.3 (core) @oclif/plugin-plugins 1.7.8 (core) @oclif/plugin-update 1.3.9 (core) @oclif/plugin-warn-if-update-available 1.7.0 (core) @oclif/plugin-which 1.0.3 (core) @salesforce/sfdx-trust 3.0.5 (core) analytics 1.2.1 (core) generator 1.1.1 (core) salesforcedx 46.17.0 (core) ├─ force-language-services 46.24.0 (core) └─ salesforce-alm 46.22.0 (core)

sfdx-cli 7.27.0 (core)

OS and version: Linux Ubuntu 18.04.3 (Bionic Beaver)

[packocz]

@pagner @renatoliveira I was able to get round this error by removing the siteDotCom setting and only keeping Sites. However, I didn’t yet get as far as to confirm the deployed public sites actually work

[shetzel]

RemoteOrgSignupFailed is a serverside signup issue and nothing that the CLI team can do anything about. Whenever this happens it’s best to contact support who can then investigate much more quickly.