Hi Manuel,

I’ve the same problem with curl. It should be noted that use of curl to 
update a website has been deprecated in favour of the custom "hut" tool.

So you may try te replace the curl commands in you build.yml by 
something like:


hut pages publish site.tag.gz -d $mydomain  


Historically, hut was not working for websites with more than a few 
hundreds of files (this bug was acknowledged at the time) so people like 
me where forced to use curl (which was very slow but sometimes worked, 
sometimes not).

One of the discussion can be found here :

https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3C166962587213.7.17616914652932105630.79592835%40ploum.eu%3E


With the new infrastructure, I should add that I’ve managed to get hut 
to work at least once ! (very stlow but it worked, yeah!) While I have 
the 400 error for curl, like you.

I’m still testing to see if hut is working reliably or if the success 
was a one time off.

NOTE: if you have an APEX domain (root domain), you should change the 
DNS to point it to :  46.23.81.157  

(check the IP, this is not the IP that hab been communicated previously. 
This is the second change)

-- 
Ploum - Lionel Dricot
Blog: https://www.ploum.net
Livres: https://ploum.net/livres.html

Thank you Drew and thank you Lionel for the quick reply.

I updated the DNS record as instructed and updated my build manifest to
use hut instead of acurl. Everything works now.


All the best.

-- 
Manuel Uberti
https://manueluberti.eu