Search results

As mentioned by @TorbHo already, the hotfix for PPPM-14661 is released. If anyone continues experiencing issues after the upgrade, please do let us know.

Hello, @EnriqueR. If you are using Grafana as a standalone extension, the issue you are experiencing is due to a bug identified with ID EXTPLESK-6085. Essentially, the data is being pulled through the Monitoring extension, so if the same is missing on the server it is normal to experience the...

Unfortunately, I am not quite sure how such limits are handled for a personal drive. I am sorry. You might want to double-check that with Google directly.

Hello, @shopuser, could you please also check if there are misconfigured packages: As for the Cannot fix %s: file exists and it is not a symlink error, you might try applying the following workaround.

I am glad to hear you were able to find the culprit of the issue. Thank you for providing the details, I am sure that will be of a great help to our team. I passed the information so they can continue investigating why would this cause the abnormal behavior in the MFA extension and possibly...

Hello, everyone. Could someone please run the plesk repair db -v -n command and provide the output either in a private conversation or in this thread? Thanks in advance for your cooperation.

Hello, @BigMaras. Could you please confirm the following details: Do you have ModSecurity enabled on the server? Do you have an .htaccess file with specific rules that might be resulting in the 403 error? Could you please check /var/www/vhosts/yourdomain.com/logs/error_log for the recently...

You can enable/disable the settings with the following commands: Turn on limitations on outgoing email messages: Fix incorrectly set sender for outgoing mail: Full documentation What I can think of is creating bash scripts and configuring cron jobs for the desired times to enable and...

First and foremost, thank you for your interest in helping bringing our attention to product issues, Ondrej . As pointed by @Maarten, the sole purpose of implying the rule for posting Bug Reports is to avoid unnecessary spam and keep reports constructive. We are by no means trying to make our...

We are currently investigating the reported error message. As soon as we have more details I will provide an update.

@Hangover2, the odd thing is that the extension was tested with double the number of users you are reporting before release and no performance issues were observed. Anyhow, I escalated the case for further review by our team and hopefully they will be able to find the culprit.

Thanks for the details, now we have some ground to start the investigation from. I will discuss the case with our team and will update you with more details shortly.

We understand the inconvenience resulting from the issue. Our team is currently working on implementing the most adequate fix for it. Unfortunately, I cannot provide any ETA on when the fix will be released. All I can confirm is that the case has been prioritized.

If possible, please apply the workaround previously pointed in this thread. We are currently working on releasing a hotfix, which is scheduled for the 12th of November. Please note that I cannot confirm on a 100% the fix will be released as some unpredictable complications may arise.

On the Forum, you can submit a bug report from Forums > Reports > Submit Report. Note that if you do not have the necessary points to submit a bug report, you can always submit it as a regular thread with instructions on how to reproduce the issue and a staff member will move it to the...

I appreciate your patience thus far. I discussed the cases with our team and both of them are prioritized for 18.0.66. Unfortunately, we still cannot provide any finality and confirm on 100% if the fixes will be delivered with the next release.

Hello, Chris. This is not a bug, hence, I moved the thread. The error you are experiencing "User rate limit exceeded" is due to a limitation set by Google Drive. According to Google's API documentation, there is a maximum limit of 10 requests per second. To modify these usage limits or request...

Hello, @ondrejvaroscak. Thank you for your report. That issue has been brought to our attention and the behavior is identified as a bug with ID EXTPLESK-5352. We will introduce a fix for it in one of the feature releases. You may monitor our change log here. Unfortunately, at this point, we...

@Will-NYESDigital, if you have the option to open a support ticket, please do. Given that, at this point, we are unable to reproduce the issue, it is quite difficult to point out what exactly the case is on your end.

Are you using any firewall on the server in question? If yes, have you already allowed the port?