bcgurl wrote:

I dunno.. I just followed your way of switching the proxies and it just worked..

Oh good!

But I should say that most of the time, switching proxies is best done as a temporary solution. Since it worked for you, if you tell your ISP that we think their transparent proxy is interfering with your being able to use jdorama.com, that might be enough information for them to actually fix the problem.

In case you (or others) are unfamiliar with using proxy servers for browsing, here are a couple things to keep in mind:

many proxy servers listed in open proxy lists are not intentionally there for public use, they just happen to be accessible to the world and end up getting listed. So it's best not to overuse them or abuse them by downloading huge files with your browser while you are surfing with that proxy.

also open proxies come and go, which means that if some day the one you are using decides to close down, your browser will stop working (until you change your browser's proxy preferences again, of course).

There's a handy extension for firefox called "switchproxy" which allows you to easily switch proxies in and out, if you really want to get into it. It's pretty useful. It would make it easy, for instance, to use a proxy only when visiting jdorama.com.

Anyway, glad to hear you're up and running again.

*sigh*

That was me again with the proxy advice
-��

I just saw this error:

Could not query forum moderator information

DEBUG MODE

SQL Error : 1053 Server shutdown in progress

<snip>
Line : 200
File : viewforum.php

got a similar one, server had a hiccup me thinks

Has something similar while posting:

Quote:

Could not obtain post/user information DEBUG MODE SQL Error : 1053 Server shutdown in progress Line : 115 File : topic_review.php

Looks like the server crashed and they rebooted it.

Edited: deleted code.
_________________

In addition to seeing the SQL error, it might not be a good idea to display the SQL code, as it makes it easier for hackers to attempt SQL injection attacks, knowing the table and field names ...

Thanks for the warning. I didn't know that.

I've edited my message.
_________________

�� wrote:

In addition to seeing the SQL error, it might not be a good idea to display the SQL code, as it makes it easier for hackers to attempt SQL injection attacks, knowing the table and field names ...

There should be a way to inform the admin of the error without showing the error via a link or something. Did that make any sense?

Yes, it did. There's always PM, but when the forum is down the PM is too.
_________________

dochira wrote:

There should be a way to inform the admin of the error without showing the error via a link or something. Did that make any sense?

If it was my site, I'd turn off SQL code display (debug mode for phpBB?), and just display an error number that users could report. But I've never looked at the phpBB code to see what it can do.

It's probably a minor issue. although I've heard that phpBB has had security problems in the past, I didn't know if it is particularly prone to SQL injection attacks. Although a quick google indicates they exist.

So my comment is just that, in general, it's a security risk to display actual SQL code.

I'm unable to do anything when logged in, but if I delete my jdorama.com cookie, it looks like I can post here. It looks like it might be corrupted tables. I'll PM Genma with the error. If I can.
- ��

�� (not logged in) wrote:

I'm unable to do anything when logged in, but if I delete my jdorama.com cookie, it looks like I can post here. It looks like it might be corrupted tables. I'll PM Genma with the error. If I can. - ��

Swapped mysql servers, should be fine now.

It looks like our little spammer friend messed up the database, like you said a little more than 24 hours ago.

I tried the "find all post by..." and I keep getting this error:

Code:

Could not delete old search id sessions DEBUG MODE SQL Error : 1016 Can't open file: 'fxxxxx_search_xxxxxx' (errno: 145) ...

I'd post more, but I don't want to make it worst.
_________________

Anonymous wrote:

Swapped mysql servers, should be fine now.

Yes, thanks. I'm logged back in.

Anonymous wrote:

Swapped mysql servers, should be fine now.

It is. Thank you, whoever you are.
_________________

Now if we can just kill that damn spammer!
There's a special place in hell for his ilk.

You guys should really have some type of captcha for guest posting and registration.

That'd be great, but is it difficult to implement?
_________________

Captcha might slow down this spammer a little, but it might not stop him at all. I doubt his postings have been automated.

Maybe it would be better just to not allow guests to create new topics in this forum. Seems to me there are already plenty of appropriate topics people can post in to get help.

�� wrote:

Captcha might slow down this spammer a little, but it might not stop him at all. I doubt his postings have been automated. Maybe it would be better just to not allow guests to create new topics in this forum. Seems to me there are already plenty of appropriate topics people can post in to get help.

They are automated bots, they do that to a ton of other forums I've seen that allow guest posting and some bots even register and post, however e-mail validations and captchas can stop them.