I’m trying to set up a new octopus server to test the upgrade paths from 3.0 to 3.2, but I can’t seem to log in with the new administrator account I created.
I’ve tried setting up an instance with both a clean, empty database and a restored backup of our 3.0 database, but each time when I try and log in with the new administrator account defined in the installer I get:
You must be logged in to perform this action. Please provide a valid API key or log in again.
If I enable Guest access through the Octopus Manager and try to “sign in as guest” I get the same error message.
There doesn’t appear to be anything particularly useful in the logs.
Sadly I get the same message - “you must be logged in to perform this action”.
No, I’d deliberately installed this on a new machine to test this out - however it’s a Windows 8.1 workstation talking to a local SQL Server instance rather than a Windows server. I’ll try it on a new VM in a little while.