• Resolved chefchiller

    (@chefchiller)


    Hi,

    after updating to Woocommerce to 9.1.1 I get the message Woocommerce Databank needs update.

    Trying to update I get an error 403 no permission.

    I also get 403 errors at All produkts when I`m trying to Filter my products.

    Would be nice if anyone had an Idea.

Viewing 9 replies - 16 through 24 (of 24 total)
  • Hey, everyone!

    Sharing below a translated version of @chefchiller’s last reply:

    Strato seems to be moving, here is part of the last answer:

    Thank you for your inquiry and feedback.

    We would like to inform you that we have been aware of the error since the early hours of the morning. This error is due to a recent Apache update, as you have already correctly guessed.

    Our team is working hard on a solution to the problem so that your website will soon be working properly again

    I’m glad to know Strato is working on the issue and hope they can solve it quickly ??

    Since the issue is related to the host, and not Woo, I’ll close this thread now, okay?

    Please let us know if there’s anything else we can do to help or if you have any questions.

    Have a wonderful day!

    Wow, ich bin nicht allein ?? Auch mir hat Strato heute gesagt, dass sie nichts für den Fehler k?nnen und dass WordPress allgemein nicht ihre Sache ist. Hier mein Thread, es handelt sich bei mir um den Events Manager:

    Wow, I’m not alone ?? Strato also told me today that they can’t do anything for the mistake and that WordPress is generally not their thing. Here is my thread, it is the events manager plugin:

    https://www.ads-software.com/support/topic/error-forbidden-you-dont-have-permission-to-access-this-resource-2/page/2/#post-17893587

    • This reply was modified 4 months, 1 week ago by cede007.

    Hey, @cede007!

    Is it possible you contacted Strato before they changed their position on this? ??

    On other threads regarding this issue, some users confirmed the issue went away after trying a different host, so it really points to the issue being Stratos, as mentioned on the reply they gave @chefchiller.

    Please let us know if there’s anything else we can do to help or if you have any questions.

    Have a wonderful day!

    Yes, I spoke to Strato this morning. The hotline employee asked the technical team and replied that Strato had not changed anything on the servers. That’s not true. Now I have to wait until Strato fixes the error.

    Another user (joneiseman), just like me, tested a new WordPress installation with just one plugin (Events Manager). He is not with Strato and has had no problems. I’m with Strato and the fresh installation had the error. It was obvious that the error was to be found there. Thank you for your interest.

    Thread Starter chefchiller

    (@chefchiller)

    Freitag ist der Fehler bei mir das erstemal aufgetreten. Seit 3 Tagen war mir fast klar das es ein Strato Problem ist. Es war echt frustrierend wie der Support einen mit Phrasen abspeist die Schuld von sich weist. Und wie lange es dauert bis sie es selbst gemerkt und auch kommuniziert haben das der Fehler bei Strato liegt.

    Danke an alle Beteiligten hier im Forum für die Kommunikation und Unterstützung.

    @dennisbehrenscom

    @ubis3000

    @flosse52

    • This reply was modified 4 months, 1 week ago by chefchiller.

    Danke, @chefchiller für dein Engagement. Heute Vormittag noch wusste bei STRATO auch keiner von dem Fehler und die taten so, als w?re alles die Schuld von WordPress ?? Ich hoffe, dass der Events Manager dann auch wieder l?uft, sobald STRATO das repariert hat.

    Thread Starter chefchiller

    (@chefchiller)

    It’s not over till it’s over.

    It seems like the problem results of an Apache Security update :

    Orange Tsai discovered that the Apache HTTP Server mod_rewrite module
    incorrectly handled certain substitutions. A remote attacker could possibly
    use this issue to execute scripts in directories not directly reachable
    by any URL, or cause a denial of service. Some environments may require
    using the new UnsafeAllow3F flag to handle unsafe substitutions.
    (CVE-2024-38474,?CVE-2024-38475,?CVE-2024-39573)

    So maybe the WordPress developer Team should have an eye on that.

    I’m referring to this discussions in TYPO3 and Contao Community:

    https://forum.t3academy.de/d/507-neues-problem-bei-strato-create-content-element-forbidden-error-403/28

    https://community.contao.org/de/showthread.php?87114-Fehler-403-Forbidden-durch-Cookiebar-AH10508-Unsafe-URL-with-3f-URL-rewritten&p=586343

    • This reply was modified 4 months, 1 week ago by chefchiller.

    Hi all,

    Thanks for the extra info @chefchiller. This worked at my site, perhaps it will work for you as well?

    For all strato users:
    1. Login at strato
    2. Security -> Spam settings for guestbook
    3. Turn off all filters

    Once you have done this the issue is gone! At least at my site ??


    Strato appears to have fixed the error. At least in the Events Manager everything works as it should. Even without turning off the filters in the Strato account ??

    • This reply was modified 4 months, 1 week ago by cede007.
Viewing 9 replies - 16 through 24 (of 24 total)
  • You must be logged in to reply to this topic.