OK, if you created the certicates using the IP, it should work.
As far as the colors of your files, usually green means it has the
executable
permissions on it. If you use the ls -al command. You will will proabbly
see
some "x"'s. html files don't usually have to be executable, only readable.
Even server side scripting usually doesn't need to be executable (PHP, JSP,
ASP, etc..)
But usually cgi-bin does need to be. Do man of chown and chgrp and see what
permissions
are the minimum you can get away with.
-rw-r--r-- 1 1134 1134 2318 May 1 05:31 index.html.ru.utf8
-rw-r--r-- 1 1134 1134 1700 May 1 05:31 index.html.se
-rwxr-xr-x 1 1134 1134 1062 May 1 05:31 index.html.zh.Big5
drwxr-xr-x 9 1134 1134 4096 May 15 11:46 manual
drwxr-sr-x 4 1000 1000 4096 Mar 7 12:28 phpSysInfo-1.2
In the examples above, the bottom 2 are directories, (they start with a "d"
flag).
They will usually show up as blue in Redhat by default.
The middle one is executable by everyone. It will usually show up as green
in Redhat.
The top two are just normal files that are read only by everyone except root
who can
read and write to that file. At the very least, I assume you will need the
file to
be readable by by Apache, which is usually run as a user (default is
"nobody").
If they are not readable, you will get the "Document contains no data"
error.
I usually do something like chmod 644 * to everything in my htdocs
directory.
However if you really need them to be executable (green) you can try doing a
chmod 755, but this is slightly less secure.
-----Original Message-----
From: Emma Wermstr�m (EMW) [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 01, 2001 3:08 AM
To: '[EMAIL PROTECTED]'
Subject: RE: cannot connect to remote secure server
Hi!
I created the certificate with the ip-adress, since this is a
"fictive" site that will not be displayed on the web. At least not for the
moment. This is why I use the ip-adress to access it from a remote machine.
I'd like to do a demonstration of the site.
I have another problem that sounds very stupid. I'm using redhat, which
means that all my "files" are displayed in green in a terminal window.
however, lately when transferring files to my redhat machine, these files
appear without any color at all (plain white). It's no big thing, since the
website works, but maybe these problems are interconnected somehow.
When I try to access the website remotely with Netscape, I get a message
saying that the documents contain no data.
Also, during redhat startup I get a message saying that the server name
"emma" , does not have an ip adress connected to it. I renamed
"localhost.localdomain" to "emma" for simplicity reasons in linuxconf.
Vivid imagination, I know...
I don't have any "non-secure parts" left on my server. I haven't defined any
virtual hosts. I only have one site on the server.
Thanks for any help.
Emma
-----Original Message-----
From: McCaffity, Ray [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 31, 2001 6:36 PM
To: '[EMAIL PROTECTED]'
Subject: RE: cannot connect to remote secure server
I think it's supposed to work this way.
When you created the certificate, did you create it
using the DNS name of your website or your IP?
-----Original Message-----
From: Emma Wermstr�m (EMW) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 31, 2001 9:35 AM
To: '[EMAIL PROTECTED]'
Subject: cannot connect to remote secure server
Hi!
RedHat Linux7.1
Apache1.3.19
Perl 5.005
mod_perl
embperl
mod_ssl and openssl (precompiled from RedHat)
I've tried to set up a secure server for my web site and I thought I had
succeeded. The entire site is "secure". I've made the server listen only on
port 443. Other than that I've basically not made any modifications from my
non-secure server (which obviously no longer exists).
However, when I try to access the server from a remote machine over the
intranet (using only https://ipadress), I can't connect any longer. With
httpd://ipadress it worked fine.
yes, my remote browser has SSL enabled. I'm not getting anywhere.
has anyone else experienced this?
Thanks,
Emma
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
