• 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

Search results

  1. WielM

    Question Letsencrypt and mailman

    I added mailman to one of my domains. Doing so creates a url called lists.my.domain. This url does not show up in the domain's subdomain overview. The domain uses a LetsEncrypt certificate to get https support. The certificate has wildcard set, but 'lists.my.domain' does not use it. The Digicert...
  2. WielM

    Question Qmail IPV6 support?

    IPV6 address e-mails are not processsed by qmail, it does not recognize the IPV6 address. On internet I read that there are patched versions of Qmail that support IPV6. Any way to replace my Qmail install with such a patched verrsion? Why doesn't Plesk support this version of Qmail as most...
  3. WielM

    Resolved Security Advisor - Plesk Panel Certificate Expired

    Solved! Obviously, the renew process restarts apache and nginx. The nginx restart failed during restart (didn't pass the config-test) and therefore the old instance of nginx kept running, with the old certificate information! After repairing the nginx config, the renewed certificate became...
  4. WielM

    Resolved Security Advisor - Plesk Panel Certificate Expired

    I'm having the same problem. My secured sites worked for 3 months and than expired. They were renewed as I can see using openssl x509 -in cert-xxxxxx -text -noout where I can read: Validity Not Before: Sep 25 23:53:00 2017 GMT Not After : Dec 24 23:53:00...
  5. WielM

    Let's Encrypt extension

    A server reboot eventually did the job. Location has switched to https now and no errors anymore on that domain. The real cause of the problem will still be hidden in the dark, I guess. Thanks! \Wiel
  6. WielM

    Let's Encrypt extension

    HTTP/1.1 301 Moved Permanently Server: nginx Date: Thu, 17 Aug 2017 17:38:52 GMT Content-Type: text/html Content-Length: 178 Connection: keep-alive Location: http://www.wsvalem.nl/ X-Powered-By: PleskLin Weird...WP does not insert that in the header. As it is just before the "X-Powered-By" I...
  7. WielM

    Let's Encrypt extension

    I have some 10 sites running SSL through LE, that operate without problems using the same IP address. I guess that's because of the SNI (Server Name Indication) that allows multiple sites running SSL using the same IP address. This is the only domain having a problem. Where did you find the...
  8. WielM

    Let's Encrypt extension

    Although, thanks to UFHH01, I managed to solve the IPV6 problem, my original problem (not able to get an LE certificate working for a domain) still exists. The conf files seem to look ok: httpd.conf shows SSLEngine on SSLVerifyClient none SSLCertificateFile...
  9. WielM

    Let's Encrypt SSL Certificate

    In my server configuration, this solution fails in the first step, because I already allocated shared IPV6 addresses for domains and 'IP Addresses' refuses to change the IPV6 address to 'Dedicated'. As far as I know, there's no place in Plesk where I can find the domains that use the shared IPV6...
  10. WielM

    Let's Encrypt extension

    BINGO! The fake IPV6 address has been removed from all the nginx conf files! Thanx! But the wsvalem site still uses the root certificate after I succesfully installed a new domain certificate through Plesk: SSL Server Test: wsvalem.nl (Powered by Qualys SSL Labs) \Wiel
  11. WielM

    Let's Encrypt extension

    That command still crashes Apache/nginx: > plesk repair web nosysoft.net -y -v Repairing web server configuration Repairing web server configuration for the domain nosysoft.net .. [2017-08-07 20:09:50] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/httpdmng'...
  12. WielM

    Let's Encrypt extension

    Bu But the Configurations table's field type 'nginxDomainVhost' seem to steer the Rebuild in generating the nginx .conf files where the errors occur. In several .conf files in /etc/nginx/plesk.conf.d/vhosts I find code like: server { listen...
  13. WielM

    Let's Encrypt extension

    Sorry for the confusion. I never alter tables in the psa database but use it as guidance to find the right GUI page where I can alter information. These were the locations where I found references to the wrong IPV6 address. In this case I guess that the only table that still matters, is the...
  14. WielM

    Let's Encrypt extension

    More info: the only places where I can find the fake IPV6 address in the psa database is in the Configurations, exp_event and log_components tables. Where in the Plesk GUI can I alter these tables?
  15. WielM

    Let's Encrypt extension

    One step forward again! I managed to remove the fake IPV6 address out of the list with Plesk IP Adresses and out of the Ubuntu interface definitions.. But for some reason, the Webserver Configurations Troubleshooter still uses the old fake IPV6 address to rebuild the nginx .conf files. Where...
  16. WielM

    Let's Encrypt extension

    I've been using this extension for some time already. All buttons for all config files are green. But I indeed have the feeling that something is wrong with nginx, not apache: > nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: [emerg] bind() to 172.16.0.1:80...
  17. WielM

    Let's Encrypt extension

    BTW, in a parallel session I can start apache2 without problems while the plesk repair utility executes.
  18. WielM

    Let's Encrypt extension

    > /opt/psa/admin/logs# sysv-rc-conf --list apache2 apache2 0:off 1:off 2:on 3:on 4:on 5:on 6:off >:/opt/psa/admin/logs# sysv-rc-conf --list nginx nginx 0:off 1:off 2:on 3:on 4:on 5:on 6:off Looks ok to me? \Wiel
  19. WielM

    Let's Encrypt extension

    Oops! plesk repair failing: igure-server'] with exit code [1] [FAILED] - httpdmng failed: [2017-08-06 22:48:54] ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/apache_control_adapter' '--restart' '--restart-interval' '300' '--http-port' '7080' '--https-port'...
  20. WielM

    Let's Encrypt extension

    Thanks for responding! The panel.log does not really provide interesting information: Invalid response from https://acme-v01.api.letsencrypt.org/acme/new-reg: Error creating new registration :: not a valid e-mail address. (I forgot the -m switch) Would be great if you could help... Cheers...
Back
Top