acurl is deprecated, please update your build to use hut(1) instead
(among other things it will actually print a useful error message).
Relatedly, the most common reason why this is failing at the moment is
because of users who need to update their apex record (again):
https://srht.site/custom-domains
It's now 46.23.81.157, which should be stable in the long term.
On 24/01/18 10:30, Drew DeVault wrote:
>acurl is deprecated, please update your build to use hut(1) instead>(among other things it will actually print a useful error message).
It should be noted that for websites with more than a few hundreds of
files, hut could fail randomly.
A few people, like myself, where thus using acurl because it failed a
lot less (and, even, in the last months, started to work reliably).
I’m currently testing and managed to get hut to randomly work (which
never happened one year ago, so this is a clear progress). But it also
randomly fail. Maybe those failures will stop completely once the dust
settle. Crossing my findger.
>>Relatedly, the most common reason why this is failing at the moment is>because of users who need to update their apex record (again):>>https://srht.site/custom-domains>>It's now 46.23.81.157, which should be stable in the long term.
This should be put in flashing red letter for people, like me, who
thought they already had changed the IP. There was a temporary IP during
the outage, so it should be changed again.
--
Ploum - Lionel Dricot
Blog: https://www.ploum.net
Livres: https://ploum.net/livres.html
On Thu Jan 18, 2024 at 11:43 AM CET, Ploum wrote:
> This should be put in flashing red letter for people, like me, who > thought they already had changed the IP. There was a temporary IP during > the outage, so it should be changed again.
We're going to run a check against all sites to see if their apex record
is correct, and email affected users who need to update. The current IP
should be permanent; the previous IP was the temporary one (and we
communicated this when we disseminated it to users).