Recent content by serreri

Hello everyone, I have always noticed that if you change the ssh port in /etc/ssh/sshd_config eg: from port 22 to port 22xx if you then log in to SSH Terminal of plesk after having changed the port from 22xx to port 22 again then an infinitely repeated error occurs: ssh: connect to host 127...

Thanks Kaspar, unfortunately I was convinced that I had at least two languages available in the Plesk license, I had to purchase the language pack to add a language. I don't understand why in the license plesk Web Pro Edition I have two languages installed, while in the Web Host Edition license...

Good morning, I apologize but I couldn't find a solution. Could you kindly help me understand if it is possible to activate a Plesk customer account by setting the language based on the language spoken by the customer. Basically, I would like an English user to enter his profile and find his...

TITLE Possible problem with password recovery with incorrect email PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian v18.0.60_build1800240421.18 os_Ubuntu 22.04 PROBLEM DESCRIPTION Hi everyone, I couldn't find any posts regarding my question. I am using Web Host Edition and...

So I can confirm that by creating X-API-Key via the SSH command by also entering the ip of the server plesk bin secret_key -c -ip-address 00.000.000.000 the curl script present on the server returns error 401: The requested URL returned error: 401 Unauthorized Whereas if I create the key...

the script is launched from my site inside my server, so same Ip. I will try again to regenerate the key from root and use it in my php script always inside my server, maybe I made a mistake the first time. Thanks

The ip used is that of my server and was generated in SSH with the command plesk bin secret_key -c -ip-address xx.xxx.xx.xxx -description "Key" but when I use the key in the curl I get the 401 message again. Probably the generated key is a root key and is not accepted in the site pages. Maybe...

Ok I solved it in part: Using API-Key generated in SSH (plesk bin secret_key -c -ip-address xx.xxx.xx.xxx -description "Key") the curl returns "error: The requested URL returned error: 401 Unauthorized" At this point I created my API-Key directly in my php page: curl_setopt($ch, CURLOPT_URL...

Unfortunately, nothing changes, I get no results. I also tried to generate errors by changing the key but nothing happens. Yet this script should work. DeepL Translate: I always use it apologize for any mistakes

Hello everyone. I generated my Api-Key in ssh and the generated key works perfectly in the Plesk REST API page, where I can to read and create the clients. I am using a curl script I found on this forum that is supposed to be working but on my server I can't get it to work. The code is this...

Thank you very much Peter The talk about bandwidth consumption for monitoring then would justify the delays on the checks. I also noticed this error message: "the hard disk quota is not supported due to the configuration of the server file system." So I guess I won't be able to fully handle...

Hi everyone I tried searching the forum pages without success. I have been using Plesk for years without any particular problems, but today I am having difficulty understanding the Policy policy on overuse of resources. I did a test by setting the default plan with traffic at 2GB/month and 2GB...