Server Error 403 Forbidden with Google

  • Resolved Jan Polet

    (@helpathand)


    1 year, 3 months ago

    When configuring WP Mail SMTP to use Google, I get a 403 Forbidden error right after allowing access to my Google account.

    The web application is working correctly.
    The publishing status is: “In production”.
    I am able to connect from another WordPress install without issues.

    I’ve also ruled out an error in .htaccess or other plugins causing the issue by disabling them. The error persisted.

    All WordPress folders have 755 permissions and all files have 644 permissions, so that should be correct as well.

    Somehow this error appeared after changing all of my passwords.
    Everything in my Google environment seems to be working correctly though.

    As a workaround I’ve now selected Other SMTP, so linking to the website in question probably doesn’t help.

    I have another WordPress install in the root of the same domain.
    The exact same error appears there as well.

    Any idea what’s going on and how I can make it work again?

    All help is appreciated.

    Thanks!

    • This topic was modified 1 year, 3 months ago by Jan Polet.
    • This topic was modified 1 year, 3 months ago by Jan Polet.
    • This topic was modified 1 year, 3 months ago by Jan Polet.
    • This topic was modified 1 year, 3 months ago by Jan Polet.
    • This topic was modified 1 year, 3 months ago by Jan Polet.

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Support Dake

    (@dakeg)

    1 year, 3 months ago

    Hi @helpathand ,

    Thanks for reaching out to us and we’re sorry to hear that you’re having an issue with setting up the Google mailer.

    I see that you’ve covered most of the usual troubleshooting steps we would recommend when this issue occurred previously.

    Just to confirm, you have already tried removing the connection and then reenabling it?

    Since you have already confirmed that this doesn’t affect other mailers, it’s possible that the password change really did play a role in the issue. In that case, we’d recommend re-performing the Google mailer setup steps outlined in our documentation.

    I hope this helps, if you have any other questions, feel free to let us know.

    Thread Starter Jan Polet

    (@helpathand)

    1 year, 2 months ago

    Hi @dakeg ,

    Thanks for your reply.

    I did remove and recreate the web application and started from scratch.
    I guess I forgot to mention that.

    I can’t figure out what changed, because it used to work and still is working from a test environment on my local network.

    I hope you can help figure out what’s going on.

    Jan

    • This reply was modified 1 year, 2 months ago by Jan Polet.
    Plugin Support Dake

    (@dakeg)

    1 year, 2 months ago

    Hi @helpathand

    Thank you for keeping me posted.

    This seems strange. May I have a list of the plugins you are currently using? Also, does the test environment have the same plugins/theme?

    Lastly, do you have a caching plugin enabled?

    We suggest that you try logging into your website in an incognito/private browsing window, then attempt the authorization again. Perhaps a fresh log in session to your Google account could make a difference.

    I hope this helps 🙂

    Thread Starter Jan Polet

    (@helpathand)

    1 year, 2 months ago

    Hi @dakeg ,

    Thanks for your reply.

    There are two WordPress installs that are having this issue.

    They both have different themes and plugins installed.

    https://www.helpathand.nl/ is currently showing very little information on just a few pages.

    Installed plugins:

    • Really Simple SSL
    • Twentig
    • UpdraftPlus – Backup/Restore
    • Wordfence Security
    • WP Mail SMTP
    • WP Meta and Date Remover
    • WPForms Lite

    https://www.helpathand.nl/janpolet/ has more of everything.

    Installed plugins:

    • Better Search Replace
    • Enable Media Replace
    • Kadence Blocks – Gutenberg Blocks for Page Builder Features
    • MetaSlider
    • PDF Embedder
    • Really Simple SSL
    • Simple File List
    • TablePress (with 8 extensions)
    • UpdraftPlus – Backup/Restore
    • Virtue/Ascend/Pinnacle Toolkit
    • Wordfence Security
    • WP Mail SMTP
    • WPForms Lite
    • Yoast SEO

    My test environment has many of the same plugins.

    Like I stated earlier I’ve ruled out the plugins causing the issue by disabling them. The error persisted.

    I am not using a caching plugin.

    My main browser is Firefox, but I’ve already tried logging into the website using Chrome and Edge. The results were the same.

    I just used a private window in Firefox.
    Selecting Google as mailer resulted in the same 403 error.

    Anything else I can try?

    Best Regards,

    Jan Polet

    • This reply was modified 1 year, 2 months ago by Jan Polet.
    • This reply was modified 1 year, 2 months ago by Jan Polet.
    • This reply was modified 1 year, 2 months ago by Jan Polet.
    • This reply was modified 1 year, 2 months ago by Jan Polet.
    Plugin Support Dake

    (@dakeg)

    1 year, 2 months ago

    Hi @helpathand

    Thank you once more for keeping us posted.

    Have you already tried using a different Google account on the website with the issue? I imagine you’ve tested this before, but we just want to rule this out as a possibility.

    Thread Starter Jan Polet

    (@helpathand)

    1 year, 2 months ago

    Hi @dakeg ,

    I have not tried another Google account.

    I’ve only tried my main account, which is part of Google Workspace.

    There is one other thing that might have something to do with this.

    Both the domains helpathand.nl and janpolet.nl used to have there own hosting plan.
    Recently, to cut back on hosting fees, I transferred janpolet.nl to helpathand.nl/janpolet.
    The domain janpolet.nl now only has DNS hosting to keep Google Workspace working. All other traffic is redirected to helpathand.nl/janpolet.

    Could that have something to do with it?

    Best Regards,

    Jan Polet

    Plugin Support Dake

    (@dakeg)

    1 year, 2 months ago

    Hi @helpathand

    We’d like to confirm if you are getting a 403 forbidden error on the Google Authentication page or on your website. May we have a screenshot for reference? Ideally, one showing the URL.

    If it is on your server then it can be that mod_security is throwing this error. Another troubleshooting step you can attempt is to disable all server security modules temporarily (you may need to reach out to your website host about this) and try to perform authorization.

    I hope this helps 🙂

    Thread Starter Jan Polet

    (@helpathand)

    1 year, 2 months ago

    Hi @dakeg ,

    Here is a screenshot of the error message:

    Hope this helps.

    I just tried using a different Google account.
    After creating the web application and using the credentials I got the same 403 error. 🙁

    I don’t get what’s wrong.
    This used to work.

    Best Regards,

    Jan Polet

    • This reply was modified 1 year, 2 months ago by Jan Polet.
    • This reply was modified 1 year, 2 months ago by Jan Polet.
    Plugin Support Dake

    (@dakeg)

    1 year, 2 months ago

    Hi @helpathand

    Thank you for sharing a screenshot of the 403 error.

    Just to confirm have you already reached out to your website host about this issue? This screenshot implies that the last troubleshooting step I provided may resolve it.

    If it is on your server then it can be that mod_security is throwing this error. Another troubleshooting step you can attempt is to disable all server security modules temporarily (you may need to reach out to your website host about this) and try to perform authorization.

    Thread Starter Jan Polet

    (@helpathand)

    1 year, 2 months ago

    Hi @dakeg ,

    Thanks again.

    I’ve contacted my hosting provider and will report back.

    Best Regards,

    Jan Polet

    Plugin Support Dake

    (@dakeg)

    1 year, 2 months ago

    Hi @helpathand

    You’re welcome, I’ll keep an eye out for your next response.

    Thread Starter Jan Polet

    (@helpathand)

    1 year, 2 months ago

    Hi @dakeg ,

    It took some time but it’s finally working.

    ModSec is now disabled on the server.

    They first tried disabling ID 334000, but that didn’t work.

    Are there specific ID’s that should be disabled to make it work, or is disabling ModSec all together the better option?

    Looking forward to your reply.

    Best Regards,

    Jan Polet

    Plugin Support Dake

    (@dakeg)

    1 year, 2 months ago

    Hi @helpathand

    We’re glad to hear that you were able to authorise successfully.

    Now that you have done so, you are free to reenable ModSec. Disabling it was only necessary since it was preventing you from authorising in the first place.

    Thread Starter Jan Polet

    (@helpathand)

    1 year, 2 months ago

    Hi @dakeg ,

    I’ve enabled ModSecurity again.
    Turns out I was able to do that myself in Plesk.

    Thanks for your help!

    Best Regards,

    Jan Polet

    Plugin Support Dake

    (@dakeg)

    1 year, 2 months ago

    Hi @helpathand

    You’re welcome, happy to help!

    Have a good one 🙂

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Server Error 403 Forbidden with Google’ is closed to new replies.