• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved PowerPress Verification Error: Connection Refused

ten.iclica

New Pleskian
Hi.

I have Plesk Obsidian on my Ubuntu server hosted by Digitalocean. I am getting this "connection refused" error during verification of my podcast mp3 file on my site.

Error: Failed to connect to [domain] port 443: Connection refused

Output for command on my terminal:
curl -I "url"
Code:
HTTP/2 200
server: nginx
date: Thu, 10 Dec 2020 16:20:48 GMT
content-type: audio/mpeg
content-length: 12528763
last-modified: Wed, 09 Dec 2020 21:15:03 GMT
etag: "5fd13e57-bf2c7b"
x-powered-by: PleskLin
accept-ranges: bytes

Output for command on my terminal:
curl -i -r "url"
Code:
HTTP/2 206
server: nginx
date: Thu, 10 Dec 2020 16:22:18 GMT
content-type: audio/mpeg
content-length: 100
last-modified: Wed, 09 Dec 2020 21:15:03 GMT
etag: "5fd13e57-bf2c7b"
x-powered-by: PleskLin
content-range: bytes 0-99/12528763

I have tried disabling firewall and disabling fail2ban but the result is same, I still got connection refused error.
Previously I was using my server without Plesk (or any Plesk like software) and there was no error while podcast verification on PowerPress.

Thanks.
 
Last edited:
I solved this issue by editing /etc/hosts file. I changed 127.0.1.1 "machine-name" line with 127.0.1.1 "server IP". But I wonder why this change solved my problem?
 
Back
Top