• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. R

    Issue 400 Bad Request

    Restarting of Apache normally has to be done from the command line or via the Plesk control panel How to restart Apache service in Plesk for Linux - Support Cases from Plesk Knowledge Base . Do not see how that can be done with a browser extension.
  2. R

    Issue sh: gs: command not found exporting files as pdf

    By the way Imagick is working for PHP FPM already . Its ini is loaded and 3.7.0 shows in PHP Info
  3. R

    Issue sh: gs: command not found exporting files as pdf

    Was trying to export files as a pdf and had time outs after 3 minutes. Checked all PHP settings for max_execution time which is 300 seconds, max_input_time 300 seconds, post_max_size 60MB and upload_max_filesize 60MB. Started checking Nginx logs, Httpd logs, Proxy logs and so on. When I did...
  4. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    Also solved. Somehow I had added the wrong ip for api.wordpress.org to `/etc/hosts` . I needed
  5. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    I checked ports based on thread How to detect if a network is blocking outgoing ports? to check for closed outgoing ports. Port 443 for https and 80 for http are closed outgoing ports. Do need these open.. or at least for api.wordpress.org
  6. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    similar error repeated connecting to WordPress api as I have to install a plug-in from the dashboard I also have in WP Toolkit: is also shown in `tail -20 /var/log/plesk/panel.log` so despite the fact that I updated name server: and added api.wordpress.org to hosts file turned off Plesk...
  7. R

    Issue Have a WordPress, widely-used plugins not able to Outbound Communicate

    Did you ever work this out? How did you set up rules? Did you use a HTTP Proxy server setting for WordPress instead like: to solve the issue instead?
  8. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    Only when I go to plugin installation page I still get timeouts . Do have api.wordpress.org added to /etc/hosts and as mentioned Plesk firewall replaced by TransIP firewall which block no outgoing traffic. and error in log
  9. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    Adding based on https://support.plesk.com/hc/en-us/articles/12387791774487-Operations-in-WordPress-Toolkit-fail-WP-CLI-command-has-not-finished-working-in-60-seconds-so-it-was-terminated seems to help
  10. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    Only WP Toolkit keeps on showing the site is in quarantine despite me refreshing. That is odd still.
  11. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    The issue in the end was simple, but overlooked. The default Plesk firewall had all outgoing traffic blocked. This blocked api access to WordPress.org, functioning of WordPress heartbeat and so on. Once I turned off the Plesk firewall and only kept the TransIP firewall all was well. This thanks...
  12. R

    Issue Problem with IP address in Plesk

    I see the same issue I thought this was an internal ip address we need to keep besides external ones. So wonder if I can just delete or need to replace..
  13. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    I checked panel log and saw failed auto update, failed LE SSL for domain, but we did not add domain for Plesk yet. Already checked sites with Immunify and no viruses found.
  14. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    Also seems plugin installation fails and connection to WordPress.org is really slow Perhaps I need to update name server: But not sure how yet...
  15. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    Checking Plesk task manager I see this a lot also 2023-09-26 01:44:01 Event 'phys_hosting_update' for object with ID '9' (snaakontwerp.nl) /usr/local/psa/admin/bin/php -f /usr/local/psa/admin/plib/scripts/interface_async_executor.php -- EventListener...
  16. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    Also 101779 until 101992 are Apache processes now. 101992-101779 = 213 . Seems a lot. did a service httpd restart just now
  17. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    WP Rocket has never caused issues on custom VPS or shared hosting or WordPress hosting. But without it it seemed the WordPress installation started to at least function some. Mind blowing, but true. How can I turn off Immunify? Could be the cause of the error Also returned as Plesk setup with...
  18. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    Yes, that is something one always can do. Stop using your shop, start a basic one and test. Will however try to solve the issue with the shop running as much as possible. Tried to install query monitor from the Dashboard but installing a plugin even timed out. I also see a tremendous amount of...
  19. R

    Resolved upstream timed out (110: Connection timed out) while connecting to upstream

    Just fired `/usr/local/psa/admin/sbin/nginxmng --disable` and TTFB byte is 16 seconds for a basic WordPress page About the company. Things were faster on shared hosting before.
Back
Top