Errors when try to manage services/plugins
Hi
I have two issues:
1. After database migration I can't remove Postgres Legacy plugins (ID 58c15418-e335-4560-a2b3-f01c2c7898a2)
2. I've created one more service today (ID: c85acf50-1f7e-41e2-b332-c8ba44e25550, service name: frontend). Having two environments, production and staging, I'm able to deploy changes to production but when I try to deploy to staging it fails with 404 error
Could you assist?
16 Replies
Project ID:
58c15418-e335-4560-a2b3-f01c2c7898a2,c85acf50-1f7e-41e2-b332-c8ba44e25550are you the owner of the project?
nope
you need to be the owner to delete plugins/services
ok got it. And what about the second issue?
where do you see the 404 error?
when deploy via github actions
my first thought is that you are using a very old version of the cli
or your service name is wrong
I've checked several times the service name - it is correct. About the CLI version - via CI/CD it always uses the latest version.
send your action file?
interesting: I've just tried to re-deploy it again - it faild and now I don't see the service in my staging environment
add the service back and then also specify the environment with the
--environment flag
and your RAILWAY_TOKEN is the project token, correct?The service persists in production and absent in staging. I tried to create a new one in staging, it came with some random name that I couldn't change. Previously all I had to do is to create service just once (in any environment) - it appeared everywhere and I was able to manage it
with --environment flag I gor the same error
sync the changes from prod to staging
hmmm... let my try
works!!! Thank You!!! I knew that I missed some small nuance
no problem!