This also happens to me (Chrome-based browser), so I am going to flag this as an issue.
In the meantime, assuming you have a bound organization, you should still be able to bind projects from the SonarCloud-side, either by creating a new bound project:
I am taking a look into what is causing this issue. I have been able to recreate the problem and am currently investigating the cause of this. I will update here when I have some more useful information.
I brought this subject up internally and was informed that unfortunately due to incompatibility with this functionality, we will be decommissioning the support of binding directly through bitbucket. Therefore bindings would need to be handled either by through importing the project directly in Sonarcloud or by using the method of binding the project mentioned above by @Colin.
You mentioned that you have 2 instances of Sonarcloud, is there any reason for this?
You’ll still get the widget, but as Shane mentioned it will ultimately require a bound organization and bound projects.
We suggest using permissions to segregate repos among internal teams (which is probably what you’ve done on the Bitbucket side) rather than creating two separate unbound organizations.
The best (and really, only) migration path here is to choose the organization you want to move forward with, bind it to Bitbucket, bind your projects and then migrate projects from the other org into the original org.