Tried to install via button or manually, keep getting 500 errors or it redirects me to 404 on our website. Is it just me?
AI-generated summary
Users are experiencing a 500 error when installing the Advanced Hero Component in Discourse. WorldIsMine reports the issue, initially suspecting a URL problem, but later resolves it by removing .git from the repository link. Moin suggests the issue may stem from compatibility with the current Discourse version, particularly due to the component’s reliance on a specific commit in .discourse-compatibility that doesn’t exist in older versions like 3.5.1. tobiaseigen confirms the fix works without .git and recommends checking the site’s update status. RGJ highlights that the compatibility file references a non-existent commit, likely due to the component being forked without preserved git history, making it incompatible with older Discourse versions.
Hello, for my part I had no problem installing the component.
If you install the component manually with the repository
Does that not work?
I just tried installing it and it worked, without the error you see. Are you using the correct URL to the github repo? Should be
https://github.com/thebestgoodguy/vibecommit-hero.git
It might be due to your Discourse version and the fact that when the versatile banner component was adopted, the compatibility file was not cleared. I suspect that the commit specified there for your version cannot be found in the current repository because it belongs to the versatile banner.
The .git at the end of the URL is what fixed it! Thank you!
Looks like you created a new theme. You’d need to select “from a git repository”. But I guess that will fail
I also just tried it again without the .git at the end, and it still works on my end.
So yes looks like Moin may be on the right track with her advice. Have you updated your site to latest? Do you have another component already installed that is conflicting?
The error handling is fairly attrocious here - would be nice if a better error message could be shown! 
Can you check if more/better info about what is going wrong is appearing in the javascript console?
Yes I tried on our staging where we have 3.5. Perhaps it’s the versatile banner we have that’s causing conflict. Either way, thank you everyone for help.
Let us know if that works. I will shift this to a new Support topic so we can tie it off.
There is an error in .discourse-compatibility
< 3.6.0.beta1-dev: 9f248e18b35e4cf599e35a871e9348957077e7c6
That commit does not exist so it does not install on 3.5.1 stable.
That’s what happens when you “fork” something but throw away all git history.
(EDIT I see that’s basically what @moin said)