At 10:26 AM 2/18/2004, Stephen wrote:
Lolke Bijlsma wrote:
I'm running unstable and I'm trying to get server side includes to work
with apache. I remove apache and apache-common and then installed it
again. So I have the latest httpd.conf.
SSI isn't on by default Lolke.
I see it has all the rig
Lolke Bijlsma wrote:
Hi,
I'm running unstable and I'm trying to get server side includes to work
with apache. I remove apache and apache-common and then installed it
again. So I have the latest httpd.conf. I see it has all the right stuff
for server side includes in there as long as mod_includ
Hi,
I'm running unstable and I'm trying to get server side includes to work
with apache. I remove apache and apache-common and then installed it
again. So I have the latest httpd.conf. I see it has all the right stuff
for server side includes in there as long as mod_include is loaded. So I
ran
"Jan Gehring" <[EMAIL PROTECTED]> writes:
> i have a problem with virtualhosts and the apache server.
>
> my debian is: 2.2r0
>
> the problem is:
> i can only put 2 virtualhost in the configuration file (httpd.conf) because
> with more virtualhosts the apacheserver did not start !
It does work
Hello list !
i have a problem with virtualhosts and the apache server.
my debian is: 2.2r0
the problem is:
i can only put 2 virtualhost in the configuration file (httpd.conf) because
with more virtualhosts the apacheserver did not start !
thanks for all your help
and please forgive my bad engli
If order to get the apache to find your index.html file in /var/www, you
have to set DocumentRoot to /var/www
Go to /etc/apache and edit httpd.conf file. You need to set DocumentRoot
to directory where you want to serve hte default pages from.
Andrei
---
I looked at the bugs on www.debian.org and didn't see mine described, so
I thought I bounce it off of this group.
I installed potato. That was my first mistake. I haven't been able to
get samba working nor will apache work. Nothing seems wrong with the
install, but I can't get pages to display
I have successfully setup apache, but even though apache-ssl has been
configure very similar I still can't get to it from a browser (on port 443).
After looking at errors.log, it seems that it is seeing the request but
denying access. Here is an excerpt from the log file:
[error] SSL_accept faile
When using dhcp, since the hostname doesn't resolve to an IP address right
away, there are a few packages that barf, like apache and samba.
These appear to attempt to find the IP address from the system name. In
the case of dhcp, this may not be known. You can't hardcode an address in
the /etc/h
I've installed the package apache-ssl from hamm/non-US
distribution.
The installation didn't cause any problems, but when I tried
to connect to my server:
lynx localhost:443
I received the error:
Alert!: Unexpected network read error; connection aborted.
And then:
Alert!: Unable to access documen
[EMAIL PROTECTED] wrote:
>Number 2
>postgesql 6.3-2
>Dpkg could not config postgresql due to problems in initdb. I tried to run
>initdb manually as user postgres from the postgres home dir /var/lib/postgre
>s
>but this didn´t work because initdb could not find other programs
-BEGIN PGP SIGNED MESSAGE-
Hi!
Yesterday i upgraded some packages to Hamm frozen and has two problems. I don´t
know if that where bugs or just my faults.
Anyway, i solved them and maybe this information can help others.
OK, here it goes:
Number 1
Apache 1.3b5-2
I had to uncomment
The pre-install script in that package is failing - it says returning
status 1, and it should return 0. You can use "dpkg" to extract the package
archive, and then try to run DEBIAN/preinst by hand. That should let you
figure out what is wrong with the script. Sometimes it is something simple
like
Hello,
I've been having problem with Apache 1.1.3-6 as supplied with Debian 1.3.1.
Basically
I've been using DSELECT, but reverted to DPKG in an effort to get more info
on the problem. Alas, even the highest level of --debug failed to provide
me with enough.
A brief history:
Apache 1.1.3-6 ins
14 matches
Mail list logo