Backup (Not finished)

Very interesting, @jpegtobbe, @cbrendlinger . Turns out the cURL version on my server is also 8.10.0 OpenSSL/1.1.1w. I’ll forward that to my host admin and see if he will implement that patch.

@cbrendlinger Its different PHP 8-versions on the different site on that host. I think they have used the same Curl on all of the php 8.x servers.

My cURL version is: 8.10.0, OpenSSL/1.1.1w and PHP version: 8.2.22 (Supports 64bit values)

• This reply was modified 2 months ago by wpdv.

Hi,

There is an issue with this particular version of Curl, you will need to ask you hosts to install this patch: https://github.com/curl/curl/pull/14895

@vupdraft maybe easier if you fix the plugin code! Else this problem might take long time before it’s patched everywhere

@vupdraft, my host is refusing to patch the cURL which is totally blowing my mind but they keep saying that it is the responsibility of the plugin developer and it should not require a change to the operating system.

@cbrendlinger curl is patched because the default way was changed between versions, don’t think that was what curl intended. If the host possible want a lot of support questions from their customers then they don’t patch ??

My host have 300 000+ customers and they patched right away.

• This reply was modified 2 months ago by jpegtobbe.

Hi @jpegtobbe

Thank you very much for your help identifying the issue with Curl.
I have informed the developers and they will now review this issue.

Best regards,

Nick

@cbrendlinger if you are still looking for new hosting check out Mojohost. They a e stellar when it comes to support and implementing patches needed.

@jpegtobbe @cbrendlinger

The problem is that the issue is not with the plugin it’s with the Curl version

The new?eos_sent?flag was not reset on a?curl_easy_reset(), causing the HTTP/2 EOS flag to be missing in certain situations and having the server request processing hang waiting for it.

It’s pretty bad form your hosting not to update if there is a know issue (especially if there is a well documented fix)

This is also not something that just affects UpdraftPlus.

@cbrendlinger, wondering if you tried again with HostGator? I also have a dedicated server and I’m having trouble even getting support to understand what I’m talking about. Do you typically contact first level support for dedicated server or do you get to work with someone higher up? Who denied your request? Maybe if enough of us contact them, we can get it updated?

@laalpert1, I contacted HostGator again in the hopes that a different support specialist would be able to help. Again, I could not get them to apply the patch but they said that my cURL version differed from the one showing on the Site Health screen. Also, full disclosure, my PHP version is a little older because there were issues when I tried to upgrade. They are insisting I have to upgrade the PHP version but I have no confidence that doing that will make any difference with this problem and I doubt that they will apply the patch even if I do. I still do not understand why the UpdraftVault works for me while DropBox doesn’t. Sorry I cannot be of more help.

@cbrendlinger If you have Vault you will need to get support here: https://updraftplus.com/paid-support-requests/

I suspect that updating your php version won’t fix the issue but did you hosts say why the health screen is showing a different Curl version? – That’s odd.