• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by MoritzCH

  1. M

    Second domain -- SSL settings???

    Hi, got my first domain up and running (secured by SSL certificate - mail server, ftp server and https) and now I want to add a second domain with the same security settings. Environment: - Plesk 12 - 2 domains and 2 mail accounts (domain 1 / [email protected] and domain 2 / [email protected])...
  2. M

    Postfix/Dovecot MX entry

    @eilko You were right. it's working like a charm now (IN: IMAP 995 SSL and OUT: SMTP 465 SSL) Thank you!
  3. M

    Postfix/Dovecot MX entry

    well it's not my local client giving me the feedback mentioned above. It's an online testing webpage :) Going to test your advice when I get home from work
  4. M

    Postfix/Dovecot MX entry

    you mean inside the /etc/postfix/main.cf? I already changed it inside the Plesk DNS settings and inside these files -->
  5. M

    Postfix/Dovecot MX entry

    Hi, after fixing this annoying HTTPS thing I have one last thing to solve. I would like to setup a SSL certificate for my mailserver and experience a strange problem. I changed the MX DNS entry to "myvserver.info" (my domain) instead of "mail.myvserver.info" (so I can use the same certificate)...
  6. M

    Prevent non-www https connections

    yeah, that trick helped me :) Thank you!
  7. M

    Prevent non-www https connections

    As I said before, the error is sitting in front of everything -.- had a typo mistake inside the domain I entered. Sorry for that. Now these things are working: http://domain.com --> https://www.domain.com:8443 (certificate working) http://www.domain.com --> https://www.domain.com:8443...
  8. M

    Prevent non-www https connections

    Good morning UFHH01, but this is exactly my problem. I choosed the "www" as preferred domain and you can still open a "non-www" domain if you specify a port (like 8443 for Plesk). I also tried to open the page with my tablet (internet connection = mobile network) but there I have the same...
  9. M

    Prevent non-www https connections

    Hi, just read a few threads where some people said that rewriting a HTTPS URL is not possible and will not be processed by the browser. Whatever, I created the .htaccess file, changed the DOMAIN.COM to the right one and nothing happens. I did try the Nginx rewrite as well without success. This...
  10. M

    Prevent non-www https connections

    Hi UFHH01, tried both seperately but they are not working (or I am doing something wrong) Read some post and I am not sure if you can rewrite https urls
  11. M

    Prevent non-www https connections

    Good morning, I am using Plesk for a week now and it's really nice but there is something I can't get working. Recently I bought an SSL certificate for my server hostname I am using for Plesk (let's say it is "www.DOMAIN.com") What I want to do is to redirect all traffic for this domain to the...
  12. M

    Can't open "Updates and Upgrades" (Timeout)

    I added both using iptables and now it looks like this: tcp6 0 0 :::8443 :::* LISTEN tcp6 0 0 :::8447 :::* LISTEN should be fine?!? (not really confident with iptables but why is it a tcp6 and not a tcp port?) I used this cmd: iptables -A INPUT -p tcp --dport 8447 -j ACCEPT EDIT Now...
  13. M

    Can't open "Updates and Upgrades" (Timeout)

    Good morning, I recently installed a "Debian Wheezy with Plesk 12" image on my vServer. After buying a license (Plesk 12 Web ADMIN Edition) everything is working fine except the "Updates and Upgrades" link. Everytime I click on it, a new windows opens and nothings happens (page cannot be...
Back
Top