Apache :: HTTPS - Generate Certificate And SSL Module
May 26, 2013
How to be able to fix my problem that is related to the https using apache2 (enabling https in apache2) at opensuse:
By the way, my opensuse version is:
openSUSE 12.1 (x86_64)
VERSION = 12.1
CODENAME = Asparagus
1) At the /etc/apache2/vhosts.d/vhost-ssl.conf, and if I do not have a name (as the server will be accessed using its IP address), can I place in the ServerName 192.168.0.5? Do I have to place it 192.168.0.5:443 or it is enough to be 192.168.0.5?
2) Is there a relation between the SSLCipherSuite values and the used method to generate the certificate?
3) I am afraid from the way that I am using to generate the certificate and the ssl module that is coming with apache2 at my machine which has opensuse. How can I select the right way?
Actually I used following commands to generate the .crt, .key and the .csr:
4) Do I have to configure the virualhost? Do I have to create files under the directory /etc/apache2/vhosts.d? Because I will have one application to be browsed .. nothing more.
After successfully installing postfix+dovecot on Debian, I've run into a problem using Thunderbird email client on my home pc to receive email. I get: "Security Error: Domain Name Mismatch"
How, then, do to I generate a certificate for mail.mydomain.com?
Before installing postfix+dovecot, I created an MX record for mail.mydomain.com, and an A record for mail.mydomain.com. Should I have also added mail.mydomain.com to /etc/hosts?
When setting up Thunderbird, I told it my Pop Server was mail.mydomain.com. When I attempted to Get Mail, then I got "Security Error: Domain Name Mismatch".
i've installed this shared SSL certificate on my server for a domain. now the weird thing is when i go to [url]it redirects to the site which owns the SSL certificate.
any idea how to either disable https access for everything else, or just now have it redirect to that site?
I have set up an Apache web server that has ssl enabled. If I go to https://myserver.com I get the 'it works!' page and the certificate is valid and trusted. If I go to https://myserver.com/myapp that also works (it's an Oracle weblogic deployed java app that I'm fronting with Apache).
I would like to configure Apache so that when a user goes to simply https://myserver.com it automatically directs them to https://myserver.com/myapp rather than showing the 'It works!' page. I have read some documentation and experimented with setting a redirect via the https.conf file and even the ssl.conf file but nothing seems to work. I either get a 404 or simply the 'It works! page.
I would like to know is there any module for Apache which can collect information like who is surfing our website and how many pages they have accessed in last one hour. I know awstats or webalizer can do this but i need some thing realtime on apache level.
I found a script that updated php to 5.5, however it's only enabling me to run it as a CGI script, if I want to run PHP an Apache module, it's still only 5.3. How can I upgrade the Apache version?
I have a server running Apache 2 with PHP as an Apache module. There are a few php scripts that use lots of cpu when they run and have lots of hits, but Apache is still running fine and pages and php scripts load pretty fast. I was just wondering if running PHP as fastcgi would use less cpu or make php scripts load faster.
I keep hearing that redirecting from http to https is not very secure [non-SSL to SSL]. Among other reasons, one reason is that the browser may continue to think it is communicating with non secure server and may not encrypt the data. Is it true? I hope not, I am using the following -
I have a problem with slow Apache 2.4.4. It's only related with https which is in general 5 time slower than the same site via http. I see this difference on the monitoring software which is measuring response time to http and https every 5 seconds. In some cases i got even timeouts in the browser on https while in the same time site is opening over http - slowly but opens always.
Apache runs on Win2k8 Enterprise, Version 2.4.4 x64 - VC10. Server is connected with quite poor internet connection as it's located in Africa. Despite of connection quality http is working properly all the time.
I've just joined the group and new to Apache/php. I have just assembled a website in Joomla/vertumart and called petslovezone.com.au. I want to redirect all the request such as
1. http://xyz.com to https://xyz.com 2. http://www.xyz.com to https://xyz.com 3. xyz.com. to https://xyz.com 4. www.xyz.com to https://xyz.com
now know I have to change .htaccess "RewriteEngine On" section. What would be the best code to do all the above.
I am trying to find out if redirecting an https URL to an http URL will still provide the security of the original https? Should the page information for the redirected http page show it as being unencrypted or shouldn't it have the same encryption as the original https?
I´ve read that a whole https website might be better for SEO than just a mixed version. So I want to change the whole website to https.
We are using Plesk 12 on Win 2008 R2. One Website is using DotNetNuke 7.3.2.
How can I automatically set the whole website to https?
What happens to the users that just type domainname.com without http or https.?
What is the right search engine friendly technique to permanently redirect to the https version even when the user is not using the application protocol prefix http/https?
Where can I do the setup in Plesk 12 fro Windows?
Are their any other drawbacks that I have to think over before I do the changes?
i have a dedicated server that i use for stream flv files. In this server i have apache.
Do you know any apache solution for prevent streaming of flv files to others domain name ? I want to stop leeching and permit stream of files only for my domain name. The htaccess solution in my case don't works...
I have recently installed the latest version of apache which is version 2.2.4 and it seems many modules were left out so I decided to add one of my favorite modules myself
I have DirectAdmin install so here is what I did
I edited this file: configure.apache_2 and at the end of the file added --enable-expires
After adding normally we would recompile apache I was doing that and I got this error
Code: /usr/local/directadmin/customapache/configure.apache_2: line 24: --enable-expires: command not found
*** There was an error while trying to configure Apache 2. Check the configure.apache_2 file
Not sure what I'm doing wrong if someone could help me I would be greatful.
If a User logs in with username only, all works correct. If a user use the DomainUsername format, the login is rejected with "user not found".Should it not work with both login styles ? Or is there a option to reformat or rewrite the username before authentication without the "Domain part ?
- Plesk 12 (v12.0.18 Update #40) and - Linux CentOS 6.6 (v2.6.32-504.12.2.el6.x86_64) to another VPS with: - Plesk 12 (v12.0.18_build1200140606.15) and - Linux CentOS 6.6 (v2.6.32-504.12.2.el6.x86_64)
I tried to do the following:
- Tools & Settings / Tools & Resources / Migration & Transfer Manager / Start New Migration - Data source: Transfer data from another server - Transfer the following data / Migrate the whole server
Following error/warrning message is recieved then:The following Apache modules are disabled on the destination server: sysenv. Please enable these modules to prevent possible problems.
I have replaced the real paths with "PATH" for security reasons. How to reduce the time to first byte in general. I tried setting up memcache to accomplish this but I didn't notice any changes...
I have a custom software that runs it's own webserver. I then found instructions on how to use apache2 as a proxy that will enable ssl for that site. (long story short, my custom software doesn't support ssl and it's not an option)
I recently got a SSL-certificate for my website. Now the old links to my website (using only http) doesnt work, the visitors just getting redirected to my index page. How can I change my .htaccess so both http and https works, but keep https as the preferred? Or even better, redirect old http links to https? I'm not using www.
My current .htaccess: RewriteCond %{HTTPS} off RewriteRule (.*) https ://%{HTTP_HOST}%{REQUEST_URI}
i want to redirect main domain http //, www request to https://
i added this code
RewriteCond %{HTTPS} off# First rewrite to HTTPS:# Don't put www. here. If it is already there it will be included, if not# the subsequent rule will catch it.RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]# Now, rewrite any request to the wrong domain to use www.RewriteCond %{HTTP_HOST} !^www.RewriteRule ^(.*)$ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
