403 when trying to save Styles.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Suiram
    Senior Member
    • Dec 2008
    • 216
    • 3.8.x

    403 when trying to save Styles.

    hi

    i recently wanted to make a very minor (one letter) change in the footer which is made via AdminCP > Maintenance > Update Counters > Rebuild Styles, and after hitting save, i get a 403 (forbidden) error. that tells me, a feature in vb is not allowed to run on my current hosting. fyi, the last time i did any changes via the styles setting was years ago, and the only underlying overall change since then is that i am now with a different host. i assume the new host might not allow some php(?) features. right? if so, how do i know which one/s to be able to talk to them about it. if it's not that, what could it be? it worked before. ps: i am running pure vanilla vb - not a single 3rd party add-on.

    thanks,
  • Mark.B
    vBulletin Support
    • Feb 2004
    • 24286
    • 6.0.X

    #2
    403 is a no permission error from the server. Probably being blocked by mod_security, or similar server security software.

    You'll need to speak to your host about this.
    MARK.B
    vBulletin Support
    ------------
    My Unofficial vBulletin 6.0.0 Demo: https://www.talknewsuk.com
    My Unofficial vBulletin Cloud Demo: https://www.adminammo.com

    Comment

    • Suiram
      Senior Member
      • Dec 2008
      • 216
      • 3.8.x

      #3
      Originally posted by Mark.B
      Probably being blocked by mod_security,
      ok, i'll go with that...

      Comment

      • Suiram
        Senior Member
        • Dec 2008
        • 216
        • 3.8.x

        #4
        it is fixed. it was ModSec rule 973321.

        Comment

        • Paul M
          Former Lead Developer
          vB.Com & vB.Org
          • Sep 2004
          • 9886

          #5
          973321 ?

          Thats a *lot* of rules .......
          Baby, I was born this way

          Comment

          widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
          Working...