Hello,
I am using shared hosting account for a website running backdrop. For the past month updates have not run - scheduled or manually. I get the following error:
HTTP request to https://updates.backdropcms.org/release-history/backdrop/1.x?site_key=rd... failed with error: Connection timed out.
I contacted support pointing to the possible IPv6 check here: https://forum.backdropcms.org/forum/error-when-trying-check-updates
Support responded:
When I use this from cpanel under the terminal section -- curl -6 https://updates.backdropcms.org/release-history/backdrop/1.x to test ipv6 connectivity from the server to that subdomain. I was able to do so without issue so I believe your issue may be something else.
Not sure what I need to do next if I can't run updates. Would appreciate any advise/suggestions.
Comments
So tried accessing the updates.backdropcms.org server again and tech support said:
Hello,
It looks like outside of the server that host isnt accessible currently --
I tried from a separate network on my end and got the same...that IPv6 IP is unreachable to anyone.
---
Then I just tried now and updates worked again. On two separate backdropcms websites.
This has happened intermittenly before but never not available to run updates for this long.
My hosting is located in a country that blocks numerous online resources, so I am not surprised that updates and modules are unavailable. However, everything works perfectly on a local server with a VPN.
The issue with checking for updates in the BackdropCMS dashboard makes website development and maintenance more difficult. I manage more than ten websites hosted by two different providers, one of which is affected by this issue, I decided to investigate.
After contacting my hosting provider support, I found that attempting to open https://updates.backdropcms.org results in a 403 error (access denied). However, another hosting provider in the same region does not have this problem. The conclusion: requests from certain IP addresses are being blocked.
I sent a description of the issue, including the hosting provider IP address, via https://backdropcms.org/contact and received a reply on September 11: “We’ll look into what we can do on our end.” To this day, the problem persists.
I ask everyone who has encountered this problem to support this topic to increase the likelihood of it being resolved. If there are people involved with the BackdropCMS infrastructure, perhaps you could influence this issue. Thank you.