I'm getting "403 forbidden" errors when trying to run yum update using my local mrepo server. This is on an air-gapped network and yum.conf has no proxy information, so I don't believe there's a configuration setting blocking updates. When I browse to individual RPM URLs using a Web browser, I get 403 responses as well.
I verified that all RRMs are open to the world (777).
Thanks,
-Andrew Moon
Related
I'm trying to install whmcs on a hosting account from truehoster and I'm getting "HTTP Error 503. The service is unavailable.", at the beggining of the install process.
The error_log in public_html is empty.
How can I fix it?
It's most likely a ioncube issue, maybe cloudlinux?
Try to change the php version, if your host supports it.
make sure you have ioncube installed ..
check the permissions of the folder where you want to install whmcs
for the error logs you can see them at /usr/local/apache/logs/error_log
I have a 1GB ram Apache 2.4.10 (MPM event) VPS, my user complained that they always encounter broken webpage or image was loaded frquently, when I try to use fiddler to investigate, I found content length mismatch problem occurred in those broken image/pages. Seems that Apache sometimes did not sent the whole file to the client. I already disable HTTP/206 in Apache server but problem still persisted.
Any idea on it ? Or i need to install the newest version 2.4.16 ?
Thanks.
I think you need to check your apache services error logs file so that you can find out the exact root cause of this issues. Please check that and let us know what error are you getting in error logs file ? We will try to help you on this with the that error logs.
How to check whether my server is blocking the post request or not?
Currently in my wordpress, whenever I click update page there will be "The specified URL cannot be found" error. This is not permalink issue. The issue is with server configuration.
If you're getting the error message you say you're getting then POST is enabled and working. The problem is, like the message says, the URL.
Wordpress has this feature to enable "pretty URLs". It could be you've enabled it (or it may come enabled by default, I'm not sure) but don't have the required Apache module - mod_rewrite - enabled.
If you've got access to the command line of the server and your server is on Linux, simply issue:
// Enable mod_rewrite
> sudo a2enmod rewrite
// Restart Apache
> sudo service apache2 restart
If you would like some more help, please post the URL Wordpress is trying to reach and your Apache configuration to start with.
P.S.
If your server is on Windows, then enabling mod_rewrite depends on which software you've got installed.
When I open my website and any website pages, I get a "500 Internal Server Error". In the host, no .htaccess file exists.
The website works properly, but when I open any website pages, it's giving a 500 internal server error.
Please tell me what's the problem in the website.
Usually you can find more information on the kind of internal server error that happened in you webserver's error log file. (e.g. /var/log/httpd/error_log on many systems).
You may be work with a new version php in local server. But your hosted server may have older version php. Just upgrade your php version in cpanel
upgrade php version
Under Windows7 I am running CentOS-6.2-x86_64-server (on VM) having Apache2 with php5 and mysql installed. The vm is working fine, apache and mysql are started.
Now I want to access a webpage on the vm host being opened by a browser under Windows7.
I get following message:
"Forbidden. You don't have permission to access /index.html on this server."
My windows firewall is activated. Via Windows console I pinged the VM server successfully.
What am I doing wrong or what I have to do?
This is almost certainly an issue of either permissions for the path you're trying to access, or the mode in which you are running Apache. If, in your httpd.conf or ssl.conf files, you have a directive like SSLRequireSSL for this path, it will show a forbidden message when you attempt to access it via http rather than https.
Another reason this can happen is if you have http basic auth set up or some such, and cancel the login process.
Probably the most likely reason though, is simply having too strict permissions set on the folder or files that Apache is attempting to serve. If you go to the path where index.html lives, and make sure that both the directory and the files you want, are set to chmod 644 and make sure that you set things as being executable if there are scripts to be run, then you should be able to serve via apache as expected. You may also then need to chown apache.apache the files in question if they need to be writable by apache as well, but the former should get you going at least.
EDIT: Fixed a typo.