XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. Beginner's Corner 
  4.  / Protector detects site manipulation
Register
1
redheadedrod
Protector detects site manipulation

I have this error coming up on my web site and not sure how to reset it...

I have a new web hosting company and setup new sites for a couple sites I am running and got them running the way I wanted before I pointed the nameservers to them..

The sites were reached by the following URL..

newsite.host.com

where newsite was the new version of the old site and host.com is the main web page on my host...

When I transfered the sites nameservers over now I can access the new site with the following URL..

newsite.com

However I get the above error now and can not log into Xoops.

This is a fresh install with XOOPS 2.4.3 and Protector 3.5(Beta).

I am assuming that all I need to do is reset some flag in protector and it will work but how does this work?

I know no one has hacked the site so I know it is just due to my switching the name servers.

Hoping someone can offer a solution.

Thanks!

Rodney
2
Burning
Re: Protector detects site manipulation

  • 2010/1/14 15:54

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


hi'

I do not understand wich (new) feature in Protector causes this problem. Perhaps some explanations are available on developer website ? (http://xoops.peak.ne.jp/)

To solve this problem, you have to uninstall Protector (complete desinstallation). To do so :

1) go to PhpMyAdmin
2) open _module table
3) find Protector line and clic on edit icon
4) for field [isactive] enter 0 instead of 1

Now Protector is just desactivated, and you can access to your site. Uninstall Protector and install it immediatly.

... perhaps there is a better way, but it has worked for me (Xoops 2.4.x and Protector 3.5)
3
redheadedrod
Re: Protector detects site manipulation

Thanks, will give this a shot when i get home unless someone else has a better option.
4
redheadedrod
Re: Protector detects site manipulation

I did this and verified it is correct in the database and it still is apparently active?

I do not have access to my site still.. Shows the same message.

I CAN just delete the site and restart it but was hoping not to...

5
ghia
Re: Protector detects site manipulation

  • 2010/1/14 22:25

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


If your site has been moved or changed, it is likely, that some definirions in the mainfile.php do no longer correspond to the real situation of URL and file paths.

'Protector detects site manipulation' I this the real error message? Where do you see that? Are there other statements?

I see you use the Protector 3.50 version, which is still beta. Ask your questions about the new features and problems of that version on the developers' site.

Else try to reinstall the original version 3.40 of the XOOPS 2.4.3 distribution.

6
Burning
Re: Protector detects site manipulation

  • 2010/1/14 22:36

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


hi' ghia

Quote:
'Protector detects site manipulation' I this the real error message?


... yes it is, and impossible to display Debug mode.

Resized Image

(I have just edited mainfile.php by adding a blank line after <?php)

As said above, there is a solution : uninstall Protector and re-install. To delete content of xoops_lib/modules/protector/configs/ does not make effect.
7
redheadedrod
Re: Protector detects site manipulation

Yes this is the error it shows. And no other information is available.

Weird thing is I did the same thing with another site and it did NOT do this...

Fortunately the site it did not happen with was the site I needed the most. I will likely back track to 3.4 or the 3.41 that was listed on the site as available.

If I were to manually uninstall Protector what areas do I need to look at?

I will likely look in the module files and try identifying the install script and basically try undoing it but I hate to do that not really knowing what all is effected outside of it. Since the sites I have this error on are in their infancy I can easily start from scratch but I will likely try to remove protector manually first before attempting this.

Assuming all there really is are the files in the docroot, trusted lib location and the database entries. Once I delete the database entries it should be as simple as deleting the two module directories and then going back and reinserting the older protector module or simply reinstalling the beta module.

Am I missing anything?

Thanks.

Rodney
8
Burning
Re: Protector detects site manipulation

  • 2010/1/15 16:51

  • Burning

  • Theme Designer

  • Posts: 1163

  • Since: 2006/8/22


hi'

As said above, the first thing is to desactivate Protector (I don't know other solution) because when you get :
Quote:
Protector detects site manipulation

... you can't do anything !

So (read before for instructions) :
1 • disable Protector -> alert disappear and you can get to administration
2 • uninstall Protector -> if you enable Protector without desinstallation, alert reapper. So uninstall completely Protector
3 • install Protector again (personnally I keep Protector 3.50, but you can prefer older version)

Before handling database, make a back up !
9
redheadedrod
Re: Protector detects site manipulation

And to clairify, The NEW site I put up has had nothing change in it physically. While setting it up and testing the base services I was able to access it via the URL, mysite.host.com. or in other words as a sub domain of host.com. I can STILL access the site in this manner (Although it still shows the same Protector error).

I have ADDED a method of getting to the web site however by changing the name server for the original web server which hosted the original mysite.com. Now when you go to mysite.com you go to the newer one which is also accessable by the mysite.host.com domain name.

I believe Protector got confused by the changing of the name server and being accessed by the mysite.com URL instead of mysite.host.com URL and has since shut down the site by displaying the above error and not providing a means for accessing the system.

I am busy today so I am hoping by putting this out here someone else has a suggestion. I will be addressing this one way or another on Saturday (US eastern time). Pending activation on the support site to ask about this there.

Rodney

10
ghia
Re: Protector detects site manipulation

  • 2010/1/15 16:54

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


I think best is to
delete first /modules/protector/preloads,
the module record of Protector in xoops_modules
then /modules/protector/
and /xoops_lib/modules/protector/
and then the Protector database tables.
Maybe some permission records has also to be deleted (reference is module id from step 2).
(1) 2 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

151 user(s) are online (100 user(s) are browsing Support Forums)

Members: 0

Guests: 151

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits