Git Push To Remote Failing with a 400 Error

Wappler General Need Help
1

I'm trying to 'push to remote' (not 'publish') my recent changes to my Git account. The whole site 'publishes' fine but when I try to 'push to remote' it fails with a 400:

image

When I click the push to remote button in the GIT manager:
image

I get a 'pushing to remote' spinner and I can see network activity uploading the files, after about 4 minutes, once the files have uploaded I get the 400 error.

I cant really see a way to debug this, has anyone else had a similar issue?

This only happens on one site, other sites push and publish just fine.

2

A 400 status normally means that some parameters sent are wrong, did something change on that remote?

You can restart Wappler with logging enabled and send us the log.

How to report bugs together with the Wappler debug log - Wappler General / How To - Wappler Community

3

Many thanks @patrick - bug report submitted:

Its not a massive priority as the site has published OK but it would be nice to see what the issue is.

4

Seems to me like your credentials aren’t working for GitHub or maybe the stored authentication key just expired.

So just try to reauthorize by disabling and enabling the GitHub oauth in the Wappler global settings

1 Like
5

It looks like the problem is Wappler is deleting my Github settings, this was all previously working perfectly, when I went to see what the status was in the Git-Options section I saw this:
image

When I selected the 'connect to github slider above and entered my personal access token I get the following error:

image

I tried this a couple of times then the error above disappeared and my settings were saved.

I then tried another 'push to remote' and got the same error - when I went back to see my Github settings in Wappler global settings the 'connect to github' was de-selected and my personal access token was blank.

Let me know if you'd like me to PM you my error log

6

Update: I repeatedly de-selected the connect to GitHub option then restarted Wappler and selected, saved, then restarted Wappler again a couple of times and this has resolved the issue. Strange behaviour, hopefully a one off but I'll report back if it happens again..