• 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.

Issue Connection reset by peer: AH01075 when using plesk API to register domain on the same server

fdehghani23

New Pleskian
Hi,
I have a problem with using plesk rset api to register a domain.

I got this error when I try to execute the code from the same server that's running Plesk on.

(104)Connection reset by peer: AH01075

After searching a lot about the issue I found this and I think that it's correct because I tried to register a domain on another server with the same code and it was successfull

"To be honest, I think this might be an issue related to Plesk itself. Because, as far as I can see, this issue only happens when you execute the code from the same server you're running Plesk on. I suspect I has something to do with the fact that php-fpm restarts when you add a new domain. Hence the 503 error, and thats also why this issue doesn't happen when you run the code from a remote/local machine.

Not necessarily a bug, but I would say it is certainly undesirable behaviour. I am also not sure if there is a solution to this issue."
 
Hi,
I have a problem with using plesk rset api to register a domain.

I got this error when I try to execute the code from the same server that's running Plesk on.

(104)Connection reset by peer: AH01075

After searching a lot about the issue I found this and I think that it's correct because I tried to register a domain on another server with the same code and it was successfull

"To be honest, I think this might be an issue related to Plesk itself. Because, as far as I can see, this issue only happens when you execute the code from the same server you're running Plesk on. I suspect I has something to do with the fact that php-fpm restarts when you add a new domain. Hence the 503 error, and thats also why this issue doesn't happen when you run the code from a remote/local machine.

Not necessarily a bug, but I would say it is certainly undesirable behaviour. I am also not sure if there is a solution to this issue."
did you ever figure this out as I believe I have the same problem?
 
Back
Top