• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Service node is unknown for sysuser with id=0

steved13

New Pleskian
When I try and go into the website and domains tab I get

Service node is unknown for sysuser with id=0
SysUser.php
77
PleskUtilException

This was caused by changing the default domain name from www.mydomian.com to mydomain.com.
To compound matters going to the the website url now points to default/htdocs directory rather than mydomain.com/httpdocs.
mydomain.com/httpdocs does exist and if I run

select * from sys_users;
+----+---------------+------------+------------+-----------+---------------------------------------------+------------+-------+
| id | serviceNodeId | login | account_id | mapped_to | home | shell | quota |
+----+---------------+------------+------------+-----------+---------------------------------------------+------------+-------+
| 1 | 1 | xxx | 1 | NULL | /var/www/vhosts/mydomain.com | /bin/false | 0 |
+----+---------------+------------+------------+-----------+---------------------------------------------+------------+-------+

select * from ServiceNodes;
+----+---------+-----------+-----------------+-----------+------------+
| id | name | transport | remoteIpAddress | accessKey | externalId |
+----+---------+-----------+-----------------+-----------+------------+
| 1 | local | local | NULL | NULL | |


so to me it would seem half the move has been done. I have looked around on the net and not found anything that has really helped.
Any help would be greatly appreciated.

Thx

Steve
 
Usually this issue related to missing record in hosting table for domain. As possible workaround you can set htype value for domains to 'none' in domains table. After that you will be able to reconfigure domain.
 
Usually this issue related to missing record in hosting table for domain. As possible workaround you can set htype value for domains to 'none' in domains table. After that you will be able to reconfigure domain.

Sorted !

Thx very much I cannot tell you how much I appreciated this.
 
Back
Top