New F/S Thread Error

[loudbeard]

Getting a recurring error when creating a new thread in the For Sale section.

[Stoneman]

It appears you may be all set now?

[loudbeard]

I ended up posting through Tapatalk, couldn’t get it to work on mobile browser.

[ZX-12R]

I'm currently getting that identical error when replying to a post in the "Pressure Washer Surging" thread in the Off Topic forum. It started yesterday and was happening with multiple browsers including my phone (I don't use tapatalk.)

[Frankenstein]

I'm currently getting that identical error when replying to a post in the "Pressure Washer Surging" thread in the Off Topic forum. It started yesterday and was happening with multiple browsers including my phone (I don't use tapatalk.)

If you can remember exactly what you were attempting to post, can you see if you can post it in this thread?

[ZX-12R]

It's fighting me tooth and nail. I even tried logging out, clearing cookies, and all the fun stuff but it won't let me post. I tried PMing you my post and no such luck.

PM me an email address and I can send you what I was trying to post.

[Frankenstein]

It's fighting me tooth and nail. I even tried logging out, clearing cookies, and all the fun stuff but it won't let me post. I tried PMing you my post and no such luck.

PM me an email address and I can send you what I was trying to post.

Ok I was able to tie that to a specific mod_security rule that you were tripping. Please try posting here again.

[Frankenstein]

It was this text that was causing the issue:

(1700ish rpm vs 3400 on a direct drive gas)

The mod_security error was "PHP Injection Attack: High-Risk PHP Function Call Found". I'm not well versed enough in PHP to understand how that text was interpreted as a php command but I'm happy to call it a false positive and bypass the parent rule.

[ZX-12R]

My post just worked in the pressure washer thread.

After I would get the message loudbeard posted, I would start getting timeouts when connecting to the site on any computer going through my home network. My cell could get to the site (when on cellular) but it would still error out when I posted. I thought there was a partial issue on my end but couldn't find anything obvious. All other websites were working. I tried pinging the site's IP address from my office computer but got no response. I tried a website that can send pings and that worked properly. I tried sending pings from my router's command line and those were going unanswered. A minute or so after you asked me to try again, the pings started going through and I was able to post in the pressure washer thread. I'm wondering if the combination of issues tripped a temporary safety on Comcast's end or did the website ignore me for several minutes?

[ZX-12R]

It was this text that was causing the issue:
(1700ish rpm vs 3400 on a direct drive gas)

Funny enough, I tried stripping out all the links and even the QUOTE BBCode and it would still punt me out. I wouldn't have guessed that line would be the offender either.

[Frankenstein]

My post just worked in the pressure washer thread.

After I would get the message loudbeard posted, I would start getting timeouts when connecting to the site on any computer going through my home network. My cell could get to the site (when on cellular) but it would still error out when I posted. I thought there was a partial issue on my end but couldn't find anything obvious. All other websites were working. I tried pinging the site's IP address from my office computer but got no response. I tried a website that can send pings and that worked properly. I tried sending pings from my router's command line and those were going unanswered. A minute or so after you asked me to try again, the pings started going through and I was able to post in the pressure washer thread. I'm wondering if the combination of issues tripped a temporary safety on Comcast's end or did the website ignore me for several minutes?

Yeah your IP was getting temporarily blocked by the firewall for triggering that security rule. Shouldn't happen again.

[ZX-12R]

I was happy that I figured out the timing enough to get in here and post the issue. Thanks for digging into it so quickly.

[Frankenstein]

I was happy that I figured out the timing enough to get in here and post the issue. Thanks for digging into it so quickly.

Being able to look at the logs while someone is actively experiencing an issue is such a big help when troubleshooting, so thank you!