• 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

Plesk 12.5 RTM is out

Status
Not open for further replies.
It will reach this stage soon. Watch for the official announcement! :)
Soon, as in a matter of days/weeks, or months? :) I have to setup a new Plesk server these days and I'm still not decided if I should install 12.0 or just wait a bit and install 12.5.
 
Hi!
In the list of Supported Operating Systems I can't find OpenSuSe. Will it release later or is it not planned to release for this OS? Or do I understand something wrong?
Regards
Sabine
 
Hi!
In the list of Supported Operating Systems I can't find OpenSuSe. Will it release later or is it not planned to release for this OS? Or do I understand something wrong?
Regards
Sabine
Support of OpenSUSE was discontinued.
 
Hi. With this version installed, ( and ModSecurity and Fail2Ban enabled ) when i click on the websites and domains tab its very slow to refresh, while refreshing, any users accessing the server get a "BAD GATEWAY" response. Here are logs during click on "Websites and domains":

upstream: "http://192.168.32.13:7080/", host: "192.168.32.13"

2015/09/27 17:28:30 [error] 1021#0: *1 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 192.168.32.151, server: , request: "GET / HTTP/1.1", upstream: "http://192.168.32.13:7080/", host: "192.168.32.13"

2015/09/27 17:28:31 [error] 1021#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.32.151, server: , request: "GET / HTTP/1.1", upstream: "http://192.168.32.13:7080/", host: "192.168.32.13"

2015/09/27 17:29:17 [error] 1021#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.32.151, server: , request: "GET / HTTP/1.1", upstream: "http://192.168.32.13:7080/", host: "192.168.32.13"

2015/09/27 17:29:29 [error] 1021#0: *8 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.32.151, server: , request: "GET / HTTP/1.1", upstream: "http://192.168.32.13:7080/", host: "192.168.32.13"

2015/09/27 17:29:29 [error] 1021#0: *8 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.32.151, server: , request: "GET / HTTP/1.1", upstream: "http://192.168.32.13:7080/", host: "192.168.32.13"

2015/09/27 17:33:27 [error] 1021#0: *213 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.32.151, server: , request: "GET / HTTP/1.1", upstream: "http://192.168.32.13:7080/", host: "192.168.32.13"


and HTTPD logs say:

[Sun Sep 27 17:48:58.192767 2015] [mpm_event:notice] [pid 21617:tid 140325901322304] AH00492: caught SIGWINCH, shutting down gracefully

[Sun Sep 27 17:49:00.853548 2015] [core:notice] [pid 22496:tid 140698387421248] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0

[Sun Sep 27 17:49:00.855544 2015] [suexec:notice] [pid 22496:tid 140698387421248] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)

[Sun Sep 27 17:49:00.857445 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH01909: RSA certificate configured for roundcube.webmail:443 does NOT include an ID which matches the server name

[Sun Sep 27 17:49:00.857704 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH01909: RSA certificate configured for horde.webmail:443 does NOT include an ID which matches the server name

[Sun Sep 27 17:49:00.857931 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH01909: RSA certificate configured for lists:443 does NOT include an ID which matches the server name

[Sun Sep 27 17:49:00.858144 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH01909: RSA certificate configured for default-192_168_32_13:443 does NOT include an ID which matches the server name

[Sun Sep 27 17:49:00.858248 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)

[Sun Sep 27 17:49:00.858289 2015] [:notice] [pid 22496:tid 140698387421248] ModSecurity for Apache/2.9.0 (http://www.modsecurity.org/) configured.

[Sun Sep 27 17:49:00.858292 2015] [:notice] [pid 22496:tid 140698387421248] ModSecurity: APR compiled version="1.4.8"; loaded version="1.4.8"

[Sun Sep 27 17:49:00.858295 2015] [:notice] [pid 22496:tid 140698387421248] ModSecurity: PCRE compiled version="8.32 "; loaded version="8.32 2012-11-30"

[Sun Sep 27 17:49:00.858297 2015] [:notice] [pid 22496:tid 140698387421248] ModSecurity: LUA compiled version="Lua 5.1"

[Sun Sep 27 17:49:00.858300 2015] [:notice] [pid 22496:tid 140698387421248] ModSecurity: YAJL compiled version="2.0.4"

[Sun Sep 27 17:49:00.858302 2015] [:notice] [pid 22496:tid 140698387421248] ModSecurity: LIBXML compiled version="2.9.1"

[Sun Sep 27 17:49:00.858304 2015] [:notice] [pid 22496:tid 140698387421248] ModSecurity: Original server signature: Apache

[Sun Sep 27 17:49:00.858305 2015] [:notice] [pid 22496:tid 140698387421248] ModSecurity: Status engine is currently disabled, enable it by set SecStatusEngine to On.

[Sun Sep 27 17:49:01.852192 2015] [auth_digest:notice] [pid 22496:tid 140698387421248] AH01757: generating secret for digest authentication ...

[Sun Sep 27 17:49:01.853079 2015] [lbmethod_heartbeat:notice] [pid 22496:tid 140698387421248] AH02282: No slotmem from mod_heartmonitor

[Sun Sep 27 17:49:01.854475 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH01909: RSA certificate configured for roundcube.webmail:443 does NOT include an ID which matches the server name

[Sun Sep 27 17:49:01.854660 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH01909: RSA certificate configured for horde.webmail:443 does NOT include an ID which matches the server name

[Sun Sep 27 17:49:01.854837 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH01909: RSA certificate configured for lists:443 does NOT include an ID which matches the server name

[Sun Sep 27 17:49:01.855009 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH01909: RSA certificate configured for default-192_168_32_13:443 does NOT include an ID which matches the server name

[Sun Sep 27 17:49:01.855093 2015] [ssl:warn] [pid 22496:tid 140698387421248] AH02292: Init: Name-based SSL virtual hosts only work for clients with TLS server name indication support (RFC 4366)

[Sun Sep 27 17:49:01.858762 2015] [mpm_event:notice] [pid 22496:tid 140698387421248] AH00489: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips Apache mod_fcgid/2.3.9 configured -- resuming normal operations

[Sun Sep 27 17:49:01.858783 2015] [core:notice] [pid 22496:tid 140698387421248] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'

[Sun Sep 27 17:49:03.208768 2015] [mpm_event:notice] [pid 22496:tid 140698387421248] AH00492: caught SIGWINCH, shutting down gracefully




Just wanted to point out i'm Running this on CentOS 7.1 ( latest version with yum update ran )
 
Last edited:
Slave DNS Manager for Windows is now only in development phase and possibly will be released a bit later. Right now Slave DNS Manager is availabe in extensions catalog only for Linux.

Hi, I see it's now available in the Extension catalog for Windows! I installed and setup and could not get it to work. I was getting a REFUSED error on the slave and a denied error on the master. I had to manually go into named.conf on the windows master and make a change. There is a line

acl common-allow-transfer {
none;
};

that all of the zones reference in the 'allow-transfer' section. On Linux Slave DNS when you add a slave, it adds this IP(s) to each zone within the allow-transfer section on the master so when a transfer request comes in it's allowed. If I add the slave's IP(s) in place of where it says none, it works. This must be a bug as we shouldn't have to manually modify the named.conf file on the master. It should be automatic when adding a slave through the extension like Linux does. Just a heads up and wondering if there is a fix or if you all have any ideas? Thanks for your hard work as always!

Tony
 
Some things popping up now and then....

I want to set a GLOBAL NS which every other domain will use, still unable to work it ou

Webmail services wont work either

Kingsley, by Global NS do you mean all your domains point at the same name servers? For me I have done this for years where I have all my domains point at the same 4 name servers which for me
ns1.mydomain.com
ns2.mydomain.com
ns3.mydomain.com
ns4.mydomain.com

I then always have NS1 and NS2 pointing at my Plesk server and then NS3 and NS4 pointing at my data center name servers that are set to slaves. Then I just updated my domain template and removed the default Plesk generated ones and added my 4 custom ones. The only thing I do after creating a new domain is goto my data center name servers and create the domain as a slave and then point them at Plesk.
 
Status
Not open for further replies.
Back
Top