<p>I am getting the following error when trying to update Craft from 3.3.18.4 to 3.3.19 and any version after. It seems like Homestead or Vagrant is having some sort of issue with IpValidator or the Class 'Yii'. Anyone else seen this issue before?</p>

<pre><code>Fatal error: Uncaught Error: Class 'Yii' not found in /home/vagrant/****/****/vendor/yiisoft/yii2/validators/IpValidator.php on line 218

Error: Class 'Yii' not found in /home/vagrant/****/****/vendor/yiisoft/yii2/validators/IpValidator.php on line 218
</code></pre>

CC BY-SA 4.0
2020-03-05T07:16:35.157Z
Can you set your `craftcms/cms` to `3.3.19` in your compser.json file, then run `composer update` from your project's root and try again?
Brad Bell
CC BY-SA 4.0
2020-03-05T22:10:10.677Z
Have tried that already. Still the same error. It was able to get it working when using MAMP but not Homestead.
kayq
CC BY-SA 4.0
2020-09-09T19:00:56.467Z
Did you ever get this to work? I'm having the same issue when upgrading 3.3.15 to any other version, running with docker.
jishi
<craft3><yii>
Yii2 2.0.31 in Homestead errors
# Yii2 2.0.31 in Homestead errors

(Asked by: username_0 on 2020-03-04)

I am getting the following error when trying to update Craft from 3.3.18.4 to 3.3.19 and any version after. It seems like Homestead or Vagrant is having some sort of issue with IpValidator or the Class 'Yii'. Anyone else seen this issue before?
Fatal error: Uncaught Error: Class 'Yii' not found in /home/vagrant/****/****/vendor/yiisoft/yii2/validators/IpValidator.php on line 218

Error: Class 'Yii' not found in /home/vagrant/****/****/vendor/yiisoft/yii2/validators/IpValidator.php on line 218

**Tags:** craft3, yii

> **Comments:**
> **username_1**: Can you set your `craftcms/cms` to `3.3.19` in your compser.json file, then run `composer update` from your project's root and try again?  
> **username_0**: Have tried that already. Still the same error. It was able to get it working when using MAMP but not Homestead.  
> **username_2**: Did you ever get this to work? I'm having the same issue when upgrading 3.3.15 to any other version, running with docker.  

---

## 0 answers

