Search results

Username: Azurel TITLE Redirect for alias domains PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian Version 18.0.33 #1, CentOS Linux 8.3.2011 PROBLEM DESCRIPTION In host settings of a alias domain, there is a checkbox for 301 redirect. Its unchecked and its disabled (greyed)...

@Vesta I had yesterday a equal issue. Maybe you must only renew it manually in plesk?

Today I get a Obsidian Update Version 18.0.33 Update #1 So I tested all alias/forward domains again for this subscription. DOMAIN www.example1.com with a valid working SSL have 3x aliases all with NET::ERR_CERT_COMMON_NAME_INVALID In alias domains click on SSl Certificate open "Upload the...

Yes I have and I am 100% sure its working all fine as I created the alias domains and "forward to"-domains months ago. In another subscriptions alias-/foward-domains working fine, I found this issue only in one subscription, but this subscription have ~20 alias domains and "forward to"-domains...

Click on "SSL/TLS Certificate" for alias domains open not Lets Encrypt, instead default SSL Upload form is opened. In other case for "forward to", its open the option to choose Lets Encrypt for SSL. Click on Lets Enrcypt open a dialog for input mail address, but the submit button (named "get it...

Username: Azurel TITLE Wrong SSL certificate for ALL alias domains PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian Version 18.0.33, CentOS Linux 8.3.2011 PROBLEM DESCRIPTION I got few mails for alias domains In plesk none alias domain is working anymore for a...

CentOS Linux 8.3.2011, Plesk Obsidian Version 18.0.33 I get today mails with: Your certificate (or certificates) for the names listed below will expire in 19 days (on 15 Mar 21 08:20 +0000). Please make sure to renew your certificate before then, or visitors to your website will encounter...

I checked the banned IPs and this system is still a mess. This has an impact on security and performance! Since august 2020 I have disabled my important script which import and ban country ip-ranges, which call firewall-cmd --reload because this issue here and now I see there is still a huge...

Is there any news on the issue yet. As noted, you can no longer import IPs, because it resets the bans from Plesk without this being noticed in Plesk.

Username: Azurel TITLE Unable to remove some IP addresses from the list of banned addresses PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS Linux 8.3.2011, Plesk Obsidian Version 18.0.32 Update #2 PROBLEM DESCRIPTION A comodo rule runs amok with false-positive, so I must unban many...

Probably in this form

What is the correct way to disable PHP for a (CDN-)Domain? Disable PHP in PHP-Settings ends with automatic download the php-file. I want PHP files in CDN, but I want something like a 404 or 403 by access. It should not execute and it should not download the php-file. That is not working...

Username: Azurel TITLE PhpMyAdmin sudden timeout PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS Linux 8.2.2004 (Core) Plesk Obsidian Version 18.0.31 Update #1 PROBLEM DESCRIPTION This is in all plesk versions. Login in plesk and pick a subscription and go to database ->...

Username: Azurel TITLE Block repeated 403 Forbidden requests with Fail2Ban as included plesk-jail - Feature Request PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE CentOS Linux 8.2.2004 (Core) Plesk Obsidian Version 18.0.31 Update #1 PROBLEM DESCRIPTION I currently have tens of thousands...

This first line location ~* ^/(.*\.(css|js|jpeg|jpg|png|gif|webp............ blocks nothing. This line check its a real file try_files $uri @fallback; for catch this files for set caching.

@blueberry The solution here is that you must disable nginx settings for - Serve static files directly by nginx - Enable nginx caching and put this code in Additional nginx directives location ~* ^/(.*\.(css|js|jpeg|jpg|png|gif|webp|......ADD_ALL_FILE_TYPES_YOU_NEED.......))$ { try_files...

@IgorG What is here the status? In my Obisidian there are this two rules set by default, what is here the detect pattern? I found for COMODO more very critical bad rules that block visitors that visit a page or use a search function on it. 211120 => Match of "endsWith...

Thanks! Yeah this time its was a Comodo rule to add "211120". After 2 years I forgot about this. I have make me a notice. ;=) I don't get it what here happen. This match make no sense.

This issue still exists 2 years later. How I can use matomo without block page visitors?

Issue still exists in new version 5.0.3