WebsiteBaker Support (2.12.x) > General Help & Support

Media shows 403 Forbidden

(1/3) > >>

svsanchez:
Hi,

I upgraded to WB 2.12.2 r379 but the media option in the admin stopped working: when I go to media, I get a 403 Forbidden error.

I tried upgrading to WB 2.13.5 to see if this would fix it, but not only it didn't, it also destroyed my template.

So, I restored my WB 2.12.2 site and have been uploading images via FTP, and directly accessing their URLs to copy and place them where I need.

How do I fix this?

The site is: https://www.caletaazul.com/admin/media/index.php

hgs:
We need a little more information.
Which php version is used to run the website?
What did the “destruction” of the template look like?

Your link should redirect to the BackEnd login, but this does not happen.
You have placed a “protection” in front of the BE login, but if you only enter https://www.caletaazul.com/admin, the login window appears after a while

sternchen8875:
if you ask me..... it's possible that someone hacked your webspace or we didn't know all about the problem

- normally it's not possible to access the files and folders in the admin directory directly as there is a protection in each file and if the condition is not met you get a redirect to the login screen

- it also looks like something is going wrong in the admin folder, maybe a redirect or foreign code. the original file in admin/index.php has only 7 lines of code, nothing can be done for this long waiting time

- I can call the file admin/media/index.php directly in the browser, this is normally not possible. It shows me that - at least - this file no longer has the original code

again... if you ask me... immediately replace the following folders with the original files from your used WB-Version
- account
- admin
- DOCU (if you have - its not needed from the WB-system, but not good, if there some changed files inside)
- framework
- include
- install
- languages
- search

and check the other files and folders. the wb-own-files are from 2019. if you found files with a newer filedate, be carefull

P.S.: if you need the original files, i can send it via email.

sternchen8875:
i remember, that a lot of users working with different folder-protections for the admin-area / admin-directory, for example: .htaccess-protection, mod_rewrite or something like this. To locate your problem, deactivate this methods (if you use it) and work only with the original files

svsanchez:
Hi HGS, to answer your questions:

PHP: I upgraded to PHP 7.2 when I upgraded from WB 2.8.3 to WB 2.12.2 about 2 years ago. Then yesterday I changed it to PHP 8.1 to upgrade to WB 2.13.5. After I restored the site to WB 2.12.2 I changed to PHP 7.4 and left it there.

"Destruction of the site": After upgrading, the site appeared with a different template, similar to the old WB 2.8.3 template but with red and some dots instead of the blue, although the site's template was completely modified.

Login Protection: this is placed by my hosting company (20i).

Navigation

[0] Message Index

[#] Next page