Tag Info

New answers tagged

1

You can just set it to localhost. Edit /etc/apache2/conf.d/httpd.conf: ServerName localhost The ServerName directive can be use in two contexts: server config or virtual host. In server config context, ServerName directive is used when creating redirection URLs. In virtual host context, ServerName directive is used to uniquely identify a virtual host. ...


0

These files are test scripts for your Apache installation in a Windows environment. Bear in mind that Apache may be installed on various platforms and the maintainers are likely to package test scripts for all platforms in the same bundle, it's not uncommon. I have never installed apache on Windows though and searching but Google Allmighty reveals these ...


3

(summary of comments) You have a conflicting SSL virtual host from the Ubuntu/Debian default-ssl virtual host. a2dissite default-ssl will fix the immediate problem. The Apache HTTP Server Wiki has a guide to configuring name-based SSL virtual hosts which you should review. The guide shows them all in one file, but you can split the different VirtualHost ...


0

You commented out the proxy listening on port 8080 in your above example. Is there a (reverse)proxy configured and still listening on the front end? In that case you should enable ssl on the front-end server and uncomment listening on 8080 as per your above example. If there is no front-end proxy listening yet/at all: Make sure to to have ssl.conf ...


0

What you're trying to do is potentially very dangerous from the point of view of security. You're trying to expose the system files through a webserver. Luckily Apache, like every other webserver, serves content in a chroot jail defined by the directive DocumentRoot, so that DocumentRoot /var/www/html would make Apache to serve content only in the path ...


0

My guess would be (although I've never done this before, I've always had the nfs mount up first) is that the running user didn't have access until it was reloaded - either it didn't know about it or something along those lines. Never tried this before though so I'm not really sure


0

The easiest approach would probably be to set up a second location block with the alternate authentication.


0

AFAIK, you need to use the same domain as the cert is registered with when accessing a site. So the IP address will always fail on the certificate check by the browser, since the IP is not part of the Certificate.


0

Look here: grep -nR -B9 mail_domain defaults.inc.php 440- 441-// This domain will be used to form e-mail addresses of new users 442-// Specify an array with 'host' => 'domain' values to support multiple hosts 443-// Supported replacement variables: 444-// %h - user's IMAP hostname 445-// %n - http hostname ...


1

The transport method of the connection between the client and this httpd instance is totally independent of the transport method between the httpd instance and the server you are proxying to. That means, just put the proxy lines (at least ProxyPass and ProxyPassReverse) to your HTTPS configuration: NameVirtualHost *:443 <VirtualHost *:443> ...


0

As of right now, CentOS 5.11 (Latest Stable) does not support TLSv1.1 or TLSv1.2. I am using a CentOS 5.11 dev machine with the following settings to mitigate any BEAST Attacks and such: [dev@host ~]# cat /etc/redhat-release CentOS release 5.11 (Final) [dev@host ~]# yum list installed | grep httpd httpd.x86_64 2.2.3-91.el5.centos ...


0

maybe password is being encrypted with some additional salt, I think you should change it through some configuration file, not sure though


0

The fail2ban package is designed to handle cases like this. You can control the time of the ban as well as generate notifications to your administrator.


0

I think your best bet is to make the apache document root a local directory on the same server that apache is running on. Then, if you must get content over a mount, use symlinks from within the doc root. The only way I have actually used this kind of setup is pulling static content from over the mount. If you are trying to reach across the mount, execute ...


1

This is a hard situation. The requests seem to match a malicious pattern, so your task is to block the IPs making malicious requests from your server. These days there are all kinds of fancy hardware to do this. If you can't get that then you are down to manually creating firewall rules or apache rules to ignore or block requests from certain IPs. For ...


0

Yes thats normal and does not have to do anything with OwnCloud itself but how you have configured apache. In the default installation you would use Apache MPM (Multi-Processing Module) Prefork. From the Apache Apache MPM prefork documentation: A single control process is responsible for launching child processes which listen for connections and serve ...


0

no listening sockets available, shutting down this errors show you to some of your app using the port 80 i have no idea how to check which app uses port 80 but u can change the localhost port from apache httpd.conf settting might be like this #Listen 12.34.56.78:80 Listen 80 you change the listen port like 8080 and start using from http://localhost:8080


0

there's no way to do it for non-EC DH.for ECDH:SSLOpenSSLConfCmd ECDHParameters prime256v1SSLOpenSSLConfCmd Curves secp521r1:secp384r1:prime256v1


0

Apache process started by the user www-data (in Ubuntu, check for Debian). Those files are created by ftp user. Owened by ftpadmin and have permissions read and write to owner only (group members and others cannot access). For currently uploaded files Add read and execute permissions to the other users sudo chmod o+rx *.php sudo chmod o+rx *.html (OR) ...


0

use .htaccess file. Add this line, replacing the files needed to be hidden: IndexIgnore file1.php file2.php Save, then restart/reload apache. Make sure AllowOverride is set to All inside /etc/apache2/sites-enabled/your-config-file in <Directory /var/www> section. Another method (still using .htaccess or config file) Add this: <files ...



Top 50 recent answers are included