I'm getting a HTTP/1.1 403 Forbidden error when trying to use chrome. Firefox works ok.
Do i need to clear my cache or something like that, or have i upset someone?
OP
UTC
Addicted
PK50XL, PK100S, ET3, Matchless G80S, Honda CBR400RR, Ducati ST4S
Joined: UTC
Posts: 721 Location: UK |
|
OP
Addicted
PK50XL, PK100S, ET3, Matchless G80S, Honda CBR400RR, Ducati ST4S
Joined: UTC
Posts: 721 Location: UK |
UTC
quote
I'm getting a HTTP/1.1 403 Forbidden error when trying to use chrome. Firefox works ok.
Do i need to clear my cache or something like that, or have i upset someone? |
|
UTC
quote
Matchlessman wrote: I'm getting a HTTP/1.1 403 Forbidden error when trying to use chrome. Firefox works ok. Do i need to clear my cache or something like that, or have i upset someone? ![]() |
OP
UTC
Addicted
PK50XL, PK100S, ET3, Matchless G80S, Honda CBR400RR, Ducati ST4S
Joined: UTC
Posts: 721 Location: UK |
|
OP
Addicted
PK50XL, PK100S, ET3, Matchless G80S, Honda CBR400RR, Ducati ST4S
Joined: UTC
Posts: 721 Location: UK |
|
UTC
quote
Matchlessman wrote: It'll be yellow boots next. |
Molto Verboso
![]() '99 PX200 & GTS300 HPE SuperSport
Joined: UTC
Posts: 1486 Location: Cheshire, England, UK. |
UTC
quote
Matchlessman wrote: I'm getting a HTTP/1.1 403 Forbidden error when trying to use chrome. Firefox works ok. Do i need to clear my cache or something like that, or have i upset someone? |
![]() UTC
Veni, Vidi, Posti
2007 LX150 2015 GTS 2017 BV 350
Joined: UTC
Posts: 12485 Location: Fond du Lac, Wisconsin |
|
Veni, Vidi, Posti
![]() 2007 LX150 2015 GTS 2017 BV 350
Joined: UTC
Posts: 12485 Location: Fond du Lac, Wisconsin |
Molto Verboso
![]() 2009 GTS250, Ducati Monster M900, KTM 390 Adventure, Honda CR125
Joined: UTC
Posts: 1821 Location: Oceanside, CA |
UTC
quote
I have also been 'dubbed thee unforbidden.'
It's only Chrome.. I sacrificed my soul and tried Edge and everything is fine.. safari on my phone is also fine. Or I wouldn't be posting this. |
|
UTC
quote
Same issue with Chrome here. Thought it might be my IP (I'm in Serbia, kinda dodgy) but no, seems to be a global problem.
|
|
UTC
quote
There are a variety of things that can trigger a 403 Forbidden error. Is there any other informative text below the 403?
How long has it been happening? What were you doing when it first happened? One potential reason for a 403 error is if a lot of requests are made in a very short amount of time -- the server is protecting itself against bots. Obviously, you all are not bots, but it is possible that Chrome is doing something that makes the server think it's a bot. |
|
UTC
quote
I'm using Chrome right now (on macOS) and not seeing any obvious problems. I'd really like to hear more about what specific activities are involved.
|
![]() UTC
Veni, Vidi, Posti
2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
|
Veni, Vidi, Posti
![]() 2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
UTC
quote
jess wrote: I'm using Chrome right now (on macOS) and not seeing any obvious problems. I'd really like to hear more about what specific activities are involved. I did nothing. Just got out of bed, picked up my laptop, walked to the cafe and tried to surf MV while drinking my liquid breakfast. No go. here's the details from brave request ------ Request URL: https://modernvespa.com/forum/new Request Method: GET Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8 Accept-Encoding: gzip, deflate, br Accept-Language: en-AU,en;q=0.9 Cache-Control: max-age=0 Connection: keep-alive Cookie: mv_token=XXXXXXXXXXXX (removed) Host: modernvespa.com sec-ch-ua: "Chromium";v="110", "Not A(Brand";v="24", "Brave";v="110" sec-ch-ua-mobile: ?0 sec-ch-ua-platform: "Windows" Sec-Fetch-Dest: document Sec-Fetch-Mode: navigate Sec-Fetch-Site: none Sec-Fetch-User: ?1 Sec-GPC: 1 Upgrade-Insecure-Requests: 1 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110 response ----- Status Code: 403 Forbidden Remote Address: 50.18.170.78:443 Referrer Policy: strict-origin-when-cross-origin Connection: Keep-Alive Content-Length: 132 Content-Type: text/html; charset=UTF-8 Date: Thu, 09 Mar 2023 08:04:31 GMT Keep-Alive: timeout=5, max=99 Referrer-Policy: strict-origin-when-cross-origin Server: Apache/2.4.54 () OpenSSL/1.0.2k-fips PHP/7.4.33 X-Frame-Options: SAMEORIGIN X-Powered-By: PHP/7.4.33 <html> <head> <title>403 Forbidden</title> </head> <body> <h1>HTTP/1.1 403 Forbidden</h1> <p></p> </body> </html>
Positive
|
|
UTC
quote
SteelBytes wrote: here's the details from brave The funny thing is that nothing on the server has actually changed for weeks. |
![]() UTC
Veni, Vidi, Posti
2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
|
Veni, Vidi, Posti
![]() 2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
UTC
quote
jess wrote: Thanks for that. It doesn't tell me a lot, but it does tell me that the error is being returned from the application layer (the forum software) rather than some lower-level server component. The funny thing is that nothing on the server has actually changed for weeks. ya know when you press F12 and get the debugging tab (forget the name) there is a button that lets you make it emulate different devices - eg pretend to be an iphone 12 or a pixel 5 etc. if I turn on that button and refresh it then works (turn off and refresh and it breaks again). So I looked at the headers during that and it doesn't include the "sec-ch-xxx" set of headers (the other Sec-Fetch and Sec-GPS are still there)
Positive
|
|
UTC
quote
Try regular chrome (with the default user agent) again and tell me if it works.
(I removed a ban on a specific agent that was triggered by an overlimit client) |
![]() UTC
Veni, Vidi, Posti
2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
|
Veni, Vidi, Posti
![]() 2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
UTC
quote
jess wrote: Try regular chrome (with the default user agent) again and tell me if it works. (I removed a ban on a specific agent that was triggered by an overlimit client) Anyone else wanna check with regular Chrome? |
|
UTC
quote
SteelBytes wrote: don't have regular chrome handy (bit lazy to install it just for this test). Anyone else wanna check with regular Chrome? |
![]() UTC
Veni, Vidi, Posti
2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
|
Veni, Vidi, Posti
![]() 2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
|
![]() UTC
Veni, Vidi, Posti
2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
|
Veni, Vidi, Posti
![]() 2019 GTS 300 HPE SuperTech 71,000km
Joined: UTC
Posts: 7147 Location: Batmania aka Melbourne, Aus |
UTC
quote
jess wrote: Does Brave use the standard Chrome user agent? SteelBytes wrote: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110 |
|
UTC
quote
SteelBytes wrote: it says Chrome in it so ... guess so? There is a subset of malicious bots that uses constantly-changing IP addresses to barrage the server with requests, but uses the same user agent for all the requests. The code in question was trying to catch that behavior, but snagged all Windows Chrome users (presumably using the latest version) in the process. I will have to rethink that aspect of session management. I've commented it out for now, so hopefully it won't snag any other innocent bystanders. Thanks much for the assist. |
|
![]() UTC
Innovator
76 Sprint V, 63 GL, 62 VBB, 05 Stella, 66 Smallstate, 66 Lammy S3
Joined: UTC
Posts: 11268 Location: Nashville 37 Days Since Last Explosion |
|
Innovator
![]() 76 Sprint V, 63 GL, 62 VBB, 05 Stella, 66 Smallstate, 66 Lammy S3
Joined: UTC
Posts: 11268 Location: Nashville 37 Days Since Last Explosion |
UTC
quote
jess wrote: It's not the word Chrome that triggers it, it's the exact user agent string. It looks like the output you pasted in doesn't include the tail end of the user agent string, but the rest of it matches the problem user agent that was put in the penalty box for being overlimit (i.e. too many requests in a short amount of time). There is a subset of malicious bots that uses constantly-changing IP addresses to barrage the server with requests, but uses the same user agent for all the requests. The code in question was trying to catch that behavior, but snagged all Windows Chrome users (presumably using the latest version) in the process. I will have to rethink that aspect of session management. I've commented it out for now, so hopefully it won't snag any other innocent bystanders. Thanks much for the assist. |
Molto Verboso
![]() 2009 GTS250, Ducati Monster M900, KTM 390 Adventure, Honda CR125
Joined: UTC
Posts: 1821 Location: Oceanside, CA |
UTC
quote
Also back up and running.
I know zero about code, so thank you to SteelBytes for saying all of those computer words to Jess. And thank you to Jess who, I think, took all of the computer words from SteelBytes and resolved it.
Positive
|
Atypical Canadian
![]() 2009 Vespa S50(LX150 motor swap), 2006 Vespa GTS250ie
Joined: UTC
Posts: 2319 Location: Toronto, Canada |
|
UTC
quote
chandlerman wrote: Are you using WAF or CloudFront to get the Shield Basic protections? Either of those would protect you, albeit at a (potentially-minimal) cost. The default edge security just provides basic packet hygiene, so protection for IP Stack level stuff like syn floods. We don't use CloudFront on the main server (modernvespa.com) at all. Nor WAF. The defense mechanisms we use predate both CloudFront and WAF (by a lot) and have largely grown organically with the site. I'm not sure converting to WAF at this point would be straightforward -- it would be hard to capture all the different rules that I've put into place over the last (checks watch) 17 years. I'll give it a closer look and see if it seems plausible, at least. |
|
UTC
quote
adri wrote: About 24 hours on access for me either. Pretty sure Jess just banned us for some fun lol |
![]() UTC
Innovator
76 Sprint V, 63 GL, 62 VBB, 05 Stella, 66 Smallstate, 66 Lammy S3
Joined: UTC
Posts: 11268 Location: Nashville 37 Days Since Last Explosion |
|
Innovator
![]() 76 Sprint V, 63 GL, 62 VBB, 05 Stella, 66 Smallstate, 66 Lammy S3
Joined: UTC
Posts: 11268 Location: Nashville 37 Days Since Last Explosion |
UTC
quote
jess wrote: We don't use CloudFront on the main server (modernvespa.com) at all. Nor WAF. The defense mechanisms we use predate both CloudFront and WAF (by a lot) and have largely grown organically with the site. I'm not sure converting to WAF at this point would be straightforward -- it would be hard to capture all the different rules that I've put into place over the last (checks watch) 17 years. I'll give it a closer look and see if it seems plausible, at least. And not that I'm totally shilling for AWS (but, full transparency, I *do* work there) the cost of WAF would probably be near zero unless MV does a lot more traffic than I think. |
|
UTC
quote
chandlerman wrote: That makes sense. Assuming the main server is sitting behind an ALB or ELB, it would be pretty simple to turn WAF on. chandlerman wrote: Unless the legacy protections are very site-specific, you'd probably find that those events Just Went Away with WAF turned on. chandlerman wrote: And not that I'm totally shilling for AWS (but, full transparency, I *do* work there) the cost of WAF would probably be near zero unless MV does a lot more traffic than I think. I don't think the cost would be zero -- a brief look at the pricing chart for US West (Northern California) puts the cost at $5 per month and $1 per rule. I suspect the number of rules I would need would be the kicker, as phpBB's very old design distributes entry points across about a hundred different PHP files, each with subtly different requirements. It's a mess, actually. I'm still reading the docs to get a better sense of what WAF can do. |
Modern Vespa is the premier site for modern Vespa and Piaggio scooters. Vespa GTS300, GTS250, GTV, GT200, LX150, LXS, ET4, ET2, MP3, Fuoco, Elettrica and more.