Why Meteor forced me to some random new portal (Metal?) where i’m not able to do most of the tasks. For example my latest deployment is not visible there.
After 10 years, should i move away from Galaxy or what is going on there? Are most of users happy with that or not?
Hey iirokak !
I was a bit lost at first too, not gonna lie. I spent an embarrassingly long time wondering where my deployments had gone… and then I discovered the sidebar, which turned out to be a fairly advanced piece of technology 
More seriously though, what’s the goal of your post? You’re not really describing any actual problems or steps to reproduce, so how is the Galaxy team supposed to improve anything from that? 
I’ve personally noticed a couple of UI issues myself, some icon weirdness and button alignment issue. Instead of opening a vague complaint thread, I just took screenshots and sent them to the Galaxy team so they could fix them 
Same thing when I got an email saying one of my apps was about to be deleted, I contacted Galaxy support, and they replied within the hour saying it was resolved
It’s totally fair not to like the new Galaxy experience, especially when you have to spend time looking for things at first. But it would be much more useful to explain what’s actually broken for you rather than just opening a thread that basically says “this is bad"
well. most of the time when Galaxy announces they have changed something, something goes broken. Like notification bar ‘change your dns’ and when link was clicked, the link didn’t work.
Now to the “beta Metal galaxy”. Yes i see the deployment tab. I got email that version 472 was deployed. The email got link to old portal, which didnt work either. Then deployment page didn’t show that version but 10 days ago deployed version. No rollback to other versions either. Then there is a manual deployment button. When i press that, it sowed “version 421 failed” (very old version number). Those are just two bugs and i already sent several emails to support.
And to the point. My point is, that it looks that i am the only one who uses galaxy in Europe or why i am the only one who sees these bugs only when trying that Metal first time!! Who does the tests at all?
Hey @iirokak, thanks for the details, it helps.
To clarify each point:
On the EU comment: we actually have a large number of active users in Europe, Asia, and the US, and the vast majority migrated to the new platform without hitting any of these issues. That doesn’t make your experience less valid, but it does suggest something specific to your account or app rather than a widespread regional problem.
In fact, as @vikr00001 noted in Deploy to Galaxy Bare Metal: 40% Faster, the migration is already delivering real improvements for users. Deploy times dropping from ~10 minutes to ~6 minutes is a meaningful win, and that’s what this transition is about.
We’re already in contact with you through support and this is our priority today. Let’s keep the troubleshooting there, where we can dig into your account specifics. We’ll get this sorted.
i still have this problem. Just re deployed. And first re-deployment it said it was version V1. Second 472, third 473…
no deployed settings (settings.json) seen in galaxy 2.0. No app notifications … nothing.
I dont understand why they make this kind of changes that breaks everything. Perhaps this is something what they learnt from Microsoft or Apple. “hey let’s remove this button what everyone uses!”.
I am having the same issue, just tried a deploy via the CLI v680, reports all good but galaxy is not showing any changes. Its like its going into the void.
@wadebuildotto thank you! I’m not the only one. It looks no one have tested this before they moved customers here.
Yesterday oi got email ‘ stopped ’. No one in my org can stop that app but me! “For full details please visit your dashboard ”.
When i go to nyt beta portal i see that app is up and running and it has not been stopped.
Nice…
“We at Quave …” is coming guys, don’t worry. It is still dark in Brazil…
since this morning, I cannot do any new deployment, build succeed but when deploy to container, it always get:
…OCI runtime exec failed: exec failed: unable to start container process: exec: “node”: executable file not found in $PATH
I’ve reached out to the support, but apparently we live in different timezone.
Anyone with the same issue?
To be frank, if I was the CEO behind this process, I’d resign …
Alright, fair enough, since you summoned us @paulishca 
@iirokak if another pair of eyes would be useful on what you’re seeing, happy to help. Feel free to drop me an email at mario@quave.com.br with some more details and we can take a look.
No pitch, just leaving the contact here in case it’s useful.
I would love to feel the Metal benefits, but my deployments no longer work, and I don’t see any way to configure them in the UI.
Push to deploy was previously working with my deploy command. That configuration is now gone, and deployment fails because Metal runs its own scripts that seem to not be configurable anywhere.
I’m a bit frustrated at how this was handled, especially after having to go through all the trouble to get the app working in the old system, e.g.:
Now it is on Metal and it is all broken.
I don’t want to sound so critical, Meteor is a good framework, but I feel this Metal migration could have been managed better.
The migration should have been optional for a while, with a clear period of overlap having both the old and new systems, so that people could migrate and fix/report issues. It shouldn’t have been a hard switchover.
Right now, the way this was handled, people whose apps broke, they are stuck or forced to find a solution, and that is not great.
npm install is not allowed to be executed in my deployments, but that’s what the new Metal deployment is running out of the box, without any way to configure it:
I now need to work around the issue to get my deployments fixed.
Indeed Meteor is great as a framework. But Galaxy team should focus their job better.
Hey everyone, Henrique here (CTO).
First off, I hear you. Migrations are stressful, especially when your app is your livelihood and something that worked yesterday isn’t working the same way today. That frustration is completely valid, and I appreciate you sticking with us and taking the time to share what you’re seeing.
Quick update on the specific cases raised in this thread:
A couple of things I’d like to share, not as pushback, just so we can help you faster.
Please reach out through support rather than the forum. Forum posts can genuinely get missed. Chat or email is the fastest way to get your issue in front of the right people.
On the migration, we took this seriously. It was zero-downtime, tested extensively, and rolled out in phases (Free apps first, then AP, EU, US). Anyone who hit an issue and reached out through support was offered the option to roll back to the legacy platform while we worked on their case. That option is still available if you need it, though keep in mind the goal is to get your app migrated once we’ve sorted out the issues affecting it.
On edge cases, one of the things that makes Galaxy special is the sheer variety of Meteor apps running on it. People do genuinely creative and unusual things with this platform, and we love that. But it also means thorough testing won’t catch every configuration. When something works for thousands of apps but breaks for yours, it’s still broken, and we want to fix it. We just need to be in direct contact with you to do that.
Our team is small and the past few days have been intense. We’ve been working around the clock on every critical issue that’s come in and we’re not stopping until everyone is in a good place.
If you’re still stuck, reach out to support and reference this thread. We’ll take it from there.
Thanks everyone.
