Stage site and images

Hi @saznajmo

Stage site created on subsite if you have “Prevent image hotlinking:” on please disable it on staging site WP security > File security > File protection tab – Prevent image hotlinking disable that fetuer and cross check,

It might be the staging site subdomain does not match htaccess rule for image prevent hotlinking for main domain that should be the case.

If you can not still see the image on subdomain staging site or prevent image hotlinking not enabled let me know that staging site url using https://pastebin.com/

508 error might be also due to a loop for the image to display So any .htaccess rule not making an issue that also needs to cross-check.

Pleaes take backup of .htacess and you may try to remove the code of .htaccess between the below two lines and it solves the issue. you may restore back remove lines and let me know.

“#BEGIN All In One WP Security”
“#END All In One WP Security”

Regards

• This reply was modified 8 months, 1 week ago by hjogiupdraftplus.

Hi,

Thank you for answer and help.

That’s right, when I erase the lines in between
“#BEGIN All In One WP Security”
“#END All In One WP Security” then the problem is fixed. Those lines are deleted when I deactivate the plugin. When I reactivate it they come back, but the pictures are still visible although new ones cannot be uploaded.

Now I tested when I unckeck any item within Filesystem security – File protection, first I tried Disable ability to edit PHP files: unckech, then the images appeared, but when I checked that option again I still had no problems and everything was fine . Then I realized that this is the case with all items within this tab.

Why is it so, that now it’s fine even though all options are checked in the Filesystem security – File protection tab?
What is the difference if it was fine on the live page and not on the subdomain?

Thank you again.

Hi @saznajmo

The difference is going to be the domain name of live and staging site.

The images are allowed access only for the domain name start which could be a problem for when you copy the live site and it has a live site domain not a subdomain using File protection > Image preventhotlinking.

Can you please share that live and staging site URL to check more using https://pastebin.com/ burn after read option?

Regards

Hi,

Ok, I’m just wondering how it’s fine now that at the end that option is enabled again?

Here is pastebin – https://pastebin.com/85F3BzY4

Hi @saznajmo,

The stage site URL domain image prevent hotlinking should match dev.opxxxxxxpt.com but it is copied from .htaccess live site URL have rule to start image URL with opxxxxxxpt.com which does not match so was an issue.

Once you remove the live domain rule from .htaccess and and update it changes to the subdomain url dev.opxxxxxxpt.com so it starts to work.

If you have the live site URL starting with www.www.opxxxxxxpt.com then it would not have been the problem (*).opxxxxxxpt.com rule has been added which will work for subdomain.

Regards

Hi,

Thanks for your help. Now I see that it is set differently in .htaccess (for the subdomain), although I did not change anything.
Earlier, when I disabled and enabled some of the options, images appeared. Does just saving the settings again automatically change the line in the .htaccess because I didn’t manually change anything?

Hi @saznajmo,

Yes saving any setting related to htaccess will rewrite the whole htacces rules, so it might have solved the issue.

Regards

Dear @hjogiupdraftplus,

Thank you for help and informations!

Hi @saznajmo,

I am resolving this topic, if you have any other questions / issues you may create another topic.

Would you mind writing a quick five-star review on www.ads-software.com?

https://www.ads-software.com/support/plugin/all-in-one-wp-security-and-firewall/reviews/#new-post

Reviews also help others to make confident decisions about our plugin.

Regards

Hi,

Yes I can, thank you.

I have one short additional question for this topic above, so I don’t know if a new ticket is needed?
I’m just wondering if it’s common with this problem (while it was different in the plugin and htaccess and while it’s a problem with images) when we try to load a new image, Error 508 appears, and I see that this error means Resource Limit is Reached.

Hi @saznajmo,

Error 508 means Resource Limit is Reached – Please contact your hosting provider.

It might be related to the physical memory, number of files limit or any other restriciton in purchased plan.

Regards

Hi,

yes, but that error didn’t occur on the page instead of the content. It appeared when trying to load images via the page builder after copying the page to the Stage page. Only on the page builder did the message Error 508 appear. But after your suggestions from earlier, now there are no such problems, that’s why I was wondering if it is related to these deviations (on htaccess and AIOWP security plugin)?

Hi,

The AIOS added htaccess rules applies F,NC,L flags means Forbidden generally it raises 403 errror not 508.

https://svn.apache.org/repos/asf/httpd/httpd/tags/2.3.6/docs/manual/rewrite/flags.html.en

Though you may ask the hosting proivder if any other reason can be it shows 508 error instead 403

Regards

Edit: please ignore the reply ??

• This reply was modified 2 months, 2 weeks ago by saznajmo.
• This reply was modified 2 months, 2 weeks ago by saznajmo.