#action: publish:github Failed to push to repo

1 messages · Page 1 of 1 (latest)

vestal plaza
#

Here are you running your backstage instance locally or cloud ?

#

And I am getting error cannot read properties of undefined reading replace any issue you got like this

#

And the error you are getting is likely due to proxy issue

valid igloo
#

im running it locally, but there is no proxy configured. Repo is created in github, but pushing is failing

#

step 9,10,11 are ok

#

pushing in step 12 fails

#

and this is the default template of backstage :/

#

i think is something related with this :
By default, simple-get sets a 10-second timeout unless overridden. If the network is slow or the remote operation takes longer than expected, the request will fail with a timeout.

vestal plaza
#

Oh that stranger but I am getting the issue in publish:gitlab as it was working fine when I was using it locally but now the error persist when running it in aws

valid igloo
#

Sometimes the error might not be just from the Node client side:

Reverse proxy timeouts (e.g., Nginx, Apache, or a corporate proxy)
Load balancer (e.g., AWS ELB/ALB)
CI/CD environment (some CI platforms kill “frozen” steps after X seconds)

Make sure no upstream service is cutting off your request. Even if you raise the Node client’s timeout, a proxy or load balancer might enforce a shorter timeout.

vestal plaza
#

I am getting issue like cannot read properties of undefined reading replace and instancerepourl is not a type string but it worked Earlier perfectly

valid igloo
#

as i have seen, other problems also are shown as there are problems in yaml. i think if yaml/template was fine before, that its ok , just backstage address like is a problem of template but in fact can be another problem as i have seen. so no good reporting of problems lets call it so

vestal plaza
#

Yes

valid igloo
#

its strange for me because every time, publish step execute for 12 seconds and then it terminates with that error

#

so its like somewhere this value is placed

vestal plaza
#

Yes exactly same for me it worked perfectly earlier locally
I don’t know if I need to add some additional thing in my docker file or config for it

valid igloo
#

i think if locally it still works fine , than its ok,
you need to double check if you have pass all parameters and env variables ok and then see that is blocking in aws