Multiple log entries similar to the following are caused by the homeassistant service receiving mdns across multiple interfaces. Those of us working across subnets and such will be susceptible to this. You may still want broadcasting of mdns across both broadcast domains so the best way to handle this is to block homeassistant from broadcasting across both as it already has an interface in each broadcast domain.
2025-03-29 00:24:49.309 homeassistant systemd-resolved[580]: Detected conflict on homeassistant601808.local IN A 10.x.x.x
Each device that handles the broadcasting of this information will be slightly different I use pfsense to manage this so in my case I simply add each interfaces ip address to the block list and it will prevent it from forwarding from those ips.
To restore the admin password on the controller, follow these steps:
Log in from the console.
Use “password” as the user name and use “forgetme!” as the password.
Enable the mode password as “enable”.
In configuration mode, enter the ‘mgmt-user admin root’ command to reset the admin password.
Re-login using the new admin password.
In configuration mode, enter the ‘enable secret’ command to reset the enable mode password.
For example:
User: password Password: forgetme! (aruba) >enable Password: enable (aruba) #configure terminal Enter Configuration commands, one per line. End with CNTL/Z (aruba) (config) #mgmt-user admin root Password: <new admin password> Re-Type password: <new admin password> (aruba) (config) #exit (aruba) #exit (aruba) >exit
Below are the steps to reset the enable mode password from the controller CLI.
User: admin Password: <new admin password> (aruba) >enable Password: enable (aruba) #configure terminal Enter Configuration commands, one per line. End with CNTL/Z (aruba) (config) #enable secret Password: <new enable password> Re-Type password: <new enable password> (aruba) (config) #write memory
sometimes you have the admin password of the controller but not have the enable mode password so what to do…….?
Access the Controller via GUI And change the enable mode password in Controller Wizard.
Navigate to Configuration > Controller Wizard > Under Wizards > Configure Controller >Basic Info> Enter any Name of your choice, Password for User Admin, retype the same, Password for Enable mode Access here is the place where we can reset the enable mode password and retype the same click on Next
From the following site just in case it gets nuked, I scoured tons of pages before this one saved me and my purchase.
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
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
The way this works currently is you need to be able to access a remote url inside your home.  Usually this will require the use of a dynamic dos host provider that can provide you with a hostname that points to your dynamic home address that is updated automatically by your router.  This is not exactly ideal security wise but obscure enough that you’re not likely to have some hacker turning your lights on and off just to mess with you and about the worst case scenario is they turn all your lights on while you are way turning up your electric bill.
Mod_mono is much easier to config at the moment than it has been int he past. Â Assuming you can use apt-get and installed the packages the following is all you need.
Upgraded to Ubuntu 14.04 LTS and discovered apache was not starting up.
Â
The culprit was the following message.
AH00534: apache2: Configuration error: No MPM loaded.
After some digging around it appears the problem has to do with the module being enabled in apache so running the following as root or with sudo clears things up.