Search results

There is no "Webserver Configurations Trouble Shooter" ¯\_(ツ)_/¯ ?

Load site in browser, dump cache and check the certificate browser is seeing. Tested on multiple browsers.

It is obvious to know when a web site is not using the correct SSL cert, I am not sure I understand why you would ask? There appears to be some sort of disconnect between the plesk admin and the actual web server using the newly created Let's Encrypt cert assignment. I will continue to plug...

Yes, I always do both.

Create a Let's Encrypt cert for a site, no errors and all looks good in web host admin. Problem is, the site does not use the new cert to serve the site, the default ssl cert is used instead. Tried restarting the server to no avail :( Anyone have any ideas why this has started happening...

Since Cloudlinux 6 support ends this year, what would be the recommended Linux OS to migrate to? I am not married to the idea of staying with Cloudlinux, especially since it does not support some basic built in Plesk features. What is the most Plesk friendly ( and secure ) version of Linux to...

This is highly frustrating. Support for MagicSpam will be dropped in Oct 2020 in lieu of Plesk Email Security. Plesk says MagicSpam will still work, but Plesk Email Security is the way to go ... unless you use Cloudlinux. Based on the replies by @IgorG , Plesk as a company does not seem to...

Yes. The IP Addresses are all setup correctly and working well. All services on server work great, it's just the internal telnet and curl requests that are choking.

There were many lines to the results, but here is the one you are likely interested in... tcp 0 0 10.0.0.144:443 0.0.0.0:* LISTEN 0 20664 7602/nginx The 10.0.0.144 IP is internal part of VPC on my EC2 instance.

Yes the IP is redacted. No it is not a firewall issue. As pointed out in my original post, I can connect via curl on remote machine ( different than server ) but cannot connect when on the server itself. I am wondering if the Listen config for nginx is not using the wildcard? Like Listen *:443...

Telnet give a similar error... $ telnet your.plesk-domain.tld 443 Trying 54.191.0.0... telnet: connect to address 54.191.0.0: Connection refused So you can see it is not a DNS issue, since it know which IP to target.

When I try to curl a site hosted on my Plesk server, FROM my Plesk server, it always fails with "curl: (7) couldn't connect to host". This is not a firewall issue, but possibly an issue what nginx Listens for? It works if I curl from my remote desktop, but not if I try and curl locally...

Ended up being CageFS (CloudLinux - Main | New template) on the domain. Removing it, allowed plesk to use the custom php.ini I had no idea that CageFS restricted the custom PHP settings ¯\_(ツ)_/¯

Thanks.

Is it true that I cannot upgrade to Obsidian on my server running CloudLinux Server 6.10 ? https://www.plesk.com/lifecycle-policy/ Looking for answers from other CloudLinux Server 6.10 users.

Plesk support fixed it up.

Yes Igor, I know all this. It is not working.

The domain's php.ini has the updated values, but the server is not using them. Perhaps plesk is not restarting things to pick up the new config correctly?

I load up phpinfo() on a page to verify changes, yet they remain the defaults. I also increase upload_max_filesize to 16MB, yet I am only able to upload files of 2MB or less.

I have set several custom PHP settings, hit Apply ( then OK ) and the custom settings are never applied to the domain. Anyone know how to fix this? CloudLinux Server 6.10 (Vladimir Lyakhov)‬ProductPlesk Onyx Version 17.8.11 Update #78, last updated on Dec 23, 2019 03:52 AM