The good news is that for most, simply upgrading the connector (as outlined in those resources) will solve the "problems" introduced with those March 2020 cf updates. My other post elaborates on the issues, for those needing more.Īnd this problem will affect folks using cf for years to come (until Adobe creates a new installer for cf2018 that includes the then latest updates out it the box-and if they would do that for cf2016, whose updates end in 2021). Most important, that first post I offered tried to share the least one needed to know-but I could have made it still less verbose. These are reasons I wrote my posts, to help folks and try to explain it all. And even then, the discussion there is rather meager. But most folks don't read the update technotes. B ut as is explained in the technote bkbk pointed to (or elaborated in my blog posts), that update (and update 8 to cf2018, bit from March 2020) will cause this error FOR SECURITY REASONS (forced on us by Tomcat), until one also updates the wsconfig to match the security change implemented by the cf update. 403 All access is denied - Proxy server is blocking access to the target URL 403.1 Execute access denied - The virtual directories do not have Execute: Scripts Only permissions 403. You can use it to connect with your web server to access your WordPress files and folders.
If it’s an issue with a recent update to their server’s or their permissions, they’ll fix it for you. Your frustration is understandable and shared. Forbidden from accessing your own WordPress website. You will indeed get the same error, because the updates are indeed cumulative.