Home › Forums › Calendar Products › Events Calendar PRO › 500 error
- This topic has 4 replies, 2 voices, and was last updated 11 years, 5 months ago by
George.
-
AuthorPosts
-
November 13, 2014 at 6:36 am #882021
justinbonnet
ParticipantHowdy! My website is broken at the moment – I can’t even log in to the dashboard.
This is the message displayed:
“Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at [email protected] to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Apache/2.4.9 (Unix) Server at http://www.healingforum.org Port 80”
I contacted my webhost, who in turn got some feedback from the tech support:
“The problem lies with the .htaccess file and the redirects you have added.
As you can see from the error logs –
healingforum.org [Sat Nov 08 19:25:51 2014] [error] [client 66.249.78.234:40020] AH01215: The Events Calendar Log: Initializing Tribe Events on Nov, 8th at 07:11:51 pm
healingforum.org [Sat Nov 08 19:26:17 2014] [error] [client 80.90.193.161:33457] AH01215: The Events Calendar Log: Initializing Tribe Events on Nov, 8th at 07:11:17 pm
[Sat Nov 08 19:26:18 2014] [alert] [client 80.90.193.161:34903] /home/sites/healingforum.org/public_html/.htaccess: RewriteCond: bad flag delimiters
[Sat Nov 08 19:27:18 2014] [alert] [client 10.0.44.92:52134] /home/sites/healingforum.org/public_html/.htaccess: RewriteCond: bad flag delimitersIf you can redo the Rewrite conditions you’ve added you’ll find you may still have an issue with the events calender log.”
And his advice is: “So my suggestion would be to disable the Events Calendar log, perhaps even uninstall it, and then try to install it again. You may also want to check out the .htaccess file”
Can you give me any support about what to do? I can access the file manager, do I just delete the plugin folder and reinstall? Is the eventsdirectory folder in public_html anything to do with the plugin too?
The .htaccess file has only this text in it:
”
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
Rewr# END WordRewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule># END WordPress
”Any help will be gratefully received π
(my level of technical competency is such that I can follow instructions if each step is obvious or explicitly explained)Many thanks in advance!
November 13, 2014 at 8:33 am #882332George
ParticipantHey Justinbonnet,
Thanks for sharing that information from your server administrator. The Tribe Events log items about the calendar initializing are actually okay β those are supposed to be there if you have the log enabled.
As for your .htaccess file, however, there seems to be some problems here. Did you copy and paste parts of it from somewhere else, or have the server administrator modify it at all?
For example, there are two separate modules within your .htaccess but one of them β the first one β is unclosed. That could cause problems.
For now, I’d recommend deleting the existing contents of your .htaccess file and replacing it with what’s recommended in this article on WordPress.org β http://codex.wordpress.org/htaccess.
Once you change that .htaccess file, let us know how things behave. We can go from there.
Thanks,
George
November 17, 2014 at 4:07 pm #888428George
ParticipantHey Justinbonnet,
Just wanted to check in on this ticket here. Itβs been a few days since it was last updated, but we did have a weekend between now and when this was last updated, so no worries.
Let us know if you get the chance to update your .htaccess file β if you do, I hope it helps!
Cheers,
George
November 18, 2014 at 9:08 am #889308justinbonnet
ParticipantThankyou, with your advice and that link it worked! I changed the .htaccess to this:
“RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]# add a trailing slash to /wp-admin
RewriteRule ^wp-admin$ wp-admin/ [R=301,L]RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ – [L]
RewriteRule ^(wp-(content|admin|includes).*) $1 [L]
RewriteRule ^(.*\.php)$ $1 [L]
RewriteRule . index.php [L]”Which is the model code for a subdomain example.
I or webmaster didn’t change it, but I did create a subdomain a while back (like, 6 months ago ish). I’ve no idea why a problem would flair up about it now!Thank you for your help π
November 18, 2014 at 11:18 am #889484George
ParticipantAwesome! Glad to hear that’s working now β we’ll be around if any other issues or questions pop up π
Cheers,
George -
AuthorPosts
- The topic ‘500 error’ is closed to new replies.
