Search results

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

Anyone from Plesk care to reply?

I have several clients that use older email clients to get/send their email. These old email apps still use older SSL protocols like SSL v.2/3 and TLS v.1 If I upgrade to Obsidian, will my clients have issues accessing their emails? My current setup... OS: ‪CloudLinux Server 6.10 (Vladimir...

Happy to see a reply confirming this was a bug caused by recent update. After working all day to track down the problem, only wish the reply was made sooner

Looks to be a bug from Plesk, not sure why no one has replied to this yet ¯\_(ツ)_/¯ It appears related to this issue, but I never changed any settings, only ran updates. PHP support cannot be enabled for one domain in Plesk when nginx service is stopped

All of my domains now look like this?

Did a reboot and did not fix things.

Here is the message next to PHP version selector... PHP support cannot be enabled because current hosting configuration does not include any PHP versions available for this domain. I believe this bug was introduced within past 7 days. How can I fix this? Furthermore it has this as well...

It is great how the new Repair Kit Extension can show which domain is using CPU and Memory, but what I really need is to see who is using high Bandwidth bursts. Is there any chance this can be added to Repair Kit in a future update?