Dontyoudarenottobeaware

After trying the "Redirect permanent / https://....." for serveral hours and reading almost all of the internet I tried my other browser midori and my configuration just works fine. So, my conclusion: firefox browser sucks!!!!! Keeping this in mind (and I emptied my cache etc) I will not rely on firefox anymore when working with my servers apache configuration. Well, if you want to use more than one virtual host with ONE wildcard ssl certificate then you have to redirect via vhost files: <VirtualHost *:80> ServerName sub.domain.com Redirect permanent / https://...... ..... </VirtualHost> <VirtualHost *:443>  SSLEngine On .... ServerName sub.domain.com .... </VirtualHost>

You may have done this: ssh-keygen and ssh-copy-id and now you want to enable SSL. With Eric Ambergs "Linux-Server" book and Converting keys between openssl and openssh , I did this so far: local: "scp MYKEY root@remote.server:~" after this its just remote: "a2enmod ssl" "mkdir /etc/apache2/ssl" "openssl req -x509 -days 365 -new -key MYKEY -out /etc/apache2/ssl/nedab.de.pem" and make sure you use a wildcard domain as common name, e.g. *.common.com. That way your certificate is valid for all subdomains.  "a2enmod redirect" virtualhost in /etc/apache/site-available with help from Redirect Request to SSL : <VirtualHost *:80> ServerName .......... Redirect permanent / https://........../ </VirtualHost> <VirtualHost _default_:443> SSLEngine on SSLCipherSuite HIGH:MEDIUM SSLCertificateFile /etc/apache2/ssl/........pem SSLCertificateKeyFile /etc/apache...

After migrating my server from one account to another, basically setting it up again, I ran into some problems with my etherpad lite installation. Since my first post on this I wanted to add some more users for more control whose group is accessing what pad. But there was always something wrong! My conclusions: use "service etherpad-lite restart" instead of the /admin restart button make sure that apache is running or restart it often enough change the bloody JSON file trough the /admin interface since its telling you about corrupt syntax Last point on the list was my major problem for I forgot to put down some more blanks in order to have the JSON hierarchy. After that was sorted my basic authentication ALMOST worked: dont use "requiresession = true" for it messes up some stuff somehow Now my installation works like a charm with my postgresql database.

I followed these steps: How to Install Etherpad Lite on Debian Wheezy Basicly: install packages for compiling etc get nodejs set up database get etherpad set it up on localhost create init script for to run as service create user and change folder permissions dry run it with that user create virtual host that forwards the local service And changed/added this at the end: a2ensite domain.tld a2enmod proxy a2enmod proxy_http /etc/init.d/apache2 restart

First of all, I like these little problems because they make me so much better with dealing with linux. And since its a hobby of mine, I cant really complain. Anyway, it took me a while to figure out that postgresql could not connect via the console because of some settings regarding authorization. Go to your pg_hba.conf and change from peer to md5 and you can login your database with your user and password. ----------------------------------------------------------- The second thing also troubled me a while and I was checking everything, because the log files did tell what was going wrong. passenger was running fine apache2 was set up ok, same with my virtual hosts and rvm was running wonderfully But I could not connect to my virtual hosts. And after a decent research on the internet and after quite a lot of message boards and posts I found the answer: check for the apache2/sites-enabled/default And there it was, these default files overwrote my virtualhosts an...