Looking for a ModX expert for update help

Our hosting company has shut down our http access due to the following below. I'm looking for somebody who can help me fix this problem. We're a non-profit but I'm willing to pay for some help here.


"When the outdated application within the [/home/cueartfo/public_html] directory is hit by search engines, very large database load is generated in relation to the retrieval of very old entries.

We have restricted HTTP access to this directory to prevent further abuse.

You will have to upgrade ModX to its latest release, ensure any caching functionality provided by ModX is properly configured, and ensure search engines are limited in what parts of the site can be accessed.
Once the files for the new ModX version are uploaded and we are notified of that fact, HTTP access will be restored."

Anyone out here who can help me?

You'll need to tell us what version of MODX is being used by the site.

Can you still log in at yoursite.com/manger ?

"ensure search engines are limited" can be done in .htaccess wich would solve a lot of your problems without having to upgrade MODX. But upgrading would be a good idea as well.

Bob, correct me if i am wrong here, but could they just manual upgrade and then be able to get into the manager? Seems like the hosting company is not all that savy about Modx.

They can update directly, but can't run setup or install or get into the Manager until the host unblocks them.

Personally, I would change hosts immediately. I'd never stay with a host that handled the problem in this way, and it's likely that their server is overloaded to begin with.

The OP hasn't checked back in almost a week, so most likely it's solved or the OP can't remember how to get back to this thread.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Hi,

You can add this to the end of your file .htaccess and should block all spiders (good and bad)

....

ErrorDocument 403 /403.html

# IF THE UA STARTS WITH THESE
SetEnvIfNoCase ^User-Agent$ .*(aesop_com_spiderman|alexibot|backweb|bandit|batchftp|bigfoot) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(black.?hole|blackwidow|blowfish|botalot|buddy|builtbottough|bullseye) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(cheesebot|cherrypicker|chinaclaw|collector|copier|copyrightcheck) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(cosmos|crescent|curl|custo|da|diibot|disco|dittospyder|dragonfly) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(drip|easydl|ebingbong|ecatch|eirgrabber|emailcollector|emailsiphon) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(emailwolf|erocrawler|exabot|eyenetie|filehound|flashget|flunky) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(frontpage|getright|getweb|go.?zilla|go-ahead-got-it|gotit|grabnet) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(grafula|harvest|hloader|hmview|httplib|httrack|humanlinks|ilsebot) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(infonavirobot|infotekies|intelliseek|interget|iria|jennybot|jetcar) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(joc|justview|jyxobot|kenjin|keyword|larbin|leechftp|lexibot|lftp|libweb) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(likse|linkscan|linkwalker|lnspiderguy|lwp|magnet|mag-net|markwatch) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(mata.?hari|memo|microsoft.?url|midown.?tool|miixpc|mirror|missigua) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(mister.?pix|moget|mozilla.?newt|nameprotect|navroad|backdoorbot|nearsite) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(net.?vampire|netants|netcraft|netmechanic|netspider|nextgensearchbot) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(attach|nicerspro|nimblecrawler|npbot|octopus|offline.?explorer) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(offline.?navigator|openfind|outfoxbot|pagegrabber|papa|pavuk) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(pcbrowser|php.?version.?tracker|pockey|propowerbot|prowebwalker) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(psbot|pump|queryn|recorder|realdownload|reaper|reget|true_robot) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(repomonkey|rma|internetseer|sitesnagger|siphon|slysearch|smartdownload) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(snake|snapbot|snoopy|sogou|spacebison|spankbot|spanner|sqworm|superbot) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(superhttp|surfbot|asterias|suzuran|szukacz|takeout|teleport) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(telesoft|the.?intraformant|thenomad|tighttwatbot|titan|urldispatcher) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(turingos|turnitinbot|urly.?warning|vacuum|vci|voideye|whacker) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(widow|wisenutbot|wwwoffle|xaldon|xenu|zeus|zyborg|anonymouse) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*web(zip|emaile|enhancer|fetch|go.?is|auto|bandit|clip|copier|master|reaper|sauger|site.?quester|whack) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(craftbot|download|extract|stripper|sucker|ninja|clshttp|webspider|leacher|collector|grabber|webpictures) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(libwww-perl|aesop_com_spiderman) HTTP_SAFE_BADBOT
SetEnvIfNoCase ^User-Agent$ .*(yahoo|google|bing) HTTP_SAFE_BADBOT

Deny from env = HTTP_SAFE_BADBOT


....


should also create a file called 503.html in your main root (public_html in your case) the content may be empty.

attention is not good practice to return error 503 to robots legitimate, if this continues
search engines, they will put your website on spampage list, as content void, and this is a shame because the ranking of your website is good.

if you need to test whether any of this spider can still come in, send me a message and we'll tell how to do the tests.

change the name of your robots.txt file to something like norobots.txt

done on again and should enter service with no problem in his "panel manager"


I think the same as Bob,
this is not a serious hosting. and everything I advise is to switch to hire dedicated servers, of course cost more, but performance is everything else and not share with anyone your hardware and software resources.

Regards. [ed. note: rtoskit last edited this post 14 years, 3 months ago.]

I've had a number of sites for a long time on shared servers at Bluehost: http://bit.ly/Hb5CAY and have never had a problem there with MODX.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html