By Jeromy Waunch on Wednesday, 08 March 2017
Posted in General Issues
Likes 0
Views 372
Votes 0
While trying to add events in EasySocial, I am getting 403 Forbidden errors fairly regularly. Error message attached below. Thank you.
Hey Jeromy,

Actually different browser have their own different error shown up, you can check my attached screenshot below which shown the different message on Chrome browser, the reason why it shown this message is because your web servers rejecting the request so web browser unable to get the proper response from your server, so it render browser default message.

May i know is it possible temporary disable all those security rule from your server then try upload an event avatar and save it, see whether still hitting that issue?
·
Monday, 20 March 2017 12:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Also when I try to create an event on the back end, I'm regularly getting the message that the server unexpectedly dropped the connection. Image attached. Are the errors connected?
·
Wednesday, 08 March 2017 03:51
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Jerome,

I suspected that the error is caused by some restriction and permission issue, However I cannot replicate as per your screenshot. Where I got error:
Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; plgSystemkSecure has a deprecated constructor in /home/vinecomm/public_html/vine/plugins/system/ksecure/ksecure.php on line 12

https://www.screencast.com/t/1BPIZlZLM9M
https://www.screencast.com/t/EiG9zCsl7D52
Can you temporarily disable this plugin and see how it goes?
·
Wednesday, 08 March 2017 15:37
·
0 Likes
·
0 Votes
·
0 Comments
·
I disabled it, but it didn't seem to fix it. I also replaced with with jSecure Lite which is getting current updates. I also tried changing our site to PHP 5.3 (since I saw in their reviews that Kareebu secure had issues with php 7), but it also didn't fix things. We've had our site hacked in the past, so I'm not wanting to have our admin login page set as default. That said, I've uninstalled the plugin you asked me to disable, but it doesn't seem to solve the issue. Thanks
·
Thursday, 09 March 2017 03:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Jeromy,

Thanks for your cooperation, I'm now can create events in your site (front-end & back-end) seems like it is quite difficult to reproduce this issue as per your said it is fairly regularly happened
front end: https://www.screencast.com/t/hJ4H66fA
back end: https://www.screencast.com/t/0ltP3U5dpJr
I've make some changes for event file permission that might caused the issue happened, temporarily. Can you clear your browser cache perhaps it might be the cause as well.
If you encountered the issue again, can you give us some information on what browser you using, which event category that you selected so we can narrow down the possibilities happened, and maybe you can give us the steps to replicate it
·
Thursday, 09 March 2017 11:41
·
0 Likes
·
0 Votes
·
0 Comments
·
In the test events that you created, I am unable to add an event avatar without getting an error, both on the front end and the back end. I have tested it most recently using Mac Safari 10.0.3 and Google Chrome on Mac 56.0.2924.87 (64-bit). Screenshots of Safari & Chrome errors attached. Thank you!
·
Friday, 10 March 2017 03:33
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Jeremy,

I am sorry for the delay of this reply, we still investigate on this, because we noticed this only happen when you add avatar from backend event page, I will keep you update regarding this.
·
Friday, 10 March 2017 21:01
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Jeremy,

After troubleshoot this issue long hour ago, it seems like your server reject the POST request if included the image data.

Can you consult with your hosting provider regarding this see whether they have restrict some of the POST data unable to pass through your server?

Because the way you press save button from the edit event backend, it will actually send the POST data to your server to store it but for some reason your server reject that POST data, so it can't even response back to Joomla which I put the vardump code inside this file JoomlaFolder/administrator/index.php , by right if your server got response back the data into Joomla, it will reach this file first so I can see my vardump code from your server response.
·
Saturday, 11 March 2017 18:29
·
0 Likes
·
0 Votes
·
0 Comments
·
I will contact them and report back. Thank you.
·
Sunday, 12 March 2017 01:28
·
0 Likes
·
0 Votes
·
0 Comments
·
Alright Jeromy, keep us updated then.
·
Sunday, 12 March 2017 09:16
·
0 Likes
·
0 Votes
·
0 Comments
·
After emailing back and forth with Hostek, here is their response. (I haven't followed their recommendation, as I wanted to communicate with you first.)

_______________
Hello,

It looks like there is a file missing or corrupt in your easysocial plugin. Please try reinstalling your EasySocial plugin to see if this resolves the issue.

Sat Mar 11 17:49:57 2017] [error] [client 66.249.75.133] File does not exist: /home/vinecomm/public_html/vine/media/com_easysocial/scripts/site-2.0.10.min.js,
·
Sunday, 12 March 2017 09:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Jeromy,

I believe they are looking at errors that are outdated because your site runs on EasySocial 2.0.13 and not 2.0.10. The script error that they seen there is probably pointing out to the moment when you upgraded earlier and someone tried to access the site at the time of the upgrade.

But even if it still has errors, that missing js file would not cause such an issue. Forbidden errors are often caused by web servers rejecting the request.
·
Sunday, 12 March 2017 15:57
·
0 Likes
·
0 Votes
·
0 Comments
·
The forbidden error was a server security rule on their end that they have now whitelisted, so that particular error is solved. However, when adding an avatar logged into the back end, I am consistently getting an error. Screenshot of error message attached. Do you think that is also a server limitation?
·
Monday, 20 March 2017 10:36
·
0 Likes
·
0 Votes
·
0 Comments
·
You were correct Arlex. They had a software firewall setting that was causing the error. Everything is now working correctly.
·
Wednesday, 22 March 2017 01:36
·
0 Likes
·
0 Votes
·
0 Comments
·
You are most welcome Jeromy Waunch Glad to hear your issue has resolved.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.

Have a nice day ahead
·
Wednesday, 22 March 2017 10:24
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post