Search results

Are you using incremental backups? Plesk first needs to download some info to ensure the main backup is there and match the new increment to the last one. I'm assuming this is what's happening so you can test without that option.

Plesk supports NFS, but you have to change the permissions as instructed in the guide so that Plesk can write to the partition. It should also be mounted to allow file locking. Otherwise, it will fail.

That's almost certainly the device's local cache. By now enough time must've passed that it fixed itself, but in the future you can just clear the local cache and reboot the phone (necessary on some iPhones) and then you'll see the right cert.

I have no clue about ModSec syntax, sorry for being useless there. I just wanted to suggest changing the ruleset to something else. Comodo is very inactive, and they haven't updated their ruleset in a while. It's possible this won't be a problem with a more actively developed ruleset like Atomic.

I just opened the site and it seems to be working. How did you fix this?

What ruleset are you using? Have you tried others?

What value are you using for the port in the app?

In these cases, the best is to get the license from a partner that provides it along with hosting, so it's cheaper (like IONOS).

Is it a ChunkLoadError? What's the full error?

Because of how VPN technology works, you can't put your entire server in a VPN so that the sites work everywhere. The Google VPN changes the IP address. Perhaps it's using IPv6 instead of IPv4 and this way the sites are accessible (that's just an example, can't tell what it is yet). What you...

When you use https://plesk-hosting.mydom.org, are you entering the Plesk port? i.e. https://plesk-hosting.mydom.org:8443

This is only necessary to change the value for existing domains. For new domains, you can just set the values you want in Service Plans > Example Plan > PHP

Yes, nginx is lighter than Apache by default and helps with higher traffic, but the configuration has to allow for it. You should match the nginx file limit to the one Apache has. That will prevent unnecessary crashes. Good to hear you're getting a lot of that traffic blocked now! Please tell...

Yeah, I haven't heard of anyone with an issue like this one. Did you import the content from a previous website? Sounds like the webspace has some file system issues during the publishing process. You should ask them to contact us so we can check the error logs from the system.,

Can't find anything about this error. What URL are you using to access Plesk?

Looks like LiteSpeed has some incompatibility with the new version. LiteSpeed is a third party and we don't have any channel to contact them. Could you guys report this to their support team? Support - LiteSpeed Technologies Just to confirm, though, it's just the extension that doesn't work...

Wonderful, great to hear that. Thanks @Sebahat.hadzhi

When does this happen? On log in or after you open some page?

plesk repair installation is not covered by plesk repair all

Awesome, thanks for the confirmation.