• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

Search results

  1. yabado

    Question Update MariaDB version on Plesk

    The article is not correct and does not install MariaDB at all? Based on comments section, I am not the only one. Why is this not part of the Component Update page?
  2. yabado

    Resolved Template_Exception: nginx: [emerg] invalid max_size value "max_size=" in /etc/nginx/plesk.conf.d

    I am in Service Provider view. And not using Windows. Plesk Obsidian Version 18.0.31
  3. yabado

    Resolved Template_Exception: nginx: [emerg] invalid max_size value "max_size=" in /etc/nginx/plesk.conf.d

    I am Web Host (service) admin with full access. That link is not listed anywhere on Tools and Settings page.
  4. yabado

    Resolved Template_Exception: nginx: [emerg] invalid max_size value "max_size=" in /etc/nginx/plesk.conf.d

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

    Issue Let's Encrypt SSL cert created, but apache/nginx not using it to serve site?

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

    Issue Let's Encrypt SSL cert created, but apache/nginx not using it to serve site?

    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...
  7. yabado

    Issue Let's Encrypt SSL cert created, but apache/nginx not using it to serve site?

    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...
  8. yabado

    Input Recommended replacement for Cloudlinux 6?

    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...
  9. yabado

    Issue Plesk Email Security - No CloudLinux support?

    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...
  10. yabado

    Issue Can curl remotely, but not locally on Plesk server. Always Get curl: (7) couldn't connect to host

    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.
  11. yabado

    Issue Can curl remotely, but not locally on Plesk server. Always Get curl: (7) couldn't connect to host

    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.
  12. yabado

    Issue Can curl remotely, but not locally on Plesk server. Always Get curl: (7) couldn't connect to host

    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...
  13. yabado

    Issue Can curl remotely, but not locally on Plesk server. Always Get curl: (7) couldn't connect to host

    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.
  14. yabado

    Issue Can curl remotely, but not locally on Plesk server. Always Get curl: (7) couldn't connect to host

    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...
  15. yabado

    Issue Domain PHP "Performance and security settings" not used?

    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 ¯\_(ツ)_/¯
  16. yabado

    Resolved Obsidian on CloudLinux Server 6.10 ?

    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.
Back
Top