Search results

If you have no SSH access: When you are @Strato and use a V-Server: Login to https://login.stratoserver.net Start the rescue System Here it is important to first change "into your own system". so 1.) start rescue 2) ssh -> hint to /repair folder comes. 3.) change to your own system chroot...

Strato informs: No Plesk login possible? "Can't open or create shared memory by shm.name" Dear customer, Some PLESK users may not be able to login to PLESK due to a bug. The message may appear in the browser: [LockManagerException] Can't open or create shared memory by shm.name...

For me this was the solution: Plesk is not accessible: Can't open or create shared memory by shm.name

Plesk is not accessible: Can't open or create shared memory by shm.name That was the Solution!!! Thanx again!

Thanx you so much Igor for your fast support!!! But I'll wait and keep cool until a friendly admin is reachable. I'm afraid that I'll break something. Websites and mail still work for all clients at the moment. Only the Plesk login is not possible. If nobody can help, you can tell me the link...

I'm not very familiar with the console When i run # crontab -e i get: MAILTO="" 4 * * * * /opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/wp-toolkit/scripts/maintenance.php' 0 0 * * *...

I will now try a technical reqeust or do you have a better idea??? .... but Technical support form reports : We identified that the Plesk license was purchased not directly from Plesk but through one of the Plesk Resellers. The Strato Hotline is usually not responsible for the following. From...

Thanx Igor, but i tried it too: There are two warnings but there are from Wordpress/Enfold theme and another CMS. I've got them pretty much longer and they don't matter. Dont Know waht to do now. plesk repair fs -v -y root@h2519287:~# plesk repair fs -v -y Checking Linux system files...

Yes i tried...and found: Plesk is not accessible: Can't open or create shared memory by shm.name and Unable to open Plesk: Lock Manager error: Can't open or create shared memory by shm.name but that doesnt help. Reinstalling Updates gets stuck.

Starto V-Server, Plesk Onyx 17,8 Update 30, Ubuntu 16.04 LTS This morning after a reboot of the server i get this error and cant login to Plesk anymore. Websites work, Mail too. I executed plesk repair all and tried to change the owner rights but then detected that the folder "/run/lock/lmlib/...

I use Plesk 17.8 with Ubuntu 18.04.LTS on a Strato V-Server. There are several customers with Wordpress installations on the server. Using the Plesk Wordpress Toolkit I have activated in the settings of the instances that a snapshot or restore point of the Wordpress installation is always...

Thank you very much. It works for me!!!

Thank you very much for this very useful hints!!!

Please take a look here. Looks like the same error? Issue - Daily erroro message "run-parts: /etc/cron.daily/asl exited with return code 127"

I still get this Error Message every morning too. Daily error message "run-parts: /etc/cron.daily/asl exited with return code 127" i tried what Igor said 2 times: # apt-get update # apt-get upgrade # run-parts /etc/cron.hourly/ (daily(weekly/monthly too) # aum -c In the 2nd run no error...

OK, switched to OWASP ModSecurity, applyd and did a restart. I will let you know tomorrow morning or can I manually initiate the error message earlier? Had to switch over to Comodo coz OWASP blocked some functions.

Thanx a lot Igor. # apt-get update = no updates # apt-get upgrade = no upgrades # run-parts /etc/cron.hourly/ # aum -c # Configuring Atomic Secured Linux (ASL) 5.0-5664 for h2519287.stratoserver.net. -bash: syntax error near unexpected token `(' I dont know what to do now. Can you help again...

Me too. Ubuntu 16.04, Plesk Onyx 17.8 Update 26 on V-Server. Switched from Comodo to Atomic (ModSecurity) and back again, still get this mail.

When reinstalling the operating system and Plesk, the Plesk admin password is identical to the root password, at least for my provider (Strato V-Server). So to change the admin password in Plesk, the root password is "the old Plesk password". Maybe this is the reason?