We backed up then restored octopus to a new server which is on a new domain which is different to where our main users are.
This has some initial issues but now the only have one issue left and users are now logging in prefixing their domain to their account name.
The issue I have is that our team city service account no longer works. We get the error:
[12:27:12][Octopus Deploy] Error from Octopus server (HTTP 403): You do not have permission to perform this action. Please contact your Octopus administrator.
[12:27:12][Octopus Deploy] Exit code: -7
[12:27:12][Octopus Deploy] Octo.exe exit code: -7
[12:27:12][Step 7/7] Unable to create or deploy release. Please check the build log for details on the error.
Hi John,
Thanks for getting in touch! Could you please generate a new API Key for the service account and see how this goes.
Thanks!
Vanessa
hi,
We have created a new API key but this has not worked.
We use the api key to push the package via TC and this works. It is only creating the deploy via Tc that fails.
I have more of an error message from ocotopus:
You do not have permission to perform this action. Please contact your Octopus administrator. (http://octo.int.wiggle.com/api/projects)
An error (1301) occurred while enumerating the groups. The group’s SID could not be resolved.
You do not have permission to perform this action. Please contact your Octopus administrator. (http://octo.int.wiggle.com/api/projects)
We have now moved it back to the old domain and it all works again. Happy to leave it on the old domain.
Hi John,
Just as an FYI I’ve had a chat with the Dev’s and we think this might have been caused with the security groups in AD and the service account not being correctly updated.
But if you are happy to keep it on the old domain this will stop all the AD headaches we might have to troll through to find where its breaking in the permissions.
Vanessa