permission issue with emoticons?
Standard member
Error
The page you are trying to access is restricted due to a security rule.
If you believe the security rule is affecting the normal operation of your website, contact your host support team and provide detailed instructions how to recreate this error.
They will be able to assist you with rectifying the problem and adjusting the security configuration if needed.
Emoticons seem to be working everywhere else (forums, etc), so this seems to be specific to galleries.
Any idea what is going on and/or how I can fix this?
Thanks in advance for your help!
Site director
Nobody here could really comment on it, you'd need to ask the webhost, provide them specifics including the URL you clicked from and that data/emoticons.php is the URL you clicked on.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Standard member
Chris Graham said
That sounds like a webhost's custom ModSecurity configuration.
Nobody here could really comment on it, you'd need to ask the webhost, provide them specifics including the URL you clicked from and that data/emoticons.php is the URL you clicked on.
From “Post #6,664”, 7th May 2020, 3:58 am
Sounds good. Thanks Chris.
I'll speak to my web hosting service provider tomorrow. Thanks for pointing me in the right direction.
Standard member
Okay, my ISP/web hosting provider is going to look into this for me. However, the second error problem that I am experiencing they said is probably on the part of the developer. Here is a screenshot of the error message I am getting (yeah, attachments worked this timecwdean said
Sounds good. Thanks Chris.Chris Graham said
That sounds like a webhost's custom ModSecurity configuration.
Nobody here could really comment on it, you'd need to ask the webhost, provide them specifics including the URL you clicked from and that data/emoticons.php is the URL you clicked on.
From “Post #6,664”, 7th May 2020, 3:58 am
I'll speak to my web hosting service provider tomorrow. Thanks for pointing me in the right direction.
From “Post #6,665”, 7th May 2020, 4:01 am
).
Basically, as I'm working on the site or using the site, I get this message about 3 to 4 times per hour. If I wait a minute I am able to refresh the page and everything is fine. However, I don't think my site users are going to be happy with this. It's extremely inconvenient.Any thoughts on how I can fix this?
Site director
However, it could also be ModSecurity. ModSecurity can be configured to give out '500' errors, or any other error status I think.
If it were an error from Composr, it would look as such.
Other possibilities include some kind of file permission problem, but that would be consistent rather than intermittent.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Standard member
Chris Graham said
You can see if anything is in the Composr error log, or the Apache error log.
However, it could also be ModSecurity. ModSecurity can be configured to give out '500' errors, or any other error status I think.
If it were an error from Composr, it would look as such.
Other possibilities include some kind of file permission problem, but that would be consistent rather than intermittent.
From “Post #6,671”, 7th May 2020, 6:39 pm
Okay, I'll see if I can check the logs but I'm not a web expert…so I'm not sure where those are located.
My web host provider (Siteground) has checked my account for security and has confirmed that everything looks good to them. They are going to look deeper into my emoticon issue, but everything else looks good to them.
Site director
But usually you can find an explicit icon for it in web hosting control panels.
Using some kind of file manager, it might be in a directory called 'logs' or something similar, usually one level up from the web directory.
It's a text file.
Composr's error log (which includes PHP errors) is under the Admin Zone > Audit menu. The file is data_custom/errorlog.php.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Standard member
Chris Graham said
Where the Apache error log is really depends on the system.
But usually you can find an explicit icon for it in web hosting control panels.
Using some kind of file manager, it might be in a directory called 'logs' or something similar, usually one level up from the web directory.
It's a text file.
Composr's error log (which includes PHP errors) is under the Admin Zone > Audit menu. The file is data_custom/errorlog.php.
From “Post #6,675”, 7th May 2020, 7:01 pm
Thanks for pointing out where I can find the log files. Much appreciated!
It turns out the problem was with process limits. Siteground has that set to 20 connections max…which should be more than plenty. However, IMAP connections that are configured for server notifications are known to sometimes hang and not free up its connection. After a while this can exhaust the 20 connection limit which will result in the occasional 500 ISR error.
Hopefully, after reconfiguring my IMAP email accounts, this problem will no longer occur.
That was an interesting lesson for me today
1 guest and 0 members have just viewed this.
