8
I had exactly the same error today. I use 2.0.10 and Protector 2.4.
I had experienced a connection problem (figured my host was having issues). Next time I logged in (as admin) I got the error message. It is particularly disturbing as it displays the full server path on screen.
I have temporarily disabled protector using the 'Temporary Disabled' option' in prefs and everything now works again. I checked to see if my host had upgraded PHP or MySQL, but it appears not. I checked the files mentioned in the message for any stray hard-coded URLs that might have been added when I built the site locally, but there are none.
I have had no problems with it for a month so I don't know what triggered this.
@Gombunan
Did you use the prefs option to disable protector, or just disable the module?. It *might* require that you disable in prefs first (a database change) before disabling the module itself. Just a guess.
A thread is for life. Not just for Christmas.