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.
I did get this message in the log file after the timeout.
Nov 28 07:15:31 pleskcp proftpd: pam_env(proftpd:setcred): Unable to open config file: /etc/security/pam_env.conf: No such file or directory
Hi everyone, my Plesk Web Panel been working perfectly since install. All of the sudden (maybe after a Plesk update), a client informed me they could not FTP to their account. I proceeded to try with my account and the same result.
The logs show a successful user login:
Nov 28 06:39:55 pleskcp...
Ive tried to resolve this on my own but it seems this is a tough one. When sending email from webmail, name and IP are blank. Any suggestions on how to resolve this?
Received: (qmail 25151 invoked from network); 25 May 2016 06:54:29 -0700
Received: from unknown (HELO webmail.gizadog.com)...
It figured out that each domain needs to have its IPv6 address assigned to the domain to allow access. Still does not explain why some domains without this assignment worked.
Here is a screen shot of the IP panel on a domain.
http://i.imgur.com/OQShwH9.jpg
Version: Plesk...
This IPv4 vs IPv6 stuff if beyond me. There are some sites on my Plesk 12 server that "can" be viewed from IPv6 devices without a problem and other sites display the default Apache page. All web sites "can be seen" from IPv4 addresses.
What Ive tried:
I've added the AAAA record with the IPv6...
I seem to be having the strangest issue with my Plesk hosting. The system was running fine for a year. Then all of the sudden, most of the sites started showing the message "Bad Gateway 502 - Nginx".
After extensive research the only option to get the site working again was to remove "Nginx"...