It appears that the issue is caused by a bad PHP update from an upstream vendor. A fix for this is being made, and we expect this to be ready and installed in the next 48 hours.
Just to remind everyone: we are aware of the issue, and we are working to fix it.
Please have patience while the fix is being prepared and deployed.
And please only reply to this topic if you have useful information or a relevant question. Simply stating that you are also experiencing the issue is not helpful, so such replies will be flagged and removed.
Hi @Admin Since It’s been four days since the initial outage, can we get an update on this? Thanks!
I have just asked iFastNet for an update.
Unfortunately, it seems that the fix that should be released has not been released yet. The plan right now is to wait for another 48 hours for the fix to be released. After that, we may be forced to roll back the PHP update. However, we hope to avoid that, as it may be painful.
Unfortunately, the fix has still not been released, so iFastNet is going to proceed with the rollback. This is scheduled for tomorrow.
So this mean the best option for us the (Users) is to take backup on our site is that correct?
Having a backup is always a good idea, but is not necessary for this by any means. The only thing that will be rolled back is the PHP version that’s installed. Your website files will not be rolled back (we don’t have any way to do so in the first place). At worst, it may result in some downtime for websites, but I see no reason to assume that the data of your website is not completely safe.
The rollback has been completed! All servers have been reverted to a PHP version that does have the right GD settings. All usual GD functions should now be available again.
Dont know why, I still get the error page. Is there anything I must do?
What is your domain name? Where do you see this issue?
Geek-road.ch
have this issue when try to connect my cjdropshipping account to my woocommerce.
What do you see exactly?
nevermind, problem solved… my error!
Is that error listed in the original announcement? If not, then you can assume it’s not related.
If you want help with any other error, then please create a new topic about it. If it turns out that it does have an underlying cause related to a known issue, we can find that out. But then we keep the topic about the outage about the outage, and not about unrelated issues that happen to occur around the same time.
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.