# problem upgrading to VM Pro

**URL:** <https://forum.virtualmin.com/t/problem-upgrading-to-vm-pro/35025>\
**Category:** Help! (Home for newbies)\
**Created:** [November 26, 2009, 3:39am UTC](https://forum.virtualmin.com/t/problem-upgrading-to-vm-pro/35025 "2009-11-26T03:39:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![midol](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/m/e56c9b/32.png) [@midol](https://forum.virtualmin.com/u/midol)\
**Post date:** [November 26, 2009, 3:39am UTC](https://forum.virtualmin.com/t/problem-upgrading-to-vm-pro/35025/1 "2009-11-26T03:39:54Z")

</div>

When trying to upgrade VM GPL to VM Pro under Centos 5.4 I get:

Error   
Failed to upgrade to Virtualmin Pro : Virtualmin has been installed from an RPM, but not using the Virtualmin GPL repository. Upgrading is not possible at this time.

eh?

---

<div class="post-metadata">

**Author:** ![Eric](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/e/898d66/32.png) [@Eric](https://forum.virtualmin.com/u/Eric)\
**Post date:** [November 26, 2009, 5:14am UTC](https://forum.virtualmin.com/t/problem-upgrading-to-vm-pro/35025/2 "2009-11-26T05:14:56Z")

</div>

How did you go about installing Virtualmin GPL?

I’m assuming you’re on CentOS – do you have a file named /etc/yum.repos.d/virtualmin.repo?

If so, what are it’s contents?

-Eric

---

<div class="post-metadata">

**Author:** ![midol](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/m/e56c9b/32.png) [@midol](https://forum.virtualmin.com/u/midol)\
**Post date:** [November 27, 2009, 12:15am UTC](https://forum.virtualmin.com/t/problem-upgrading-to-vm-pro/35025/3 "2009-11-27T00:15:50Z")

</div>

well, it was installed a year and a half ago and I’m not sure how I went about it, I think I used the install.sh file and it just happened automagically.

Centos 5.4 and

yes, like this:

[root@cserver yum.repos.d]# ls -l  
total 28  
-rw-r–r-- 1 root root 2245 Oct 1 05:28 CentOS-Base.repo  
-rw-r–r-- 1 root root 626 Oct 1 05:28 CentOS-Media.repo  
-rw-r–r-- 1 root root 626 Mar 16 2009 CentOS-Media.repo.rpmnew  
-rw-r–r-- 1 root root 954 Apr 25 2008 epel.repo  
-rw-r–r-- 1 root root 1054 Apr 25 2008 epel-testing.repo  
-rw-r–r-- 1 root root 922 Dec 19 2008 pgdg-83-centos.repo  
-rwxr-x— 1 root root 440 Nov 25 19:33 virtualmin.repo.rpmsave

[root@cserver yum.repos.d]# cat virtualmin.repo.rpmsave  
[virtualmin]  
name=Red Hat Enterprise $releasever - $basearch - Virtualmin  
baseurl=http://–obscured–@software.virtualmin.com/rhel/$releasever/$basearch/  
enabled=1  
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin  
gpgcheck=1

[virtualmin-universal]  
name=Virtualmin Distribution Neutral  
baseurl=http://–obscured–@software.virtualmin.com/universal/  
enabled=1  
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-virtualmin  
gpgcheck=1

Dave

---

<div class="post-metadata">

**Author:** ![Eric](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/e/898d66/32.png) [@Eric](https://forum.virtualmin.com/u/Eric)\
**Post date:** [December 2, 2009, 1:53pm UTC](https://forum.virtualmin.com/t/problem-upgrading-to-vm-pro/35025/4 "2009-12-02T13:53:12Z")

</div>

Hrm, the .rpmsave extension of your virtualmin repo file might be causing trouble.

Does it help to rename that from “virtualmin.repo.rpmsave” to “virtualmin.repo”?

-Eric

---

<div class="post-metadata">

**Author:** ![system](https://cdn.forum.virtualmin.com/uploads/default/original/2X/c/cd96d761e326db4b2bef94886a639109bd7a8e76.svg) [@system](https://forum.virtualmin.com/u/system)\
**Post date:** [April 30, 2020, 5:32am UTC](https://forum.virtualmin.com/t/problem-upgrading-to-vm-pro/35025/5 "2020-04-30T05:32:18Z")

</div>

Closed on April 30, 2020, 5:32am UTC