Search results

Hello, Thanks for reporting the problems, I was able to reproduce it. The bug EXTPLESK-10033 is confirmed and will be fixed in one of the upcoming versions.

Hello, @Movak . Could you please also check the redirect using CURL, with command like curl -I https://youralias.com. The most tricky moment with 301 redirect - that it's a permanent redirect, so it could be cached by your browser.

Hello, @riick. To be honest - it sounds a little bit strange, that you didn't face the problem with your old server, because the problem is typical for MariaDB 10.6. From MariaDB 10.6 default char set for utf8 was changed from utf8mb4 to utf8mb3. Maybe you have custom my.ini in the old server...

Hi, @adamsargant . You can use update-dbuser command to update the ACL. Something like this: plesk bin database --update-dbuser dbuser -set-acl 1.2.3.4,4.3.2.1 -server localhost:3306

It's not a part of panel.ini or any other config and can not be modified safely, if you are interested about this aspect of building.

Hello, @Leta. It looks like the problem with DoS preventing. I think you could try the following article - https://support.plesk.com/hc/en-us/articles/16752461985943-Some-pages-of-a-website-on-Plesk-for-Windows-return-403 .

Hello, @AlexLaforge. Unfortunately, there is no way to add any custom ODBC driver to Plesk. But if you want to see support of some specific ODBC driver - you can create a feature suggestion using UserVoce.

Hi. "Unsupported file format" most possibly means that file doesn't recognized as test file. Could you please show the output of next command: # file /var/www/vhosts/<your subscription domain>/httpdocs/config.ini For usual ini file, there should be something like "myfile.ini: ASCII text". If...

Hello. This option actually secure mail service connection by your domain certificate. You can read more in the related Plesk guide

Hello. According to your screenshot - you provide an HTTP address as a repository URL. But authorization by SSH Key works only with SSH cloning. So you should go to your GitHub repository, find Clone option and choose SSH. After that, you will get a URL, that looks like...

Looks like the problem is in disabled SSH access in hosting settings. You can use this KB article - How to grant a subscription user SSH/SFTP access to its home directory in Plesk - Support Cases from Plesk Knowledge Base. I think that every option except "forbidden: or "chrooted" will works...

Hello, You can try to add few more options to Nginx and Apache from articles https://support.plesk.com/hc/en-us/articles/12376956284695-How-to-upload-large-files-to-a-website-hosted-in-Plesk and https://support.plesk.com/hc/en-us/articles/12377537186711

Hello, Upgrade to the latest version major doesn't happen right after release. All Plesk servers are upgrading from the previous version to the latest by small bunches during 4–5 weeks after release. So if most of your server already upgraded to the latest version, and few still don't - it's...

Hello, If you are using Git extension to pull your changes from a remote repo, you can use Deploy Action in Domain -> Git -> Settings (lower right corner of Git overview card). There you can enable "Enable additional deployment actions" checkbox and write any shell code you want. This code will...

Hello, Thank you for the information, bug PPP-61978 confirmed. Unfortunately, there is no workaround available, but we will fix the issue in one of nearest upcoming releases.

Hi. I checked URLs from the screenshots, and right now it looks, like you have assigned domain certificate (mystifying-cray.3-11-62-26.plesk.page) as a Plesk Panel certificate, because https://3-11-62-26.plesk.page/ is secured by this certificate. But mystifying-cray.3-11-62-26.plesk.page site...

Hello all. Thank you for the information. The issue is caused by recently discovered bug #EXTGIT-232 which will be fixed in the nearest Git extension update. As a temporary workaround, following KB article could be used...

Hi. Yes, you can try to rerun the Plesk installer one more time. As an example, you can use this article - https://support.plesk.com/hc/en-us/articles/360018135640-Plesk-Obsidian-upgrade-on-Windows-get-s-stuck-or-fails-this-operation-returned-because-the-timeout-period-expired . It describes...

Hi, Jonium. Can you check, does the file `C:\Program Files (x86)\Plesk\admin\plib\vendor\react\promise\src\functions_include.php` actually exists? If not, it looks like a broken installation of Plesk, when only part of the files of Plesk 18.0.41 was applied. So probably you should check Plesk...

Hi, GhaithJ. I hope this instruction will be helpful - https://support.plesk.com/hc/en-us/articles/360014611379-Plesk-was-partially-removed-by-mistake-along-with-psa-database