I have followed the tutorial, but i can’t make it work. After finishing all steps, both lynx from the local machine and other pcs in my network can’t access to the svn folder. Access to the apache root folder works fine. I’m using a Ubuntu 8.04 Server Edition (64 bit).

If anybody knows what is the problem, that would help me a lot. Thanks in advance!

I fixed the problem, I had to move the

DAV svn
SVNParentPath /var/svn
AuthType Basic
AuthName “Subversion Repository”
AuthUserFile /etc/apache2/dav_svn.passwd
Require valid-user
SSLRequireSSL

from dav_svn.conf to /etc/apache2/sites-available/servername

And insert the data in between the

// right here

PC 1- SVN server Apache (SSL enabled)
PC 2- APache (reverse proxy proxypass) connects to PC1 via SSl
when svn list https://PC1/svn/REPOSITORY is issued

In PC-2
in config file /etc/apache2/sites-available/myconfig (included via a2ensite command)
ProxyPassReverse /svn/REPOSITORY/ https://PC1/svn/REPOSITORY/
ProxyPass svn/REPOSITORY/ https://PC1/svn/REPOSITORY/

Order Deny,Allow
Allow from all
Satisfy Any

svn list https://pc2/pc1/

(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down

We got apache running yesterday with SSL and a colleague of mine installed Samba , and this morning i whent ahead and create the svn repositories and when restarting apache it gives the socket error.

Any one that can give me maybe a hint?
Thanks in advance

1. adding the “Listen 443″ port to ports.conf caused the apache server restart to fail with this error:

98): make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs

Removing the extra Listen 443 statement from the ports.conf file fixed this.

2. Somehow my first attempt at generating the SSL cert failed, causing this error in the log file upon restart:

[error] Init: Unable to read server certificate from file /etc/apache2/ssl/apache.pem
[error] SSL Library Error: 218529960 error:0D0680A8:asn1 encoding routines:ASN1_CHECK_TLEN:wrong tag
[error] SSL Library Error: 218595386 error:0D07803A:asn1 encoding routines:ASN1_ITEM_EX_D2I:nested asn1 error

The server _appeared_ to start (no errors/warnings on the console) but trying to hit it from the browser or lynx showed that it was not in fact running.

Fix was to delete the cert file (/etc/apache2/ssl/apache.pem) then generate it again.

Thanks for publishing this - it saved a great deal of time and energy for many people!

one tip: when I restarted apache it failed
I fixed it by opening the /etc/apache2/ports.conf
and commenting out with # the 3 extra lines I found in mine

#
# Listen 443
#

I guess I didnt need to add the line “Listen 443″ to my set up “ubuntu server 7.10″

Great Tut
Pugna

- Dav module is already included on Apache2
- The htpasswd2 does not exist… Instead, use the htpasswd… Also, the command described on the article just create a single user… In order to add more than one user, just append to the file as follows:

sudo htpasswd >> -c -m /etc/apache2/dav_svn.passwd $USERNAME

- Warning message
“apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName”
-> just add the following to global section of the apache2.conf
ServerName $HOSTNAME
Where $HOSTNAME is the convenient name you choose… I’m working on a localhost machine behind a firewall from a router, so I just used “localhost”

- Warning messages
[warn] NameVirtualHost *:443 has no VirtualHosts
[warn] NameVirtualHost *:0 has no VirtualHosts

-> The article states to change, the …*443 line, but on mine there was nothing… So I had added the section instead of changing

NameVirtualHost *

To

NameVirtualHost *:443

Everything works great!!!! Thanks a lot

sudo apache2-ssl-certificate -days 10000

to get a cert that doesn’t run out after 1 month… now my server can run till I retire without whining about the cert being expired…

However, if you want security it could perhaps be a good idea to change cert now and then… I don’t know… and I’m not security-paranoid so… 2035 as last valid year works fine for me…