Search results

Thank you for the confirmation. I will consult with our team further on this and follow up with more details as soon as possible.

Thank you for the clarification, @Frank.P . We were able to reproduce the issue and the same has been identified as a bug with ID PPPM-15045. Our team will introduce a fix in one of the upcoming releases. You can monitor the changelog here. At this point, I cannot suggest any workaround. Thank...

@chris-design , essentially this allows you to switch (define) another Dr.Web update server. If the issue is on their end as suspected, changing the destination server should sort it out. If the 81.176.67.172 entry does not produce good results, you may use one of the alternative IPs.

Have you already tried: If not, please give it a go and let us know if it solves the issue.

Thank you. The issue was investigated by our team and they determined the issue is on Atomicorp's end. They aknowledged the issue and it should be sorted out now. Please do let us know if you continue experiencing any difficulties with the download.

Hello, @Frank.P . Please provide more details on the issue you are experiencing, such as what actions exactly you are performing when you encounter the error, have you performed any recent changes, etc.

Peter, I discussed the matter with our team and, unfortunately, it is currently unavoidable to run plesk bin http3_pref --enable -nginx due to how the configuration system is architected. Enabling HTTP/3 globally is necessary to expose the per-domain control in the UI and backend. The intent of...

Hi everyone, The WebPros team is working on improving the look and feel of our dashboard interfaces — and your feedback can make a real difference. We've prepared a short visual test (just 4–6 minutes) to better understand how different UI themes are perceived and whether the current design...

Thank you. Unfortunately, I cannot identify the reason for the issue. I would suggest opening a ticket with Plesk support for further investigation on your server. To sign-in and open a ticket please go to: https://support.plesk.com If you got your license from a reseller, your reseller is...

Hello, @GillKidson . Can you please provide some more details? A good start would be your server OS, Plesk version, and the webmail service. If you are using SmarterMail and your Plesk version is below 18.0.69 Update 3 the issue is caused by a bug, which has been resolved.

Hello, @reka000 . Could you please test if you are able to install the Configuration Troubleshooter: I would also recommend reviewing the /var/log/plesk/installer/autoinstaller3.log for any errors/warnings.

Thank for the update. It looks like the issue is triggered by the same error reported in your other thread.

Hello, Peter. You are right, HTTP/3 needs to be turned on globally by plesk bin http3_pref --enable. I will consult with our team about your concerns on Monday and follow up with more details.

Hello, @Erwan . If I understand correctly and you would like to create a CNAME for 'a.com' pointed to 'cdn.a.com' this is not possible in Plesk regardless of being alias or not...

Our team is currently reviewing this case. It is still unclear what exactly causes the issues as it cannot be reproduced on every environment. I will follow-up with more details as soon as possible. Thank you in advance for your patience in the meantime.

Hello, @Colonel36 . Sounds like the system database has been corrupted. If you have system backups available, I would suggest to try restoring it.

From your Plesk panel, please search for the "SSH Terminal" tool and then execute the following command: If there are no entries, please try:

Hello, guys. Our team is currently working on introducing a fix for the issue with the DKIM records migration. The ETA is the end of August. Unfortunately, there is no workaround apart from moving the records manually.

Thank you for the update. This is actually my mistake, apologies for any possible confusion caused. Our team addressed a bug about warnings related to other packages. We do have a bug registered for the warnings reported in your message identified with PPPM-14983, which is still in our team's...

@brother4 , thank you. Unfortunately, none of the entries helps to identify what the issue could be. It is possible that during the process, the update of sw-engine package wasn't executed properly, hence, resulting in the errors in provided in your initial messages. However, I cannot confirm...