Am I really the first to notice this? 
The funny thing is, it already didn’t work when I was there last time and that’s at least 3 years ago…
The marketplace was replaced last year. But yes, still questionable behaviour on filter/search.
Now it’s the third day that it is not reachable at all. It says “Request blocked.” - Is this due to my post??
Are you searching https://market.concretecms.com/ directly, or are you using the marketplace search from within a site dashboard?
If within a site dashboard, the search will only work for v9+. Dashboard marketplace search for v8 was discontinued when the v9 marketplace was released last May.
I’m using 9+ and I’m searching directly in the marketplace. Still blocked…
Try contacting Portland Labs to report the problem, use Contact Us :: Concrete CMS and the last option Everything Else.
Also tagging this for @Myq , but the above may be quicker.
@cgrauer your requests to https://market.concretecms.com/products?keywords= are blocked? Or some other URL?
exactly that URL is blocked
Are you on a corporate network, maybe with a firewall or something else that might be blocking that URL on your end? Antivirus software might even do that.
1 Like
Is there any other information? I see normal traffic going to that endpoint and nothing in our stack would return just “Request Blocked”. Can you provide a screenshot and possibly the details of the HTTP request (open your browser console to the network tab or use curl -Iv 'https://market.concretecms.com/products?keywords=' from the command line.
I reported a similar issue a few days ago: see https://forums.concretecms.org/t/cloudfront-is-blocking-market-concretecms-com/8759
I solved that error by cleaning all the coockies for the concretecms websites
Yep, that’s the problem I experienced too (and solved by deleting the cookies)
@mlocati excellent memory! As I recall, we could never figure out why the cookie triggered a WAF rule, but it looks like that might be happening again. @cgrauer could you try deleting the _pk_ref* cookie if you have it set and try again?
In order to automatically build the docker images for new ConcreteCMS versions, there’s a scheduled job running on GitHub that fetches a couple of pages from the concretecms.org website.
And 6 hours ago that job received a 403 error too - see Check last published version · concrete5-community/docker5@65cb7a2 · GitHub
Yes, deleting the _pk_ref… cookie solved the problem, thanks!
1 Like
@cgrauer thanks for confirming that. I think we have a handle on why that’s being blocked now and we’re taking steps to avoid that issue in the future.
@mlocati looking into it
1 Like
@mlocati as far as I can tell, the error you saw was unrelated and appears to have been transient. I haven’t been able to track down an exact cause, but it doesn’t look like it’s still happening. Let me know if you run into any further problems.