403 error

Posting this on behalf of another forum member.

He (or she, cannot confirm nor deny anything) has said that they were not able to post anything, nor PM anybody. Attached is a screenshot showing the error:

Anyone else finding the screenshot suspicious, or I'm I being overly paranoid (more than my normal level)?

pfsenseforum.png_thumb

doktornotor

Delete the forum.pfsense.org cookies. (I was never able to track why this BS happens, plus those links are absolutely useless and do not work and certainly do not fix anything.)

phil.davis

I got this a day or 2 ago from home. My IP is behind CGN, so "everyone" in my town with my ISP ends up with the same public IP. I guess somebody was doing something naughty from that public IP.
It was all fine when I got up the next morning.
Anything that tries to establish the reputation of a public IP address is going to have more and more problems (with IPv4) in futre - as there are often 1,000 random private users behind some ISP public IP. One of those users is naughty and all 1,000 get a bad reputation.

I pressed the "fix this problem yourself" button with no joy.

Sharing a public IP like that is idiotic, to say the least ;D

I understand the 1 IP per household, but "carrier grade NAT" shouldn't be implemented like that.

doktornotor

@phil.davis:

I got this a day or 2 ago from home. My IP is behind CGN, so "everyone" in my town with my ISP ends up with the same public IP. I guess somebody was doing something naughty from that public IP.

Certainly not behind CGN… (In fact, my public IP hasn't changed for years.) Getting this 2-3 times a month. NFC what's the "protection" supposed to prevent.

@phil.davis:

I pressed the "fix this problem yourself" button with no joy.

Yeah, no-op.

Mr. Jingles

@doktornotor:

Delete the forum

I just tried that.

( ;D ;D ;D ;D ;D )

Nooooo! think of the black hole!!! :o

Mr. Jingles

@phil.davis:

"everyone" in my town with my ISP ends up with the same public IP.

as there are often 1,000 random private users behind some ISP public IP.

:o :o :o

Does the person in IT, whomever invented this, still do barter trade (e.g.: exchange a bucket of milk for some bread), or does he actually use pieces of paper as a medium to exchange?

Electronic banking. 'sGonna be big in a century or three, mark my words. It's often a burden, being the visionair that I am :P

doktornotor

Also, this cannot be IP-based, could not be solved via clearing cookies.

@Mr.:

@doktornotor:

Delete the forum

I just tried that.

( ;D ;D ;D ;D ;D )

Mr. Jingles

@doktornotor:

NFC what's the "protection" supposed to prevent.

Your sentence reads a little bit weird to noobs like me:

Near Field Communication what's the "protection" supposed to prevent.

And yes I was baptized a good catholic. Why?

( ;D ;D ;D )

I think "Not F***ing Certain" is more appropriate :o

Mr. Jingles

@jflsakfja:

I think "Not F***ing Certain" is more appropriate :o

That's the problem with all these IT peoples: the minute you finally understand what they mean with an acronym, they change the game by replacing the words.

So do accountants, but instead of shortening words, they make them longer ;)

Mr. Jingles

When we released IFRS to the world, we made it clear, perfectly clear, that it stands for either:

International Financial Reporting Standards;

Incredibly Fine Rant System;

Improvable Functionally Retarded Setup;

'tIs the case of IT peoples: they never read manuals.

hda

@jflsakfja:

Posting this on behalf of another forum member.

Ah, when one connects tru Tor, such message too.

When that forum member can't login because he/she/it isn't sure that the forum hasn't been compromised on their end, in fear of losing the password, which could or could not be used elsewhere, and having to go through a password reset.

Or in general when others can't post, as in the error came up when they were trying to post.

Tor has (and always will) be operated by U.S. government subsidiaries. No need for yet another attack layer on my networks. I got enough headaches trying to keep up with letter-soup-agencies trying to actively break in.

cmb

If you get a 403, please take note of the "tech support code" it shows you, and you can PM it to me here, or email forum at pfsense.org.

Unless it's because you're coming in via a Tor exit node. We do not intentionally block Tor, however we block known actively malicious source IPs where significant abuse has recently occurred. Please submit the Tor exit node's IP to httpBL/Project Honeypot to get it whitelisted. Obtaining a new identity on Tor is commonly enough to re-gain access.

@doktornotor:

Delete the forum.pfsense.org cookies. (I was never able to track why this BS happens, plus those links are absolutely useless and do not work and certainly do not fix anything.)

I'm pretty sure what you're describing is something I killed off a few days ago after getting an email from someone who hit it with the "tech support code". that's this: https://redmine.ioerror.us/issues/72

the same thing still happens to some after it was "fixed". I disabled that check since it seems useless and problematic.

There were a couple other situations along the same lines that I just disabled a bit ago. That includes the one OP listed in this thread.

I also cleaned up the error page a bit in the source.

doktornotor

@cmb:

@doktornotor:

Delete the forum.pfsense.org cookies. (I was never able to track why this BS happens, plus those links are absolutely useless and do not work and certainly do not fix anything.)

I'm pretty sure what you're describing is something I killed off a few days ago after getting an email from someone who hit it with the "tech support code". that's this: https://redmine.ioerror.us/issues/72

Last time I was getting this about the exact time this thread was started. In fact, any time I got this, it was always solved by deleting cookies. The "fix this problem yourself" link is something that never produced any useful action solving the problem for me.

cmb

@doktornotor:

Last time I was getting this about the exact time this thread was started. In fact, any time I got this, it was always solved by deleting cookies.

I deleted the stupid rule in question in that badbehavior bug I linked about the time this thread started, so it most likely was that.

@doktornotor:

The "fix this problem yourself" link is something that never produced any useful action solving the problem for me.

I removed that link entirely because, yeah, it's useless.

kejianshi

So I don't have to periodically flush all pfsense.org related cookies and cache anymore? ;D