Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
telnet smtp.gmail.com 587
Trying 2a00:1450:400c:c07::6c...
telnet: connect to address 2a00:1450:400c:c07::6c: No route to host
Trying 173.194.76.108...
Connected to smtp.gmail.com.
Escape character is '^]'.
220 smtp.gmail.com ESMTP s139sm10136236wme.35 - gsmtp
I already tested my system and I can reach port 587 via telnet, this is the first thing I tried. And I added port 587 in the Plesk firewall. But the mail settings page still shows the alert message saying its blocked.
OK I see now, and you are right the ports appear blocked, my settings are almost the same. But how do we explain the "blocked" alert in Plesk panel and, stranglely, why is smtp.gmail.com appearing here?
In our server Mail settings we get "You cannot send emails from Plesk because outbound connections on TCP port 587 is blocked. Check the firewall settings or contact your hosting provider.". Port 587 is open when tested using Telnet, Emails can be sent from port 587 and we even opened it up...
I tried the smtproutes qmail control setting but emails still go out through the "primary" IP. Are there any other solutions. Changing from qmail over to Postfix seems to block messages sent from some websites, especially orders from e-commerce sites, so this is not the best solution.
I have three IPs and would like to allocate each one to different domains in smtp for sending mail (as they are set in hosting settings and DNS). Right now all hosted domains send out e-mail using only the primary IP regardless of the IP used in hosting settings. I'm in Plesk 12.5 and CentOS6.7...
I created and stored some important files in a private password-protected folder under mydomain/files/private (webdav). I lost an important file stored in this folder. I cannot see how to retreive it from my whole server backup, this folder does not appear on either site files nor domains when...
I have an identical problem on an identical set-up (Plesk12.5 CentOS6.7). Mail clients cannot connect on ssl ports 993 or 995. Plesk repair mail doesn't change anything, TLS Receiver test says all OK except for "self-signed certificate" (it's the Plesk Parallels default certificate). SSL works...
I have a similar related issue on a fresh install exactly the same set up (CentOS 6 Plesk 12.5). Upon adding a custom rule in Plesk firewall (opening passive FTP ports), all connections Pop and Imap via ports 995 and 993 are denied, and despite them being indicated as open using SSH root command...
I had a problem with this MU and, in fact, it is a recurring problem since MU #40 or before. The server crashes (or just doesn't reboot) after the updates. I just had to manually restart my server each time. I temporarily resolved this issue by switching off automatic updates and manual updates...
502 Bad Gateway after upgrade to Plesk 12
I have the same problem and I (unwisely) rebooted my server. Now the websites and email services are inaccessible too. Only SSH works. Is there a way to revert to previous Plesk 11.5?
I have exactly the same set-up as Manuel (recent Plesk upgrade, change from qmail to postfix) and I get the same warnings. It started when I couldn't send out a newsletter with PHP mail() because "[email protected]" was not considered as a valid email address for sending. I resolved...