Answers.Body: <p>did you copy the <code>license.key</code> from your Mac environment to the Windows/Vagrant environment? Maybe deleting the <code>license.key</code> would help in this case.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-21T04:23:22.140Z
Answers.Text: Hi Denis,  
  Yes copied the `license.key` and tried deleting `license.key` and Craft still doesn't appear to recognise it's in a development environment.  
  
  Also deleted `/vendor` and `/storage/*` folders and did a `composer install` and still no luck.
Answers.UserDisplayName: Nick
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-07T10:02:44.307Z
Answers.Text: Experiencing something similar... Developed my project without issues, but once I moved to production and bought the license, all of a sudden dev environment started to bother about license... I'm puzzled.
Answers.UserDisplayName: Masiorama
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-20T10:21:16.980Z
Answers.LastActivityDate: 2020-02-20T10:21:16.980Z
Answers.UserDisplayName: Denis
Body: <p>I have a Craft CMS installed in a development environment thewebsite.test.  </p>
  
  <p>I can't get it to trial paid plugins and Craft Pro.  </p>
  
  <p>It appears Craft doesn't recognise it's in a development environment?</p>
  
  <p><strong>Application Info</strong></p>
  
  <ul>
  <li>PHP version  7.4.2</li>
  <li>OS version   Linux 4.15.0-74-ubuntu</li>
  <li>Database driver &amp; version    MySQL 5.5.5</li>
  <li>Craft edition &amp; version  Craft Pro 3.4.6.1</li>
  </ul>
  
  <p>I'm running Windows 10 with Vagrant/Homestead with Craft installed on a Virtual Machine in VirtualBox.</p>
  
  <p>The same setup on a Mac does not have any issues with licensing.</p>
  
  <p>I have copied the database and updated the .env file from the Mac install, and everything appears to be working except for the licensing issues.</p>
  
  <p>Is there any way to force Craft CMS to recognise a dev environment?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-02-21T04:41:26.173Z
Comments.Text: Are you able to load the "updates" page in the Craft control panel without any errors or issues?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-02-21T05:29:35.743Z
Comments.Text: Yes, can load the "updates" page in the control panel. No errors. Two updates available 3.4.7 and 3.4.7.1
Comments.UserDisplayName: Nick
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-02-21T20:22:36.920Z
Comments.Text: Well, now I'm confused. Can you shoot your `config/license.key` file over to support@craftcms.com and reference this SE post?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-20T09:41:50.690Z
Comments.Text: I never solved this. I instead switched to running Craft in DDEV instead and didn't have the issue. I suspect it may have been something in the vagrant stack combined with using GitBash WSL and the Untuntu VM. Somethings may have been run or installed in the wrong terminal/environment?
Comments.UserDisplayName: Nick
Tags: <craft3><license><windows>
Title: Craft CMS development licensing issues
ThreadText: # Craft CMS development licensing issues
  
  (Asked by: username_0 on 2020-02-20)
  
  I have a Craft CMS installed in a development environment thewebsite.test.
  
  I can't get it to trial paid plugins and Craft Pro.
  
  It appears Craft doesn't recognise it's in a development environment?
  
  **Application Info**
  
  * PHP version 7.4.2
  * OS version Linux 4.15.0-74-ubuntu
  * Database driver & version MySQL 5.5.5
  * Craft edition & version Craft Pro 3.4.6.1
  
  I'm running Windows 10 with Vagrant/Homestead with Craft installed on a Virtual Machine in VirtualBox.
  
  The same setup on a Mac does not have any issues with licensing.
  
  I have copied the database and updated the .env file from the Mac install, and everything appears to be working except for the licensing issues.
  
  Is there any way to force Craft CMS to recognise a dev environment?
  
  **Tags:** craft3, license, windows
  
  > **Comments:**
  > **username_1**: Are you able to load the "updates" page in the Craft control panel without any errors or issues?  
  > **username_0**: Yes, can load the "updates" page in the control panel. No errors. Two updates available 3.4.7 and 3.4.7.1  
  > **username_1**: Well, now I'm confused. Can you shoot your `config/license.key` file over to support@craftcms.com and reference this SE post?  
  > **username_0**: I never solved this. I instead switched to running Craft in DDEV instead and didn't have the issue. I suspect it may have been something in the vagrant stack combined with using GitBash WSL and the Untuntu VM. Somethings may have been run or installed in the wrong terminal/environment?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2020-02-20. Score: 1
  
  did you copy the `license.key` from your Mac environment to the Windows/Vagrant environment? Maybe deleting the `license.key` would help in this case.
  
  > **Comments:**
  > **username_0**: Hi username_2,   Yes copied the `license.key` and tried deleting `license.key` and Craft still doesn't appear to recognise it's in a development environment.    Also deleted `/vendor` and `/storage/*` folders and did a `composer install` and still no luck.  
  > **username_3**: Experiencing something similar... Developed my project without issues, but once I moved to production and bought the license, all of a sudden dev environment started to bother about license... I'm puzzled.  
  
  ---
  
  