• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

An error occured during getting domain information

S

serg3263

Guest
Environment: FC2, PLESK-7.5.4

When I run PLESK command line utility

#./domain.sh -i <DomainName>

I get error message
----------------------------------------------------------------
An error occured during getting domain information: Can't print report for domain:

#
----------------------------------------------------------------

Message does not contain <DomainName>.


Q1: What can cause this problem?

Q2: Whare can I find PLESK diagnostics info such as logs?
 
You must log in or register to reply here.

Similar threads

T
Resolved FTPS remote backups fail after upgrade to Plesk 18.0.80 due to TLS session not being resumed on the FTP data connection (pmm-ras regression)
2
Replies
21
Views
30K
Sebahat.hadzhi
Sebahat.hadzhi
P
Resolved Smart Update fails during "Analyzing the test site before updating it" at 10%
Replies
2
Views
3K
Peter van der Kleij
P
P
Smart Update - wp-admin not working after update
Replies
1
Views
6K
Sebahat.hadzhi
Sebahat.hadzhi
S
Resolved Monitoring shows errors 'Dashboard not found' or 'An unexpected error occurred'
Replies
2
Views
3K
Sascha Schlüter
S
F
Issue Plesk Backup Suddenly Fails on SSHFS: pmm-ras Returns EPERM After Years of Working
Replies
6
Views
4K
FloLa
F
Back
Top