• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Resolved port 443: Connection refused?

Space Monkey

Basic Pleskian
In WP I got 2 critical issues. Below are the messages:


Code:
The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

When testing the REST API, an error was encountered:

REST API Endpoint: https://alternus.nl/wp-json/wp/v2/types/post?context=edit
REST API Response: (http_request_failed) cURL error 7: Failed to connect to alternus.nl port 443: Connection refused

Code:
Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.

The loopback request to your site failed, this means features relying on them are not currently working as expected.
Error: cURL error 7: Failed to connect to alternus.nl port 443: Connection refused (http_request_failed)
This handled by Plesk?
 
I don't know why Plesk don't add this automatically
Because it is a basic operating system setting. Plesk does not touch your nic settings. On many systems, /etc/hosts is maintained automatically by a system service, too.
 
Back
Top