Firefox unable to bypass Webmin Connection failure

Since Firefox 33 a “Secure Connection Failed” error can no longer be bypassed using the “I Understand the Risks” button. That buttion is gone! It turns out that Firefox now requires self signed certificates to be 1024 bits or longer where older versions only required 512 bits. Therefore you need to make a new certificate that is long enough.

You can fix this right from Webmin if you use another browser (such as Chrome or Chromium) that lets you bypass this type of error . Otherwise you can log in to your server and temporarily disable SSL in webmin by setting ssl=0 in /etc/webmin/miniserv.conf and restart webmin with “/etc/init.d/webmin restart”.

Then, either way, you can login to the Webmin web UI and select: Webmin -> Webmin Configuration -> SSL Encryption -> Self Signed Certificate. Fill in the form (or leave the defaults) and then click the Create Now button. This will update your self-signed certificate for Webmin and you will now be able to access the page from Firefox 33 (With the usual browser warning about an untrusted connection).

If you temporarily disabled ssl you will need to re-enable it with ssl=1 in /etc/webmin/miniserv.conf and restart webmin with “/etc/init.d/webmin restart”.

Can’t access Webmin using SSL from recent versions of Firefox

Firefox and newer no longer SSL support keys less than 1024 bits. This means you need to create a new set of keys for Webmin.

The easiest way to fix this is from Webmin using a different browser (like current versions of Chrome/Chromium) that let you bypass this type of error. Just login to the Webmin web UI and select:

Webmin -> Webmin Configuration -> SSL Encryption -> Self Signed Certificate.

Fill in the form and then click the

Create Now

button. This will update your self-signed certificate for Webmin and you will now be able to access the page from Firefox (With the usual browser warning about an untrusted connection)

Adjusting to 14.04 (Nautilus dumbed down)

So I liked being able to use the “Connect to Server” feature in 12.04. It allowed me to modify files on my server easily. The Nautilus in 14.04 no longer has that ability. I presume this was done to increase security. Too bad. I can get the capability back by opening a terminal and:

sudo apt-get install sshfs

rebooting and then using the dumbded down Nautilus Connect to server using the address




Which works. I can see /home/user on the server but I can’t see go up to /home or /. That means I can’t see or modify files except in the user home directory.

It turns out that Nemo has a connect to server option similar to the one Nautilus used to have and it also has a button that allows to move upwards in the directory structure not just forwards and back. So, I’m going with Nemo instead of Nautilus.  Install Nemo fro a terminal using:

sudo apt-get install nemo

Note: if I were to create a password for root on my server I could even edit server files requiring root access  from my desktop. I’d rather not do that though due to possible security issues.

Get rid of Overlay Scrollbars in Trusty 14.04

Open a terminal and enter:
<pre>gsettings set com.canonical.desktop.interface scrollbar-mode normal</pre>

Stuck in Ubuntu login loop

Press Ctrl+Alt+F3 and login into the shell.

Now run

sudo ls -lah | grep .Xauthority

if the result looks like:

-rw——- 1 root root 53 Nov 29 10:19 .Xauthority


sudo chown yourusername:yourusername .Xauthority

Outdated release key on ownCloud client

To download an updated release key, open a terminal and:

sudo wget
sudo apt-key add - < /etc/apt/sources.list.d/Release.key

note: sudo wget needs to be on the same line as the address. It’s too long to show that way here.

Grub2 Boot Timeout Fail

Recently one of my systems started waiting for an enter key on a reboot. I usually run this system as a headless server so this meant it never would reboot properly. I found this workaround.

sudo grub-editenv unset recordfail

Running Raring Kernel on Precise

So, a couple of days ago I read that people were finding 13.04 to be quite solid. I want to remain on 12.04 at least until 14.04 is out and stable. Nevertheless, I decided to upgrade to the Raring kernel. In order to accomplish that you need to make sure the “backports” repository is enabled in apt sources. You can do that with gedit by opening a terminal and:

gksudo gedit /etc/apt/sources.list

Then change

#deb precise-backports restricted main multiverse universe


deb precise-backports restricted main multiverse universe

save and exit gedit. Next update your sources with

sudo apt-get update.

I got everything I wanted xorg and the kernel installed by installing a single package. That package pulled in everything else I wanted. Unfortunately I’m not entirely certain what package it was. I think it was:


which is a metapackage. Some of the other metapackages are missing dependencies and won’t install. In any event there’s the entire list of packages I’ve installed.


AT&T Uverse does not block port 443 but…their wireless STB uses that port

I fought for days trying to get my Owncloud server to allow remote https access. At first I thought it was either my Apache 2 configuration or my DMZ Shorewall router (on a Debian Squeeze Pogoplug). I turned out that my wireless set top box was using port 443. That meant I needed to use a different port for my remote https access to Owncloud. I decided to route port 4430 on my router to port 443 on my Owncloud server (running Ubuntu 12.04). Worked great…so far.

Converted from AWN dock to Cairo Dock

AWN dock has apparently not been updated for a while. Moreover it isn’t included in 12.10 and, presumably, later versions of Ubuntu. The nice thing about Cairo Dock is that it comes with it’s own Gnome based desktop. Also I like the ability to add sub-docks to the main dock.


Get every new post delivered to your Inbox.