Tried to update one of our websites and got this error:
Fatal error: Uncaught exception 'Httpful\Exception\ConnectionErrorException' with message 'Unable to connect to "http://arastta.io/core/1.0/update/1.6.2/5.6.26/5.5.57-cll": 28 Operation timed out after 30000 milliseconds with 5735729 bytes received' in /home/whitewaterhoney/public_html/system/vendor/nategood/httpful/src/Httpful/Request.php:1028 Stack trace: #0 /home/whitewaterhoney/public_html/system/vendor/nategood/httpful/src/Httpful/Request.php(204): Httpful\Request->buildResponse(false) #1 /home/whitewaterhoney/public_html/admin/model/common/update.php(281): Httpful\Request->send() #2 /home/whitewaterhoney/public_html/admin/model/common/update.php(75): ModelCommonUpdate->downloadUpdate('core', '1.6.2') #3 /home/whitewaterhoney/public_html/admin/controller/common/update.php(99): ModelCommonUpdate->update() #4 [internal function]: ControllerCommonUpdate->update(Array) #5 /home/whitewaterhoney/public_html/system/modification/system/engine/action.php(74): call_user_func(Array, Array) #6 /home/whitewaterhoney/public_html/s in /home/whitewaterhoney/public_html/system/vendor/nategood/httpful/src/Httpful/Request.php on line 1028
Share this post:
Responses (7)
-
Accepted Answer
-
Accepted Answer
Lots of confusing writing ...
Simply comment those lines: https://github.com/arastta/arastta/blob/master/admin/model/common/update.php#l210-l233
PHP commenting: https://www.php.net/manual/en/language.basic-syntax.comments.php
Or better, add the never released fix manually: https://github.com/arastta/arastta/commit/f12f54ee887274832ce61ac124a07694eb105f38 -
Accepted Answer
Hi Ed,
This appears to have occurred again due to the "arastta.io" domain not being available perhaps due to the hosting not working. It is a little strange that this happened around the time the domain was due to expire however it has been renewed recently as can be seen:-
Domain:
arastta.io
Registrar:
101domain GRS Ltd
Registered On:
2015-04-05
Expires On:
2020-04-05
Updated On:
2019-04-05
Status:
clientHold
clientTransferProhibited
autoRenewPeriod
Name Servers:
ns11.arastta.cloud
ns12.arastta.cloud
It could be that the Internet needs to propagate with the "name servers" again since it fell over like last time, but it is possible to simply update a file to remedy the problem for the future too.
We do not believe you are likely to get any more updates as the development around Arastta seems to be a little lacklustre, so this feature is somewhat redundant.
Anyway, you can access the "admin" again by correcting the "URL" reference to "arastta.io" in the "update.php" file. To do this you will require "Cpanel" and "File Manager" or "FTP" access to your Arastta installation.
There is also an "error.log" under the "admin" folder in the root of your installation which may shed some light on this issue :-
Could not resolve host: arastta.io
PHP Fatal error: Uncaught exception 'Httpful\Exception\ConnectionErrorException' with message 'Unable to connect to "http://arastta.io/core/1.0/version/1.6.2/5.6.40/5.7.25/en-gb/1": 6 Could not resolve host: arastta.io' in
/system/vendor/nategood/httpful/src/Httpful/Request.php:1028
Stack trace:
/system/vendor/nategood/httpful/src/Httpful/Request.php(204): Httpful\Request->buildResponse(false)
/admin/model/common/update.php(242): Httpful\Request->send()
/admin/model/common/update.php(219): ModelCommonUpdate->getRemoteVersion('http://arastta....')
/admin/model/common/update.php(172): ModelCommonUpdate->getVersions(Array)
/admin/model/common/update.php(158): ModelCommonUpdate->getUpdates()
/admin/controller/common/header.php(152): ModelCommonUpdate->countUpdates()
The errors "snowball" a little, but you can certainly "login" again by modifing just one reference to "arastta.io" in file "/admin/model/common/update.php"
public function getVersions($addons = array())
{
$data = $this->cache->get('version');
if (empty($data)) {
$data = array();
// Check core first
$info = $this->utility->getInfo();
$base_url = 'http://arastta.io';
The last line is 215 in Arastta version 1.6.2 which needs to be a valid domain like "arastta.org" or probably any domain that is accessible.
In summary modify line 215 to this $base_url = 'http://arastta.org' to get logged back in again.
Possibly, it is worth then re-checking the "/admin/error.log" to see if there are any subsequent error messages.
Hope this helps.
Regards,
Hackasacka -
Accepted Answer
-
Accepted Answer
Hi Breck,
We wouldn't recommend using the new version on a clients site without first testing it. Wait and see if any glaring errors show up before considering using it.
Always backup before any major updates too.
If you download both Arastta ver 1.6.1 and Arastta ver 1.6.2 from https://github.com/arastta/arastta/releases.
Then extract both versions and do a directory and file comparison (you can also compare the contents of the files themselves).
Then do a clean install of both versions, preferably in the same environment (done seperately), to avoid even any path differences being confusing in the comparison.
If you have Control Panel access and PHPMyadmin you can export the MySQL database (it's only a text file) and either carefully look for differences or again use an application designed for or with a feature for file comparison.
This way you avoid any custom data you may later add confusing the comparisons at this stage.
Developer editors like Atom or Komodo Edit are free and can help here.
Hope this helps,
Regards,
Hackasacka -
Accepted Answer
Hi Breck,
Did you read the error message and try to understand it or perhaps the meaning was not obvious?
Fatal error: Uncaught exception 'Httpful\Exception\ConnectionErrorException' with message 'Unable to connect to "http://arastta.io/core/1.0/update/1.6.2/5.6.26/5.5.57-cll"
This part suggests a time lag with your Internet connection or the server you were trying to connect to (this is a quick guess).
Another, part of the error message:-
However, you may need to download Arastta ver 1.6.2 from "GitHib" "https://github.com/arastta/arastta/releases" to see the differences. It may be possible to manually update it yourself. It can only be files and database changes or possibly just one or the other? Arastta may confirm this or do a file and database difference check (lots of developer tools are capable of this function, sometimes called file compare too).
We have just tested the update and it was successfully updated. I would also check server permissions on your files on your server in case this is the cause. With your error message saying it could not connect it may be unlikely, but is often a problem.
Hope this helps.
Regards,
Hackasacka
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »