• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Search results

  1. F

    Issue Downloads abort after 1gb or a bit later

    Ok that's interesting, should these fastcgi_buffers 8 16k; fastcgi_buffer_size 32k; proxy_buffers 8 16k; proxy_buffer_size 32k; also go in to the panel.ini or are these unrealted to the issue with the download?
  2. F

    Issue Downloads abort after 1gb or a bit later

    Sorry for the double post, I also see following in the log when a customers downloads the video, but I doesn't know what this means 2021-12-13 18:43:54 Access 77.xx.xx.xx 206 GET /?download_file=40560&order=wc_order_EnyMWsCKYgCRR&email=xxxx&key=6619b810-7482-4a0a-8606-c1d04c995967...
  3. F

    Issue Downloads abort after 1gb or a bit later

    Ok thank you I will try that. I've that line already in panel.ini but with a high value after that, found it also in a different solution. Could you explain why this should be without any value behind the quotation and why in the panel.ini not in /etc/nginx/conf.d? Also is there a way to check...
  4. F

    Issue Downloads abort after 1gb or a bit later

    Hello everyone, currently I've a medium sized problem. We're running a woocommere store and my customers have some problems with the digital downloads. Our files are quite huge (smallest 4 GB largest 37 GB). For most of our users the download works, however for some the download aborts right at...
  5. F

    Resolved NGINX error: upstream sent too big header

    really sorry for digging out this really old message, but is it enough to place it under /etc/nginx/conf.d/ and there in a file like example.conf and restart the nginx service? Is it then applied to all domains on the plesk server?
  6. F

    Issue Problem with reverse DNS (SMTP Banner) for multiple Domains

    Ok thank you for that information. So in general I should be fine? Don't want to go through the trouble of contacting every single provider because they put the domain on a blacklist because of a wrong SMTP Banner.
  7. F

    Issue Problem with reverse DNS (SMTP Banner) for multiple Domains

    Hello everyone, currently I struggle with the SMTP Banner. on mxtoolbox. I get the error Reverse DNS does not match SMTP Banner The plesk/mail setup is as follows. domain1.com is the main domain and also the hostname for the plesk server. Here everything is correct SMTP Banner is working...
Back
Top