Search Engine: Elastic

Article ID: 113089, created on Jan 6, 2012, last review on Jun 23, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5


With some clients and domains, Plesk was registered in OBAS. After yhe node synchronization, the clients and their domains appeared in Conflicts Resolver under the Not Registered tab.

Domains owned by Plesk admin are missing in OBAS. Why?


After Plesk is registered in OBAS, the latter is considered a management tool for Plesk: clients and domains should be created/managed through OBAS only. If they were created through Plesk, the clients and their domains appear in Conflicts Resolver during the next Plesk node synchronization. The Provider can resolve the conflicts by going:

PCC > Top > Migration Director > Conflicts Resolver > Plesk Domains {Plesk Clients} > Resolve

This will create new subscriptions and register Plesk domains and Plesk clients in OBAS. Plesk admin is not considered a client by Plesk:

[plesk@node ~]# /usr/local/psa/bin/client --info admin
 User admin is not a client
[plesk@node ~]#

Because Plesk admin is not considered as a client, Plesk admin and all domains owned by admin do not appear in OBAS Conflicts Resolver.


To register domains owned by Plesk admin you need to create a new client in Plesk and assign the domain to that client.

This new client and his domains will then appear in OBAS Conflicts Resolver (under the Plesk Client and Plesk Domain tabs).

The Provider can resolve the conflicts to register the client and domains in OBAS.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 624ca542e40215e6f1d39170d8e7ec75 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF