Search results

Liwindo... the domain must be visible.. make sure .htaccess files are not interrupting access.. and make sure the domain is not going through cloud flare or similar.

You must be right.. after restart i was able to upload 3.3gb no probs... thanks

Hi there According to http://kb.odin.com/en/122900 it stated "Note: Maximum upload file size can not exceed 2Gb" as a foot note. even with client_max_body_size 3000m; we get "client intended to send too large body" if uploading a 2.2gb file Is there a way to raise this limit or is it...

wow that is a narrow screen.. can we see the next page?

upload a infophp file as described.. take a screenshot of the top of the page and show us what it looks like.

Which one?

How are you running php? Mod_php fastcgi?

apache php-fpm is only supported on apache 2.4 .. does your distro support this?

yum install -y php-soap

Thanks for the heads up.. this is a irritating bug

How are you clearing the cache?

There are a range of .htaccess fixes for this but none worked as well as the above.. nginx is pretty low profile... switch it on and give it a go.

In plesk 11 you could update the CA bundle without needed to repaste the SSL certificate. This was very handy. In plesk 12x you need to add your new CA bundle and scroll down and copy and paste the cetificate again.. its only small but very irritating.

You just need to use ProxyPass ie In Web server settings.. Additional directives for HTTP AND HTTPS (if needed) add <Location /> ProxyPass http://ip.of.site.xxx:8080/ ProxyPassReverse http://ip.of.site.xxx:8080/ </Location> this will then send all requests to 8080 from 80 and 443...

Are you sure this is not just the microupdate bug.. check that /etc/proftpd.conf folder exist and create it if not also tail -f /var/messages to see what is going on when you connect. you can also service iptables save service iptables stop service iptables status to drop all firewall...

Just in case.. check the entries in core_config_data for base_urls (secure and non secure) are they correct? then try to rebuild you vhosts /usr/local/psa/admin/bin/httpdmng --reconfigure-all

This is beyond annoying.. we had one client who had hundreds of identical clones of his site. The urls were in the form of http://something.com/random.php?actual.domain.com/some_page after going around in cirlces we found the best fix was to add ## Deny illegal Host headers if ($host !~*...

for us it is the flexibility.. want domain1.com to run pure nginx and domain2.com to run nginx>apache or domain3.com to run pure apache.. all are possible at the same time in plesk. Plesk also seems to play nicer with the underlying OS rather than demanding that things are done THIS way. Also...

thanks.. very interesting.. + I am sure it would be good to see other tests. I suspect the relative differences will be about the same

We have seem this on 5 servers now starting last weekend. it is really misleading as it looks like there is a port issue. Which is not the case. on 4 servers disabling and re-enabling nginx in service management was enough to fix the issue. on the other we had to manually upgrade nginx and...