I have a problem with my Wordpress site. When I try to edit old pages/post - I get "500 Internal Server Error". If I create a new page/post and edit it - it works fine.
I tried all the options I could find on Google:
Switched off all of the plugins.
Changed main Theme.
Created new clean .htaccess
Tried "debug mode' in Wp-Config
Checked all the rights to folders or files (all 755 or 644)
Increased memory in Wp-Confid to '64M' and '256M'
Contacted the host (they said we don't know, the problem is on your side)
Changed PHP to Apache from CGI(Apache).
Nothing helped.
What I get from Log:
[Tue Jun 27 02:02:37.218178 2017] [core:error] [pid 28851] [client 138.246.253.30:60354] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
[Tue Jun 27 02:02:37.309418 2017] [core:error] [pid 27769] [client 138.246.253.30:60356] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.'
What else can I try?
Related
When requesting via https it looks like serf is funnelling the request via port 80 instead of 443?
[Mon Jan 16 10:25:48.007386 2017] [error] [pid 350] [mod_pagespeed 1.11.33.4-0 #350] Serf status 120171(APR does not understand this error code) polling for 1 threaded fetches for 0.05 seconds
[Mon Jan 16 10:25:48.007539 2017] [error] [pid 350] [mod_pagespeed 1.11.33.4-0 #350] Serf status 120171(APR does not understand this error code) polling for 1 threaded fetches for 0.05 seconds
[Mon Jan 16 10:25:53.021234 2017] [warn] [pid 350] [mod_pagespeed 1.11.33.4-0 #350] Fetch timed out: https://www.domain.com/assets/76dc6ad2/style.min.css (connecting to:10.33.12.222:80) (1) waiting for 50 ms
SSL termination on the load balancer. SSL is also configured to work from behind the load balancer as well so https can be served from within the network.
ModPagespeedFetchHttps enable
ModPagespeedRespectXForwardedProto on
ModPagespeedEnableFilters prioritize_critical_css
How to have serf request https via port 443?
#dhaupin
I don't seem to notice that error anymore.
This is probably what fixed it, explicitly handling https requests.
ModPagespeedLoadFromFile "https://example.com" "/var/www/example/"
ModPagespeedRespectXForwardedProto on
I'm having Internal server error in some sessions(parts) after I login in wp dashboard.
Issues are in wp-admin/plugins.php and some few other places where is relating with any plugins.
I have checked .htaccess, memory limit to my server and in wp file is ok, I have deactivated all the plugins, changed themes, updated WordPress and still have the same issue.
I have check the error log and this is what it shows:
[Thu Jun 09 12:22:25 2016] [error] [client 217.73.141.38] Premature end of script headers: update-core.php, referer: http://www.salus.al/wp-admin/
[Thu Jun 09 12:22:29 2016] [warn] [client 217.73.141.38] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: http://www.salus.al/wp-admin/
[Thu Jun 09 12:22:29 2016] [error] [client 217.73.141.38] Premature end of script headers: plugins.php, referer: http://www.salus.al/wp-admin/
[Thu Jun 09 12:22:32 2016] [warn] [client 217.73.141.38] (104)Connection reset by peer: mod_fcgid: error reading data from FastCGI server, referer: http://www.salus.al/wp-admin/
Remove or rename your plugins folder and see if the problem goes away. If it does, then add each plugin one at a time to see which one produces the error. Perhaps clear all cache, cookies, etc as well.
I currently have a client that is using AEM 6.0. As they have some URL's that are lengthy they have been looking for a solution to shorten them without editing a virtual host file and adding redirects to the virtual host (they do not have the proper knowledge to do that). The only solution I found was to use vanity urls which per my research is supported in AEM 6.0 and as of Dispatcher 4.1.9.
Currently they have a dispatcher version 4.1.10 and I have gone through the AEM documentation https://docs.adobe.com/docs/en/dispatcher/disp-config.html#par_title_21 that discribes how to configure the Dispatcher and Publisher to enable access to vanity urls.
So far:
I have installed the VanityURLS-Components package on the Publisher.
I have added the following configuration to the dispatcher.any on the Dispatcher:
/vanity_urls {
/url "/libs/granite/dispatcher/content/vanityUrls.html"
/file "/tmp/vanity_urls"
/delay 300
}
and checked that the paths are correct.
I have created /tmp/vanity_urls file with ownership of apache:apache (this is on Centos) and permissions of 777.
And I have restarted apache.
Despite these steps it looks like I've overlooked something as /tmp/vanity_urls is not being updated. Maybe there is something I am not understanding here but I thought that the dispatcher updated every x seconds (here 300) /tmp/vanity_urls via the Publisher's /libs/granite/dispatcher/content/vanityUrls.html. Then used /tmp/vanity_urls as a whitelist of vanity urls that are allowed.
I am wondering why this is not working, any thoughts ?
Could it be a permission issue on /tmp/vanity_urls ?
Maybe there is something I erroneously assumed ?
Are there existing bugs out there I am unaware of that impact this dispatcher vanity urls feature ?
Any help is welcome ...
Best,
Nicola
UPDATE:
In my logs found the following:
[Thu Oct 08 16:11:03 2015] [D] [1780(140151407138784)] Vanity URL file (/tmp/vanity_urls) too old (1443478601 < 1444345863) on startup, fetching...
[Thu Oct 08 16:11:03 2015] [D] [1780(140151407138784)] Creating new socket: 127.0.0.1:8080
[Thu Oct 08 16:11:03 2015] [W] [1780(140151407138784)] Unable to connect to 127.0.0.1:8080: Connection refused
[Thu Oct 08 16:11:03 2015] [D] [1780(140151407138784)] incomplete request, no socket reuse
[Thu Oct 08 16:11:03 2015] [E] [1780(140151407138784)] Unable to fetch vanity URLs on farm website: no backend available.
[Thu Oct 08 16:11:03 2015] [D] [1780(140151407138784)] Loaded 0 vanity URLs from file /tmp/vanity_urls
Fairly self explanatory given that my publisher is not on localhost port 8080 ...
Hopefully that should fix my issue will update soon.
Thanks,
Nicola
I figured it out it was a network issue nothing to do with AEM,
/libs/granite/dispatcher/content/vanityUrls.htm was not accessible from my publisher.
I've installed mod_aspdotnet-2.2.0.2006.msi, and modified the httpd.conf to support dot net:
LoadModule aspdotnet_module "modules/mod_aspdotnet.so"
AddHandler asp.net asax ascx ashx asmx aspx axd config cs csproj licx rem resources resx soap vb vbproj vsdisco webinfo
<IfModule mod_aspdotnet.cpp>
AspNetMount /active "E:/TestWeb"
Alias /active "E:/TestWeb"
# Allow asp.net scripts to be executed in the active example
<Directory "E:/TestWeb">
Options FollowSymlinks ExecCGI
Order allow,deny
Allow from all
DirectoryIndex default.htm default.aspx index.html index.aspx
</Directory>
# For all virtual ASP.NET webs, we need the aspnet_client files
# to serve the client-side helper scripts.
AliasMatch /aspnet_client/system_web/(\d+)_(\d+)_(\d+)_(\d+)/(.*) "C:/Windows/Microsoft.NET/Framework/v$1.$2.$3/ASP.NETClientFiles/$4"
<Directory "C:/Windows/Microsoft.NET/Framework/v*/ASP.NETClientFiles">
Options FollowSymlinks
Order allow,deny
Allow from all
</Directory>
</IfModule>
It works fine when I launch normal HTML files(xxx.xxx.xxx.xxx:801/test.html), but when I launch any asp.net file(xxx.xxx.xxx.xxx:801/apps.aspx), there comes 500 error:
Internal Server
Error The server encountered an internal error or
misconfiguration and was unable to complete your request.
Please contact the server administrator, xxx#gmail.com and inform them
of the time the error occurred, and anything you might have done that
may have caused the error.
More information about this error may be available in the server error
log.
[Mon Aug 11 11:20:41 2014] [notice] Apache/2.2.25 (Win32) mod_aspdotnet/2.2 configured -- resuming normal operations
[Mon Aug 11 11:20:41 2014] [notice] Server built: Jul 10 2013 01:52:12
[Mon Aug 11 11:20:41 2014] [notice] Parent: Created child process 4952
httpd.exe: Could not reliably determine the server's fully qualified domain name, using xxx.xxx.xxx.xxx for ServerName
[Mon Aug 11 11:20:41 2014] [notice] mod_aspdotnet: CorBindToRuntimeEx has loaded version v2.0.50727 of the .NET CLR engine.
httpd.exe: Could not reliably determine the server's fully qualified domain name, using xxx.xxx.xxx.xxx for ServerName
[Mon Aug 11 11:20:42 2014] [notice] Child 4952: Child process is running
[Mon Aug 11 11:20:42 2014] [notice] Child 4952: Acquired the start mutex.
[Mon Aug 11 11:20:42 2014] [notice] Child 4952: Starting 64 worker threads.
[Mon Aug 11 11:20:43 2014] [notice] Child 4952: Starting thread to listen on port 801.
[Mon Aug 11 11:20:56 2014] [error] [client xxx.xxx.xxx.xxx] mod_aspdotnet: No AspNetMount URI for request: /Apps.aspx
This is the first time I use Apache to run my asp.net site. Maybe the error is stupid but please tell me.
I figured it out:
In my config, I used alias
Alias /active "E:/TestWeb". So I should input url http//172.0.0.1/active instead of http//172.0.0.1.
I attempted to install Gitolite on a Fedora 17 server with the aim of setting up git and HTTP access along with authorisation. Git access works OK. Can push and pull. But HTTP access falls over with an Error 500. It appears I got something wrong with permissions.
Here's what I did. I followed instructions from here: sitaramc.github.com
I have documented what I have tried to do here if anyone would like to see it down to detail.
HTTP Error:
Internal Server Error - 500
The server encountered an internal error or misconfiguration and was unable to complete your request.
More information about this error may be available in the server error log.
Error Log - /var/log/httpd/error-git.log
[Wed Feb 13 08:26:11 2013] [error] [client 192.168.0.40] suexec failure: could not open log file
[Wed Feb 13 08:26:11 2013] [error] [client 192.168.0.40] fopen: Permission denied
[Wed Feb 13 08:26:11 2013] [error] [client 192.168.0.40] Premature end of script headers: gitolite-suexec-wrapper.sh
[Wed Feb 13 08:30:13 2013] [error] [client 192.168.0.40] Directory index forbidden by Options directive: /var/www/git/
* Update 1 *
- Managed to post the error output here.
* Update 2 *
Relaxed permissions on log directory and gitolite-suexec-wrapper.sh. More details are available at the link above where I have documented in detail.
/var/log/httpd/error-git.log
[Wed Feb 13 21:18:47 2013] [error] [client 192.168.0.40] suexec policy violation: see suexec log for more details
[Wed Feb 13 21:18:47 2013] [error] [client 192.168.0.40] Premature end of script headers: gitolite-suexec-wrapper.sh
[Wed Feb 13 21:18:54 2013] [error] [client 192.168.0.40] Directory index forbidden by Options directive: /var/www/git/
$ sudo more /var/log/httpd/suexec.log
[2013-02-13 21:18:47]: uid: (990/git) gid: (988/git) cmd: gitolite-suexec-wrapper.sh
[2013-02-13 21:18:47]: cannot stat program: (gitolite-suexec-wrapper.sh)
Not sure where next
* Update 3 *
Ok, so I made some progress. I may have fixed the permissions issue. Now facing a PATH issue. Like before, most relevant output is included here. Full details are updated at the link in my original post.
My knowledge of Apache config is very basic. After reading about suEXEC, I realised the permission issue could be arising out of SELinux. So I disabled it for now. (Would like to identify a way of having gitolite working with SELinux active, but that's for later. Suggestions are welcome.)
Now when I access the url: http:// mochapenguin /git/testing.git in browser
001E# service=git-upload-pack
0000003BERR FATAL: unknown git/gitolite command: 'testing.git'
When I test from the client machine, I see:
ssh git#mochapenguin \echo $PATH
FATAL: unknown git/gitolite command: 'echo /usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/mochapenguin/.local/bin:/home/mochapenguin/bin'
* Update 4 *
Alright, got it working. No further change was needed since my last update.
I ought to have tried accessing the repo like so, instead of trying the URL in the browser:
git clone http://username:password#mochapenguin/git/testing.git
This setup allows clone and push over http
I can't figure out what I got wrong.
Could someone point me the right way, please?