Case #5083 - Notify admins upon detection of admin directory configuration issue

[sentq]

someone else find a fix rather than the old init.php file, seems like the issue related to the folder path, check:

Okay, I managed to get in to the login page by setting the $customadminpath to a full relative path. My WHMCS is setup in a sub-directory so my path is /clients/mycustomadmindir. Never needed the /clients/ part before upgrading to 5.3.10.

http://forum.whmcs.com/showthread.php?93362-5-3-10-and-customadminpath

[Infopro]

Multiple threads merged here.

[durangod]

thank you all for posting... same issue here...

 

- - - Updated - - -

 

Well that actually removes the customisation tricks that WHMCS itself provides as extra security, not sure if a check like that (for the false admin dir) is necessary.

 

Maybe if they are going to check for the admin dir they can first check to see if the fake admin mod is installed first. Something like this maybe:

 

if(isset($customadminpath))

{

// skip the admin check

 

}

 

 

Well i guess that means that WHMCS does not use fake admin mod on their test environment lol oops

 

 

I also concur that uploading 5.3.9 init in the whmcs root will also allow you to finish the update as well so you will be at 5.3.10 as you would expect. So this temp fix does work... however just remember to replace that file with the 5.3.10 init when they get a fix done.

Edited September 17, 2014 by durangod

[ryan.odwyer]

Same issue here, running IIS on 2008 R2, putting 5.3.9 init.php back into 5.3.10 works as above.

[sentq]

Same issue here, running IIS on 2008 R2, putting 5.3.9 init.php back into 5.3.10 works as above.

http://forum.whmcs.com/showthread.php?93327-Case-5083-Notify-admins-upon-detection-of-admin-directory-configuration-issue&p=391774#post391774

[TND]

http://forum.whmcs.com/showthread.php?93327-Case-5083-Notify-admins-upon-detection-of-admin-directory-configuration-issue&p=391774#post391774

 

i have another problem when follow your step

 

Language Folder Not Found

[Matt]

A hot-fix is now available for this issue at http://docs.whmcs.com/HotFixes#Version_5.3.10

 

Matt

[clopezi]

A hot-fix is now available for this issue at http://docs.whmcs.com/HotFixes#Version_5.3.10

 

Matt

 

This not solve the problem with the fake admin directory.

[SteveR]

I'm seeing "Admin Directory Conflict" as well (And posted about it on a separate thread). Yesterday my installation of WHMCS worked, today it does not. That's despite me not changing anything so I can only assume that the latest update has been applied by cpanel/Installatron and that update has caused this issue.

 

I have never used or created a 'fake admin folder' and I'm on a Linux system. The update was installed by cPanel/Installatron.

I now cannot log in to the admin area.

[knritsolutions]

A hot-fix is now available for this issue at http://docs.whmcs.com/HotFixes#Version_5.3.10

 

Matt

 

 

Matt does this also apply to Linux servers? It specifically states Windows.

 

Thanks!

[WHMCS Patrick]

Matt does this also apply to Linux servers? It specifically states Windows.

 

Thanks!

 

This hotfix is specifically for Windows platforms.

 

If you are getting the Directory warning and you are not on Windows, submit a ticket and we'll get ya sorted out!

 

-Patrick

[knritsolutions]

This hotfix is specifically for Windows platforms.

 

If you are getting the Directory warning and you are not on Windows, submit a ticket and we'll get ya sorted out!

 

-Patrick

 

 

Thank you Patrick - I'm on CentOS and had the issue but replaced the init.php from 5.3.10 with the old one from 5.3.9 aa mentioned previously in this thread and it's working fine now - should I leave it this way or are there security concerns doing this? I can still put in a ticket if desired.

 

Thank you!

Lou

[Skinner]

Think I will hold back, can you let us know when it's safe to update.

 

Thanks

[grindkore]

Same thing happened to us this morning. Applied the 5.3.10 patch broke the custom admin folder. Thank god found this thread we were shut down for 30 minutes while I was poking about WHMCS. We are running IIS7.5 Fast-cgi.

[merlinpa1969]

Seems the simple solution would be to remove the check for the bogus admin directory

[clopezi]

Seems the simple solution would be to remove the check for the bogus admin directory

 

Exactly... it's so easy... a option in the admin zone to uncheck this check.

 

Since WHMCS is a software with so many bugs, at least not break the additional security measures that some users we have implemented...

[joedavis]

WHMCS sent me a patch for this and explained that the issue is related to my use of IIS for hosting the WHMCS site. I applied the patch and all is well.

[wsa]

This not solve the problem with the fake admin directory.

 

That true same problem with the fake admin folder. I can not use a fake admin folder

[Jaggl]

working here with the hotfix...

 

you dont need the line in your config

 

$customadminpath = "admin";

[mdeinhardt]

Same here on CentOS and with a fake admin folder. Waiting for fix...

[merlinpa1969]

WHMCS sent me a patch for this and explained that the issue is related to my use of IIS for hosting the WHMCS site. I applied the patch and all is well.

They have issued a fix for this for windows users, the rest of us are stuck waiting for them to fix it. It was whispered to me that maybe they did this on purpose to cut down the number of tickets for people that forget to properly upgrade when they have changed the admin username in the past. I can see and understand that, however for those of us that track folks attempting to get into the /admin folder it kinda defeats the extra security Plus I love it when people get the nasty gram that we post to the screen after the third failed login attempt in the fake admin

[brian!]

isn't one of the temporary fixes for this is to use the init.php file from v5.3.9 instead?

 

http://forum.whmcs.com/showthread.php?93327-Case-5083-Notify-admins-upon-detection-of-admin-directory-configuration-issue&p=391662#post391662

[Hein]

Yep, same here. Used the fake dir for catching the baddies .... seems like threading the wrong path on this one WHMCS.

[durangod]

Yep brian im not sure why so many just dont put the 5.3.9 init back and wait for a fix. It still lets you update to 10 all you will need to do is just put the 10 init back when they get a fix. Deep breath people and relax... its not a fatal issue if you just use the 5.3.9 init and wait.

[merlinpa1969]

Hi Duran, while your suggestion is a good one I think it is kind of a fatal issue. especially since there seems there wont be a fix.

the next passage is from the current changelog, seems like this is done on purpose

Case #5083 - Notify admins upon detection of admin directory configuration issue

 

Case #5083 is an attempt to make the upgrade process more fool-proof. We have found in recent releases that a lot of users apply an update forgetting to take into account their custom admin directory settings. The results of this are that you end up with the newer files in the default /admin/ directory, and then experience errors and problems due to attempting to use WHMCS with older files still present in their custom admin directory. So as of this update, you will be prompted any time a custom admin directory name is configured and a default /admin/ directory is found also. You will not be allowed to continue using the admin area until the default /admin/ directory is removed. If you encounter this error, please ensure you have uploaded all the files from this and any recent updates into your custom admin directory before removing it.