Search results

I would suggest then to contact the technical support to check this further

Please do check: https://support.plesk.com/hc/en-us/articles/12377464405527-Unable-to-open-Updates-and-Upgrades-menu-on-Plesk-for-Linux-server-Can-t-connect-to-backend-No-such-file-or-directory

Where did you download it from and what are the repos used?

The error is too general, I would recommend you to contact the Plesk Support team to investigate this further with server access. It could be permission issues, corrupted HDD/SDD, etc. You can try to find more specific errors in the event viewer, but it would be faster over the support since...

Duplicated of Issue - Plesk is not working Contact support over ticket as advised or check or check for InnoDB issues for example: https://support.plesk.com/hc/en-us/articles/12387817373207-How-to-fix-InnoDB-corruption-cases-for-the-MySQL-databases-on-Plesk-for-Windows-

Try: https://support.plesk.com/hc/en-us/articles/12377964180631-Plesk-for-Windows-login-page-shows-No-connection-could-be-made-because-the-target-machine-actively-refused-it Or contact Plesk support directly: How to get support directly from Plesk?

How are you trying to connect? over sftp?

Normally, should work the way you did it: Seems to be something with your shell configuration?

https://support.plesk.com/hc/en-us/articles/12377452798359--How-to-remove-Plesk-backup-files-and-their-logs

In Plesk Obsidian 18.0.53, such an option was added to correctly bounce it: https://docs.plesk.com/en-US/obsidian/administrator-guide/80013/#plesk-for-linux-rejecting-mail-with-forged-sender-address You would need to upgrade Plesk for it

seems you having network/firewall issues since it fails to connect to the ubuntu and plesk repos: Ign:45 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 apache2-data all 2.4.41-4ubuntu3.14 Err:154 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 locales-all amd64...

Normally, you can update it over commands like: plesk sbin sslmng --service dovecot --strong-dh --dhparams-size=2048 Did you do it manually?

This is a known issue under the ID #EXTREST-158 Until the bug is fixed, the following workaround can be applied: 1. Create a secret key (X-API-Key): # curl -iku admin:password -X POST -H 'Content-Type: application/json' -d'{}' https://hostname:8443/api/v2/auth/keys 2. Run the API-CLI call...

Additional question, are you using Litespeed web server? If yes, this 2 commands may help: mv /usr/local/bin/lsphp /usr/local/bin/lsphp-bk ln -s /opt/plesk/php/7.3/bin/lsphp /usr/local/bin/lsphp See Troubleshooting LiteSpeed Web Server with Plesk | LiteSpeed Documentation for reference

Search option here is a good friend :) You can find a tutorial made by a user here: https://talk.plesk.com/threads/not-happy-with-plesk-email-security.356732/post-901856

Linux does cache so the use being higher is normal, see: Help! Linux ate my RAM! Over SSH you can check it better with free -m, there you can see what is under the column “available” instead of the “free” But also 1 GB is not a lot of ram, so I would not expect too much of it :)

What mail server do you have set in the settings? Also, do you have an option on Macs Thunderbird to show the SSL? Security Certificate Expired | AVG There could still be leftover services from AVG running.

Are you using the IP or the Hostname to connect? Try with the IP if you did not It would also help if you provide the commands you're using to provide more information.

what are the exact commands you are using?

You can use the location directive under the domain. Just make sure that proxy mode is disabled. as an example for seafile, I used: server_tokens off; location / { proxy_pass http://127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Real-IP...