• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Recent content by R2bEEaton

  1. R

    Resolved Curl Request 401 Unauthorized

    Yes, I'm sure I'm using the correct password for the admin account. It's the same one I use to log in here: If you add an -i flag to your test with a wrong password you will see the unauthorized bit. And yes, I'm using the correct domain (same as what I use for the web portal) and did restart...
  2. R

    Resolved Curl Request 401 Unauthorized

    Yes, but as per the example there: curl -X POST --user root:password -H "Content-Type: application/json" -H "Accept: application/json" -d'{}' "https://domain:8443/api/v2/auth/keys" You still need to use the normal authentication method to even generate an API key in the first place. And also...
  3. R

    Resolved Curl Request 401 Unauthorized

    How would I enable this in the web interface? Edit: I found the panel.ini editor extention and pasted the api enable to the editor and hit save, but it still appears to not work. Also, my friend was wrong, we are on Plesk Obsidian.
  4. R

    Resolved Curl Request 401 Unauthorized

    Hello! I am very new to Plesk and I'm doing this for a friend who is also stumped. He's got a Plesk server set up and wants to access the Rest API remotely, but whenever he or I try on our own machines, we get the following error: [root@vps ~]# curl -i -k -X GET -u admin:thepasswordgoeshere...
See more
Back
Top