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

Request failed: 403 "No realm detected." on drush psite-create #148

Closed
dearmond opened this issue Jun 18, 2014 · 4 comments · Fixed by #149
Closed

Request failed: 403 "No realm detected." on drush psite-create #148

dearmond opened this issue Jun 18, 2014 · 4 comments · Fixed by #149

Comments

@dearmond
Copy link

Here's my terminal log:

$ drush psite-create 403REALLY2
Human readable label for the site [403REALLY2]:
Organizational affiliation
...
2
Select your starting state.
...
7
Queuing build. [ok]
Your new site "403really2" is now building with UUID "Object". [ok]
Waiting for site spin-up to complete. You can cancel at any point and the process will continue in the background.
.Request failed: 403 "No realm detected." [failed]
Invalid argument supplied for foreach() terminus.drush.inc:1494 [warning]
Invalid argument supplied for foreach() terminus.drush.inc:1498 [warning]
Invalid argument supplied for foreach() terminus.drush.inc:1518
.Request failed: 403 "No realm detected." [failed]
Invalid argument supplied for foreach() terminus.drush.inc:1494 [warning]
Invalid argument supplied for foreach() terminus.drush.inc:1498 [warning]
Invalid argument supplied for foreach() terminus.drush.inc:1518

And repeated.

@joshkoenig
Copy link
Contributor

Looks like there may have been a backend change in response to the site creation process:

Your new site "403really2" is now building with UUID "Object". [ok]

Looks like it's not getting the proper UUID back now, and so isn't able to properly use that to check on completion. I'll see what I can discover.

@joshkoenig
Copy link
Contributor

Confirmed there's a bug on site create. Fixing this will require us to deploy a change to the platform, and also likely an update for Terminus on the client site.

Stay tuned for a pull request to fix this later today.

@joshkoenig
Copy link
Contributor

Ok, the platform fix is going to roll out shortly. Stay tuned for an update on Terminus.

You'll need to pull from Master to get things working once it hits.

@dearmond
Copy link
Author

Works like a charm! Thanks!

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

Successfully merging a pull request may close this issue.

2 participants