I have used galaxy for 9 years… I have never in my 40+year life have seen so bad portal than galaxy beta. Even BBS boards had better ux.
Couldn’t add credit cards – saving just didnt work
Could use push to deploy - after 34 tries i my repository suddenly came visible and i was able to select it. However i couldnt deploy since it gives error “Failed to save app configuration: Something went wrong trying to initiate deploy for your app. Please, try to save the configuration again or try to do a commit to your repository.”
And when adding new user to galaxy, it says some general error… had to see debug console and it says “user does not exist”.
Please tell me there is new portal coming, the old one was working just fine. If Galaxy sucks later i will move to zcloud, scalingo or heroku. Bye bye.
Could someone tell me what is your life with galaxy beta? How you were ablet to
I had some issues with the push to deploy button as well. I assume there was a migration issue with the new galaxy. If you contact support they will sort it out for you. Same with the card prioblem.
Hey @iirokak, I’ve responded to your tickets, and we’re actively fixing these problems.
We couldn’t reproduce the bugs at first, but after more testing, we found the deployment issue. A fix will be in production soon. Our team is prioritizing the other issues.
The app management on the old Galaxy still works, so you can continue using it until we complete the new beta.
If anyone else is experiencing issues, please share them here or preferably submit tickets, which is the most effective way for us to track and resolve problems.
@fredmaiaarantes i don’t know but suddenly yesterday this happens. (Using diffrent borwser, different network, even using only mobile phone) only this loading screen is visible in old galaxy. I also sent you support ticket about this. So suddenly i cannot access old galaxy anymore … and push to deploy forwards me to new buggy galaxy… Could you check that ticket too?
Indeed, why is paying customer forced to use beta?
Setting push to deploy for new app or configuring existing broke for me last year, see the picture below.
Also why do I have to change account from personal account to company account and region to Europe every single time I login to beta site?
Does it still work? (it comes up with the users/orgs for me).
Via the command line, I was able to start a deployment of a random starter app on my personal account, I just forgot to set the MONGO_URL so the deployment failed.
Hey @iirokak, I know this disruption was frustrating, and I sincerely apologize for the inconvenience caused.
Our team has identified and fixed the root cause, a database synchronization issue affecting recently created organizations. We’ve fixed the data mismatch, but our automated synchronization system accidentally reverted these fixes, prolonging the issue. We’ve confirmed that other clients who experienced similar problems are now successfully deploying their apps.
Our support team reached out via chat a few hours ago, and we’re awaiting your feedback to ensure everything works for you.
As humans behind this platform, we take these incidents seriously. Our team worked tirelessly to resolve the problem, and we’re implementing additional measures to prevent similar incidents in the future.
We’ll continue monitoring your case closely and await your feedback on the deployment retry.
