Tag Info

New answers tagged

0

Here is a configuration that I run on Rackspace 256 MB Ubuntu 12.04 servers without issue (HTML only sites): gzip on; gzip_disable "msie6"; gzip_min_length 1100; gzip_vary on; gzip_proxied any; gzip_buffers 16 8k; gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/rss+xml text/javascript ...


0

There may be several reasons for this, which is nicely described in Parallels article http://kb.sp.parallels.com/en/120785 Also, I suggest you to re-register the php with fcgi module through command line and see if that helps.


-1

Try this as root. # chroot <users chroot> # apt-get update # apt-get install -y subversion


0

Thank you for your help. FYI the problem was the SSL. I leaved the IP without the SSL and the domain was working well with the new IP. So I think this UCC certificates will work only with domain alias, or maybe Plesk can't manage them without different IPs. The problem is the cost of the new IP, that is larger than the SSL.. Thks


0

I am not sure about which version this error was reported. But as per my knowledge this was a error in versions below 9.5 Root cause was with faulty sw-cp-server package. And the fix was there in a Parallels KB article. I would be glad to redirect users there: http://kb.sp.parallels.com/en/8338


0

First of all let me clarify you one thing, Parallels considers Debian 5.0 as EOL. You can refer Parallels website for this. Again Plesk 10 will be EOL by 2015. http://sp.parallels.com/hcap/support/policies/plesk-lifecycle/ So as per my suggestion it's safe to migrate all your contents to a supported system. As everyone knows migration will be safe and ...


1

Plesk stores its logs under: /var/log/sw-cp-server/error_log /usr/local/psa/admin/logs/panel.log /var/log/sw-cp-server/sw-engine.log and yes the first part we need to check if psa not running is: df -h df -ih make sure none of them is showing 100% full If the issue still there just check and make sure port 8443 is not used by any other service. ...


1

A quick search shows that support for TLS server name indication (SNI), which is what you need in your case, was introduced in wget release 1.14. Curl included SNI support quite a bit earlier. For instance RHEL/CentOS 6 include wget version 1.12 and Debian wheezy 1.13 so I expect they don't support SNI yet.


0

Two separate, but loosely related issues: Regarding 1&1 DNS The issue with not being able to use their DNS as a secondary unless the domain is registered with them is a policy issue, not a technical one. So, you can either transfer the domain to 1&1, or not use 1&1 as your secondary. There are numerous other options for secondary DNS Regarding the name ...


1

There are 2 options This appears to me to be either a case of DNS caching or of DNS poisoning I'm guessing the old DNS server has very long timeouts (like a week) and/or is acting as an authoriative server and serving up the old records to whoever asks it. If it happens to be a large ISP who does not run separate caching and authoritative servers, the old ...



Top 50 recent answers are included