April 26, 2022

How do I find my Alexa’s IP

When securing your network it’s nice to have firewall rules that control traffic to only what you expect or allow and for this, you would need the ip of that device. With the amazon alexa there isn’t an easy way to do this so you have to start by getting the mac address of the device you’re trying to find the ip for.  You can do this if your alexa is already setup by going to https://alexa.amazon.com/.  From here click Settings on the left hand side, then under devices select the alexa you wish to find the ip address for.  Under the About section at the bottom of the page you can see the MAC address.  Copy this and the next step is dependent on your router.  Most allow you to see all the machines on your network.  find that page and simply search the MAC address.  You can also use various network scanning tools that will probe your network for machines.  Most all report the mac address and if they don’t you can 

March 31, 2021

NextCloud Ubuntu Upgrade 18.04 to 20.04

cp /etc/php/7.2/fpm/pool.d/nextcloud.conf /etc/php/7.4/fpm/pool.d/

vi /etc/php/7.4/fpm/pool.d/nextcloud.conf

change the line 

listen = /run/php/php7.2-fpm.nextcloud.sock


listen = /run/php/php7.4-fpm.nextcloud.sock

Next we need to install some items that for whatever reason don’t get upgraded if you are using something other than pgsql change that here too.

apt install php7.4-fpm php-pgsql php-curl php7.4-xml php7.4-gd php-json php-mbstring php-zip php-bz2 php-intl php-ldap php-imap php-bcmath php-gmp php-redis php-igbinary php-memcache

systemctl enable php7.4-fpm

service php7.4-fpm start

grep php7.2-fpm `find ./`

change all these instances to php7.4-fpm

service apache2 restart

Doing these steps should solve the following errors:

No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /run/php/php7.2-fpm.nextcloud.sock

Memcache \\OC\\Memcache\\Redis not available for local cache

Got error ‘PHP message: PHP Fatal error: Uncaught Doctrine\\DBAL\\DBALException: Failed to connect to the database: An exception occurred in driver: could not find driver

failed to make connection to backend: httpd-UDS

January 17, 2014

Ubuntu Gutsy Gibbon Hardy Heron update failed OEL upgrade

So today while trying to VM an old server at work I ran into a problem. It was running Ubuntu 7.10 (Gutsy Gibbon) and would not virtualize properly. I tied to upgrade it using the EOL Path at ubuntu.com to 8.04 (Hardy Heron) but it just wouldn’t work I ended up with the following.

Checking for a new ubuntu release
Failed Upgrade tool signature
Failed Upgrade tool
Done downloading
extracting '/tmp/tmpGEx2kl/hardy.tar.gz'
Failed to extract
Extracting the upgrade failed. There may be a problem with the network or with the server.

This clearly isn’t good but after paring my /etc/apt/sources.list down to the following I was still getting the same error.

deb http://old-releases.ubuntu.com/ubuntu dapper main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu dapper-updates main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu dapper-security main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu dapper-proposed main restricted universe multiverse
deb http://old-releases.ubuntu.com/ubuntu dapper-backports main restricted universe multiverse

With the modification from archive.ubuntu.com to old-releases.ubuntu.com I figure it was really just modifying the server it was retrieving the files from and even though the remote server could be using the host header I though I would try modifying my /etc/hosts file to point to the same ip for archive.ubuntu.com as was resolved for old-releases.ubuntu.com.

/etc/hosts archive.ubuntu.com

It worked running do-release-upgrade now returns

Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tool
Done downloading
extracting '/tmp/tmpXpWtyk/hardy.tar.gz'
authenticate '/tmp/tmpXpWtyk/hardy.tar.gz' against '/tmp/tmpXpWtyk/hardy.tar.gz.

Reading cache

Checking package manager

Continue running under SSH?

This session appears to be running under ssh. It is not recommended
to perform a upgrade over ssh currently because in case of failure it
is harder to recover.

If you continue, a additional ssh daemon will be started at port
Do you want to continue?

So apparently really old versions of ubuntu have archive.ubuntu.com hard coded in the updater and this trick should get around it. Thank god they don’t use virtual hosts for their archives.