Payment successful
jntcloudcod2019
HOBBYOP

a year ago

My payment was successful, but you still have my services offline. I need it urgently and I want my services activated immediately.
Solved

9 Replies

jntcloudcod2019
HOBBYOP

a year ago

Segue o comprovante

Attachments


a year ago

Try redeploying your services


jntcloudcod2019
HOBBYOP

a year ago

Fiz o redploy da aplicação e ainda assim estou com problemas e não tivemos nem uma aletração nos projetos

Determining projects to restore...

All projects are up-to-date for restore.

/src/Services/AutentiqueService.cs(18,5): error CS0106: The modifier 'public' is not valid for this item [/src/Lambda.Pregiato.csproj]

/src/Services/AutentiqueService.cs(85,2): error CS1513: } expected [/src/Lambda.Pregiato.csproj]

Build FAILED.

/src/Services/AutentiqueService.cs(18,5): error CS0106: The modifier 'public' is not valid for this item [/src/Lambda.Pregiato.csproj]

/src/Services/AutentiqueService.cs(85,2): error CS1513: } expected [/src/Lambda.Pregiato.csproj]

0 Warning(s)

2 Error(s)

Time Elapsed 00:00:02.17


a year ago

Please try to communicate in English if possible!

That error seems code related, are you using your own Dockerfile or using a Railway builder like Nixpacks or Railpack?


jntcloudcod2019
HOBBYOP

a year ago

There have been no changes to the application code or any service configuration. After you disable my services due to payment issues, these issues will start to appear.


echohack
EMPLOYEE

a year ago

Hey Jonathan,

I'm seeing that your subscription is active, which is good for the original issue you raise. Let me look at your application issues to see if we can help.


Status changed to Awaiting User Response Railway about 1 year ago


echohack
EMPLOYEE

a year ago

I'm seeing successful deployments for all your Services. Could you go into more detail on the issues you're seeing now?


jntcloudcod2019
HOBBYOP

a year ago

Look, I redployed a version that worked. However, I believe that this would be inconsistent knowing that the last version that was deployed was working correctly. You need to review this process of deactivating a service because it caused me a lot of headaches. My services are accessed daily by multiple users.


Status changed to Awaiting Railway Response Railway about 1 year ago


echohack
EMPLOYEE

a year ago

Sorry about the headaches jntcloudcot2019. If you don't have an active subscription, we can't serve your Services. You can always simply redeploy them, should an interruption occur.


Status changed to Awaiting User Response Railway about 1 year ago


Status changed to Solved echohack about 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...