Hi,I can not publish application In my personal environment. Environment Health screen show "The service 'Deployment' could not be reached.".
Go to services (type services.msc in run and enter) find the service by its name and start it after that try again.
In a cloud personal environment you cannot start the environment services using Pramod suggestion.
Can you confirm if you still have this problem? Can you publish on your personal environment?
I still have this problem.
I can not publish on my personal environment.
We have been able to mitigate the issue.
Can you confirm if you can now publish in your personal environment?
Thank you for your patience and understanding.
I tried to publish, but same error has occurred. I still can not publish on my personal environment.
Thank you for your feedback!
We have restarted the service and we have also performed some checks in the system. We currently can't find any issue and all services are running again.
Can you try to publish first another application (test application) than the one you're trying to publish, just to rule out some issue in the application itself? Then, you can remove the test application and try to publish the one you have been trying before.We will be waiting for your feedback.
Thank you for your help.
I tried to publish test application and the one I have been trying before, and I succeeded in publishing them in my personal environment.
The problem was solved.
Hello Yasuharu,Great news, thank you for your feedback!We are glad the problem is solved.
Hello, I have the same problem, I have try the hole day to use the platform but the error persists.
Could you tell me how to solve it?
Thanks, the provem is solved now, it was a platform component that was unavailable.
I have the same problem. Could you fix it for me too please?
Ricardo Martins wrote:
Hello, I'm having the same problema in my environment, can you please help me? I'm in a training program and got stuck with this problema.
Pedro Figueiredo wrote:
Can you check if the problem persists?
Hello, I have the same problem with my environment corner.outsystemscloud.com. I have tried several publishes this morning but the error on the deployment server persists.
Is there a resolution available?
Miguel João wrote:
the problem was solved.
I don't want to turn this into the official "My personal environment's deployment service is down" thread, but since I don't know a better way to warn OutSystems about this, here it goes:
My deployment service is down on wodify-test.outsystemscloud.com. Error message is "Error deploying eSpace 'ClientsExercise' in PRS68673LT97852".
I'm facing the same problem, can anyone help me?
I also have the "Deployment service is down in front-end SERVER" problem.
How do I go about getting the service restarted?
Thabo Sibeko wrote:
Can you please check if you still have the problem?
António Marques wrote:
same here, deployment service down on bruis.outsystemscloud.com. Have sent some feedback yesterday but no answers so far. Please provide some feature within the personal environment so we can restart services ourselves. But now for this time help me,
Regards and thanks
Hello, I had the same problem and got stuck all day.. I`m not sure how to fix it, It might be the problem with a platform component but I didn`t keep track of the ones I installed.
Thank you for bringing this issue into our attention.
Unfortunately, on Personal Environments (PE) this is something you cannot act upon, our support will handle the issue briefly.
Taking the opportunity, we have recently enabled PE users to open support cases especially considering these situations.
At the moment, you already have a case registered there to tackle this issue :)
We'll try to be as brief as possible.
Ana Martins wrote:
Obrigado pela rápida resposta Ana!
Vou aguardar então, só queria ter certeza de que vocês já estavam cientes do erro.
I have just found this thread, after having the same issue with my PE, for a few days. I had hoped to work on my programing this weekend but can't continue.
Is there a fix for it?
Lee Hammond wrote:
We have restarted the service and everything seems to be ok.
Please test it again and confirm if everything is ok?
Pedro Luís wrote:
Thanks for the reply, Pedro.
I am still seeing the 'Deployment failed' error, when I try to publish. Full error is shown below.
I am only testing the web app training module, so it is very simple!
If I try to load another app in Chrome, that was previously working, I am now seeing 'http error 503' service unavailable.
Error message from node SERVER (127.0.0.1): Deployment failedDeployment failed. Could not invoke ping. Exception: The remote server returned an error: (503) Server Unavailable. at System.Net.HttpWebRequest.GetResponse() at #tBc.#RBc.#1Bc.#UBc(String espaceName, String ptaOrTenantName)CompModule : Broadcast Message
Hi OutSystems Developers and enthusiasts!
As a part of our continued efforts to provide you the best experience and availability on Personal Environments, OutSystems has revamped the support experience for the free offer.
So, whenever you experience issues with the Deployment Service, with any of the following symptoms:
Let us know by opening a support case for your Personal Environment.
1. Access OutSystems Support Center
3. And let us know your concerns:
4. Choose your Personal Environment's Infrastructure:
5. Confirm, and that's it!
OutSystems most dedicated staff will act on it as soon as possible and will personally inform you!
Happy low coding!
Thanks Ana. I did submit a case two days ago. I received a reply in this thread, which is why I continued the conversation. I have just submitted another support case.
Clearly I am not alone in seeing this issue. It is frustrating for me as a training beginner.
When we submitted this post your case had a prompt response.
We will always answer as soon as possible and we are sorry for the time the first case took.
But this new feature came exactly to change that, and we will improve our response times in a very near future!
Opening a new case won't speed up the process, so check your inbox and give your environment another try ;)