External Publication
Visit Post

Wrongful error: (my site) "is already assigned to an account and in use on another account."

InfinityFree Forum [Unofficial] June 19, 2026
Source

Hi there,

Welcome to the forum!

This error usually happens because the system detects mayabeaming.com is already linked somewhere on the shared network infrastructure. Since you mention you own both domains, the fix is likely very simple depending on where it’s currently sitting:

1. Check if it’s already an “Addon Domain” on your current account

Sometimes people accidentally add the domain as an Addon Domain first. In the VistaPanel/Control Panel, an Addon Domain gets its own folder, which prevents you from adding it a second time as an Alias/Parked Domain.

  • The Fix: Go to your control panel, look under Addon Domains , and if mayabeaming.com is listed there, delete it. Once removed, go back to Parked Domains (or Aliases) and try adding it again.

2. Check the InfinityFree Client Area (Highly Recommended)

Instead of using the older Control Panel menus, it’s highly recommended to use the main InfinityFree Client Area Dashboard.

  • Go to your account in the client area and look at the Domains list. It will show you exactly what status the domain currently has.
  • If you try to assign/change it there, the client area will often give you a much more specific error telling you exactly which account or folder is holding it up.

3. Did you host it elsewhere recently?

InfinityFree shares a backend network with iFastNet and other resellers (like ProFreeHost or old ByetHost accounts). If you ever added mayabeaming.com to a different hosting provider or an old, separate InfinityFree account in the past, you must log into that specific old account and completely delete/unlink the domain from it first. Removing nameservers or letting the account go “inactive” doesn’t release it from the system.

Give the Addon Domain check a try first! If you are certain it isn’t listed anywhere on your current account, let us know so an Admin can look up the backend data to see where it’s stuck.

Discussion in the ATmosphere

Loading comments...