Search results

Yes, that works if it has already scanned your website and sees that there are multiple folders with a composer.json file. If you have scanned and then add a folder with a composer.json file there is no way to have the website rescan for composer.json

as someone who builds saas companies and owns one myself, you and i both know that it is extremely unreliable to use a voting systems like this to determine the direction of software. i have used plesk 20 years and not once has the 3 owners ever reached out to me asking about features i struggle...

here we are 4 years later - no rescan function yet. has cost me many hours of development time trying to create a workaround when this happens.

If i rename a domain under hosting settings and then try to access PHP Composer for that domain it asks me to scan the website for composer scripts (this is a domain i had already done this in the past for) and when i click scan - Could not scan domains for Composer applications: There is no web...

i have a clean version of plesk on a brand new server, went to extensions and installed node and am using node 12, i am getting the same error when trying to run my node app. /usr/bin/env: node: No such file or directory but when i do [root@host httpdocs]# ll /usr/bin/env -rwxr-xr-x 1 root...

I am sure you figured out this by now but thought i would add it for the rest of the internet who may be looking. In the <vrt_hst> section add a new property type. <property> <name>seo-redirect</name> <value>www</value> </property>

anyone have any ideas when the Event Viewer will be fixed to work per the documentation? Its clearly not passing variables on like it states it does.

file and output Here is my shell script #!/bin/bash COMPDATE=`/bin/date` echo "$COMPDATE - [${COMP_IP_ADDRESS}] - (${COMP_LOGIN_NAME}) User Authentication Failed" >> /var/log/psa-cp.log Here is what it outputs Tue Nov 6 17:37:37 CST 2012 - [] - () User Authentication Failed

hmm... might work if... event handlers worked according to the documentation it doesn't work. 1) If you create Shell script EXACTLY as described and choose the event panel user failed login no vars are passed on to the shell script. 2) Because no vars are passed on there is no way to...

I have fail2ban running on my server and i want to have it be able to check brute force attacks on the plesk panel login itself. Action log today recorded 43,000 attempts to log in... would have been nice to ban after the first 4 but the results are in a database from what i can tell and not...

Ohh yes... without a doubt i always manually copy the databases, database users (in case it was done outside of Plesk) manually copy emails (just before I repoint name servers) manually copy data (just before I repoint) Also as a thumb rule i always keep old server for a week to ensure...

I wish this feature worked. It however does not. Multiple attempts to remigrate domains with the option checked to overwrite existing data failed with the same error. User already exists. I had to delete all subscriptions delete all users from /etc/passwd (because deleting the...

Looks like the migration tool has much more errors than just yours. I got a new server... migrate from plesk 10 to plesk 11 and i get nothing but user already exists errors. I follow instructions on how to purge destination server of these users... go back into migration manager and try...

Well i will try anything... This happens from gmail as well as exchange... Executed command and it didn't change anything. Of course... in POSTFIX /etc/postfix/main.cf if i edit it and comment out smtpd_milters = inet:127.0.0.1:12345, inet:localhost:12768 the error goes away...

PS with all spam filters off and greylisting turned off on the mail settings still gives me the same error.

I am running Plesk 10.4.4 on Redhat ES5 Email service is Postfix with MagicSpam module installed. The problem i am about to describe happens if MagicSpam is on, disabled, installed, and uninstalled so i can rule that one out. Mail Service settings only have greylisting checked...

How strange. Provide server info...as in what linux type and plesk version. It worked for me seemlessly on Redhat5.3 Plesk 10.4

restart PSA service service psa restart

Yes there is now a KB article on it. http://kb.parallels.com/en/9327 I used it not long ago and am happy to be free from it. The continued websites being turned off automatically even though i changed subscription plans and set renewal to unlimited among other issues got too much for...

In closing... If thats the only problem i have as a result of the update... It really is the smoothest update of Plesk so far... off to see what else I can fine. My luck and the API will be fixed this time.