Search results

Solved.... after playing around, the trailing slash was the issue. No clue why it changed, maybe a change in PHP version of the script calling the API... In brief: https://<IP_ADDRESS>:8443/api/v2/cli/user/call/ returns 404 https://<host.domain.tld>:8443/api/v2/cli/user/call/ returns 404...

Solved.... after playing around, the trailing slash was the issue. No clue why it changed, could be something else than the new IP, such a change in PHP version of the script calling the API... In brief: https://<IP_ADDRESS>:8443/api/v2/cli/commands/ returns 404...

Hi, Since I migrated my Plesk vm to a new IP, I realized the REST API calls to CLI returns 404: https://<IP_ADDRESS>:8443/api/v2/cli/commands/ returns 404 https://<host.domain.tld>:8443/api/v2/cli/commands/ returns 404 command curl -k -u 'admin:password' -X GET...

https://IP_ADDRESS:8443/api/v2/cli/user/call now returns 404... based on the Swagger, there's no more user/call... Any alternative?

Thx!

Same question here. Anyone knows?

Hi, Just running into some IO delays on daily basis, and I can see this command being run on my Plesk box (CentOS Linux 7.9.2009 & Plesk Obsidian Version 18.0.39 Update #2) Would anyone know what it's related to? I could not find what is triggering this command so far. The only page I could...

Hi Benjamin, Did you ever had a chance to find an answer to this question? I'll be also interested in enabling full text search in dovecot. Seen as well a plugin for elasticsearch: https://github.com/filiphanes/fts-elastic Let me know.

FYI - waf.comodo.com authentification is now working fine - I just got an email from their support team and tried, and all back to normal. Nevertheless, latest update of their WAF rules is November 2020. So not so fresh.

@Peter Debik I've now tried to switch to Atomic Basic ModSecurity, but there are no rules.... it's like empty. When I navigate to the WAF settings under a domain, it doesn't allow to browse the rules to exclude some of them for instance. The rules are empty. Nevertheless, in the logs, I could...

Thx Peter - I have also checked on the comodo forum and others encountered the same issue - definitely seems to be on Comodo side...

Hi, Since early this week, I get the following message once logged into Plesk: Error: Failed to update the ModSecurity rule set I've double-checked login/password, all looks good but it keeps failing. I have also noted that I can't login anymore to Free ModSecurity Rules from Comodo I even have...

Hi, Same here since beginning of June. Unsure if it's related to Plesk. Any idea? Thx

Ended up with this and it works well: curl -k -X POST -u 'admin:PaSSword' "https://IP_ADDRESS:8443/api/v2/cli/user/call" -H "accept: application/json" -H "Content-Type: application/json" -d '{ "params": [ "-c", "myUsername", "-role", "myRole", "-passwd", "PaSSword!", "-cname", "myName"...

Yep, ended up with this and it works well: curl -k -X POST -u 'admin:PaSSword' "https://IP_ADDRESS:8443/api/v2/cli/user/call" -H "accept: application/json" -H "Content-Type: application/json" -d '{ "params": [ "-c", "myUsername", "-role", "myRole", "-passwd", "PaSSword!", "-cname", "myName"...

Encountering same issue here - was used to the user/add packet through XML API. Any alternative?

That's my conclusion too. Thx

@IgorG thx, that's a great alternative. So do we confirm that for Plesk prior to Onyx 17.8, where only XML API is available, there's no way to set the language of a user?

Hi, any update on how to set the language of a user through the XML API? Thx

Actually I found the way to make it work - perfectly working with Plesk Onyx - content of the .ftpaccess file: <Limit ALL> Order allow, deny Allow from 127.0.0.1 Allow from IP1 Allow from IP2 Allow from IP3 DenyAll </Limit>