WP toolkit can't scan for exiting site

PeterN123

Active Member
Aug 4, 2021
35
5
8
Australia
cPanel Access Level
Root Administrator
Hello everyone,

WP Toolkit generally works well for me, but on 1 account, it just won't detect an exisitng Wordpress installation.

Any pointers?

Thanks everyone
 
Last edited by a moderator:

andrew.n

Well-Known Member
Jun 9, 2020
982
363
63
EU
cPanel Access Level
Root Administrator
You need to provide us more info here. Is the WP install at the root of the account? is there multiple installs under the same folder? Is there any other files/softwares installed there as well? You should be able to attach a WP install using command line:

 
  • Like
Reactions: cPRex

PeterN123

Active Member
Aug 4, 2021
35
5
8
Australia
cPanel Access Level
Root Administrator
You need to provide us more info here. Is the WP install at the root of the account? is there multiple installs under the same folder? Is there any other files/softwares installed there as well? You should be able to attach a WP install using command line:

Hello,

I tried that script and it didn't worked for me also, I ran it under root:

Code:
 wp-toolkit --register -domain-name mydomain.com -path /home/mydomain/public_html
The site was migrated over cpanel a long time ago, I think I iniitially installed WP using Softaculous.

No there is no other installation under the same folder or even cPanel account.
 

Spirogg

Well-Known Member
Feb 21, 2018
700
163
43
chicago
cPanel Access Level
Root Administrator
This is what I got after running the command:

Code:
Warning: Current locale is unusable. Using 'C' instead.
WordPress installation was added to WordPress Toolkit.
I checked WPtoolkit on both Cpanel + WHM, still not added :-?
@PeterN123
what did you get when run

Code:
locale
UPDATE:
This is what I get on my server with AlmaLinux 8.5.0

Code:
[root@server1 ~]# locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
and
Code:
locale -a
what operating system are you using ?
 
Last edited:

Spirogg

Well-Known Member
Feb 21, 2018
700
163
43
chicago
cPanel Access Level
Root Administrator
You can find global locale settings in the following files:

  • /etc/default/locale – on Ubuntu/Debian
  • /etc/locale.conf – on CentOS/RHEL
or more information, see the locale, update-locale and localectl man pages.

$ man locale
$ man update-locale
$ man localectl

I think you need to update your locale

These files can also be edited manually using any of your favorite command line editors such as Vim or Nano, to configure your system locale.

it seems its giving the error C cause it needs to use LANG=en_US.UTF-8

I think now it's using C.UTF-8
 
Last edited:

PeterN123

Active Member
Aug 4, 2021
35
5
8
Australia
cPanel Access Level
Root Administrator
You can find global locale settings in the following files:

  • /etc/default/locale – on Ubuntu/Debian
  • /etc/locale.conf – on CentOS/RHEL
or more information, see the locale, update-locale and localectl man pages.

$ man locale
$ man update-locale
$ man localectl

I think you need to update your locale

These files can also be edited manually using any of your favorite command line editors such as Vim or Nano, to configure your system locale.

it seems its giving the error C cause it needs to use LANG=en_IN.UTF-8

I think now it's using C.UTF-8
Thanks so much, it is currently running:

LANG="en_US.UTF-8"

Do you think I should change to LANG=en_IN.UTF-8?
 

Spirogg

Well-Known Member
Feb 21, 2018
700
163
43
chicago
cPanel Access Level
Root Administrator
Thanks so much, it is currently running:

LANG="en_US.UTF-8"

Do you think I should change to LANG=en_IN.UTF-8?
I change it to US sorry I write down IN by mistake the correct one should be en_US.UTF-8
 

Spirogg

Well-Known Member
Feb 21, 2018
700
163
43
chicago
cPanel Access Level
Root Administrator
Thanks so much, it is currently running:

LANG="en_US.UTF-8"

Do you think I should change to LANG=en_IN.UTF-8?
I change it to US sorry I write down IN by mistake the correct one should be en_US.UTF
Thanks so much, it is currently running:

LANG="en_US.UTF-8"

Do you think I should change to LANG=en_IN.UTF-8?
run this command

cat /etc/locale.conf
 

Spirogg

Well-Known Member
Feb 21, 2018
700
163
43
chicago
cPanel Access Level
Root Administrator
Sure, this is what i got:

Code:
LANG="en_US.UTF-8"
Please note, It didn't make any changes.
yes no just getting information

what system are you using ? Almalinux ? centOS 7 ? Ubuntu ?
 

Spirogg

Well-Known Member
Feb 21, 2018
700
163
43
chicago
cPanel Access Level
Root Administrator
Yes, I am running CentOS 7, just weird that all others WP working fine just except this site.

The language of the site is Vietnamese by the way.
is that the only one that is Vietnamese ?
 

PeterN123

Active Member
Aug 4, 2021
35
5
8
Australia
cPanel Access Level
Root Administrator
is that the only one that is Vietnamese ?
Ah no, not at all. There are a few sites in there that is vietnamese as well.

1 thing I want to note is that, the site was detected properly.

2 weeks ago, the site went down due to updates, I then recovered the site from Jetbackup 5, I am unsure if was able to be detected at that time, I just recently try again and it can't be found by WPtoolkit anymore. :-?

Just odd.
 

Spirogg

Well-Known Member
Feb 21, 2018
700
163
43
chicago
cPanel Access Level
Root Administrator
Ah no, not at all. There are a few sites in there that is vietnamese as well.

1 thing I want to note is that, the site was detected properly.

2 weeks ago, the site went down due to updates, I then recovered the site from Jetbackup 5, I am unsure if was able to be detected at that time, I just recently try again and it can't be found by WPtoolkit anymore. :-?

Just odd.
when going to the website it is working yes ? or completely down
 

Spirogg

Well-Known Member
Feb 21, 2018
700
163
43
chicago
cPanel Access Level
Root Administrator
Ah no, not at all. There are a few sites in there that is vietnamese as well.

1 thing I want to note is that, the site was detected properly.

2 weeks ago, the site went down due to updates, I then recovered the site from Jetbackup 5, I am unsure if was able to be detected at that time, I just recently try again and it can't be found by WPtoolkit anymore. :-?

Just odd.
@PeterN123

ok just found something interesting.. maybe you can try this

go to that users home directory and see if this file is there .wp-toolkit-ignore

check home/ and home/public_html

if found rename that file DO NOT delete it just rename to .wp-toolkit-ignore.bkp
so after we try to scan and find it - if it still does not we can rename back to the original name

just rename for a moment then try again to scan and see if it finds it this time

I found this on Plesk which is how we got the Wordpress toolkit from.

Cause
Starting from WordPress Toolkit 5.9.2 detached WordPress instances are no longer re-added through the Scan procedure, making their detachment permanent.

Resolution
If the website should be added to WordPress Toolkit back for some reason, perform the following:

  1. Log into Plesk.
  2. Go to Domains > example.com > File Manager.
  3. Find and remove the .wp-toolkit-ignore file in the domain's document root.
  4. As soon as the file is removed, go to the WordPress menu and re-scan instances.
SO I would assume same for cPanel

that's why I asked if that file is in that users home / directory or public_html folder

this might cause it not to find it as stated above in Plesk statement ..
 
Last edited:

PeterN123

Active Member
Aug 4, 2021
35
5
8
Australia
cPanel Access Level
Root Administrator
@PeterN123

ok just found something interesting.. maybe you can try this

go to that users home directory and see if this file is there .wp-toolkit-ignore

check home/ and home/public_html

if found rename that file DO NOT delete it just rename to .wp-toolkit-ignore.bkp
so after we try to scan and find it - if it still does not we can rename back to the original name

just rename for a moment then try again to scan and see if it finds it this time

I found this on Plesk which is how we got the Wordpress toolkit from.

Cause
Starting from WordPress Toolkit 5.9.2 detached WordPress instances are no longer re-added through the Scan procedure, making their detachment permanent.

Resolution
If the website should be added to WordPress Toolkit back for some reason, perform the following:

  1. Log into Plesk.
  2. Go to Domains > example.com > File Manager.
  3. Find and remove the .wp-toolkit-ignore file in the domain's document root.
  4. As soon as the file is removed, go to the WordPress menu and re-scan instances.
SO I would assume same for cPanel

that's why I asked if that file is in that users home / directory or public_html folder

this might cause it not to find it as stated above in Plesk statement ..
Hey I actually did that before but couldn't find the wp-toolkit-ignore file.

BUt, I just tried changing site PHP to 7.3 and it is now detected :| Super weird.

I then revert it back to 7.4, it is detectable now, any idea how this happen?
 
  • Like
Reactions: Spirogg

Spirogg

Well-Known Member
Feb 21, 2018
700
163
43
chicago
cPanel Access Level
Root Administrator
Hey I actually did that before but couldn't find the wp-toolkit-ignore file.

BUt, I just tried changing site PHP to 7.3 and it is now detected :| Super weird.

I then revert it back to 7.4, it is detectable now, any idea how this happen?
I will have to defer that question to someone else @cPRex when or someone whom might have that answer. The good thing is it worked :) maybe php.ini was 7.3 prior to transfer and update from jet 5 when you recovered the site ?
I am not 100% sure.
At least there was some workaround that worked. Im glad it works
:)
 
  • Like
Reactions: PeterN123