The Pulumi UI (https://app.pulumi.com/) is a bit shaky today. Navigating to a project site results in 404.

@busy-honey-73811 How do you login to the Pulumi app? Github? SSO?

GitLab

Thanks. And is it intermittent? So for example can you click on the link to go to the stack and you always get the 404 or is it only sometimes?

Yes, it is happens all the time:

So I've just created an account so I can sign in and when I create a project I'm not seeing the 404. We do use 404 if you try to access something you don't have access to, so can you check in your organisation that you have the correct access set up please. (if this is the case, it doesn't answer why you're able to see the lists, but one step at a time)

I have all the permissions available (ADMIN access), also if I directly navigate to the project’s site by entering https://app.pulumi.com/.../cockroachdb-backup, it works as expected.

Ok, let me talk with the engineers and I'll get someone to respond to your issue. In case they ask, what's your organisation name?

Maybe it is caused by cookies being blocked by Firefox:

Interesting... that would definitely cause a 404 to show (as it doesn't think you're authenticated). Is it possible to turn that feature off in FF?

I have no ad-blocker in place and the same behaviour on Chrome, so it is not Firefox specific. Furthermore, it does not use Cookies for authentication on the failing endpoints, it passes a

Authorization

header instead with a token

Authorization: token pul-...

.

Have you managed to see these stacks from before today? Reason I'm asking is that I've found some errors where we couldn't get some details for you from gitlab and I'm wondering if there's an issue because of that.

Yes, I was able to access these (resp. all) stacks until today. It looks like it stopped working with the most recent Pulumi UI update (since the dashboard has been introduced). Also I don’t see what my GitLab user has to do with this incident, especially as most other Pulumi pages are still working.

ok... Just spoken to some others and they're seeing it as well, so hold off on doing any changes with users for now

Have the same issue. We have SSO with Azure AD configured.

Hi folks, just to keep you updated, a fix is being worked on. In the meantime, there is a workaround where you can go to https://app.pulumi.com/orgname/projectname (substituting orgname and projectname for appropriate values)