Hello there!
I installed VMware ESXi/vSphere (.ova) on my Ds723+ following the tutorial on first topic. Everything works great, expect that I’m not getting the supervisor options/menus.
What I’m missing here?
Thanks.
Sorry, I was a new user, so I had the rule that I couldn’t post more than 3 in a topic…
BTW…
First of all thanks for your help, then:
- incognito: CHECKED
- different browser (ffx, chrome, edge): CHECKED
- reboot router and switch: CHECKED
- disabling nas firewall: CHECKED
- connection from a different device (smartphone): CHECKED
- 3rd party AV/Firewall/MW on Windows: NO
Yes, brand new install, never used HA before (a couple of days with the docker version, then I discovered its addon restriction and decided to try the VM version). I obviously cleaned the old docker installation.
When I try telnet 192.168.1.109 8123 this is the result:
with the blinking “_”
don’t thank me, I do not seem to be helping.
Any idea if the old docker install was the same IP?
I think I would just delete the VM and start over and once it is running let it run for a “good” while. Perhaps a couple of hours and see if you get an interface without rebooting it
Sorry, I had the flu. This morning I tried to delete and reinstall the VM and VMM, then waited for about 3 hours. Nothing has changed.
The docker IP was the same as the NAS IP, different from ..*.109.
Unfortunately, the actual updates cannot update on synology VM. I have still the version 2023.11.3 installed. With this version it works without problems. When I update to the newest versions like 2023.12 or also the new one 2024.1.1 I get a permission error from the supervisor and an IP 172.30.32.1 and so many things are not working.
Does anybody knows, what the IPs 172.30.32.1 and 172.30.232.1 are?
This is the error in the log files:
Log entry:
Logger: homeassistant.components.http.ban
Source: components/http/ban.py:129
Integration: HTTP (documentation, issues)
First occurred: 18:26:40 (1 occurrences)
Last logged: 18:26:40
Login attempt or request with invalid authentication from supervisor (172.30.32.2). Requested URL: ‘/api/core/state’. (HomeAssistantSupervisor/2023.12.0 aiohttp/3.9.1 Python/3.11)
Runs fine here. You do have these IP’s in configuration under http - trusted proxies? These are IP’s from virtual machine (or something…) and must be trusted.
And insert “use_x_forwarded_for” under http, too.
http:
ip_ban_enabled: true # optional
login_attempts_threshold: 10 # optional
use_x_forwarded_for: true
trusted_proxies:
– 192.168.0.0/24 # or whatever is your local ip segment...
– 172.30.32.0/24
– 172.30.232.0/24
you can see these IP’s in your virtual machine data:
I get that every now and then and just click dismiss
Is it new, that I have to add the IPs to the trusted_proxies? As I said before, with 2023.11.3 It worked without that without problems.
When I have a look at your print-screen, the additional IPs are the same:
In my configuration.yaml it looks like this. I will add the 2 Ips and will try again.
Does it need this entries?
ip_ban_enabled: true # optional
login_attempts_threshold: 10 # optional
No Clue. I just downloaded the .ova file and created/imported a new machine and it seems to be working fine.
Download the ova file again and place it on the NAS to import it
Ip ban and threshold is optional, not needed but a good idea. It limits number of (false) login attempts into your HA, after set threshold it blocks login posibility from that IP by entering that IP into ‘ip_bans.yaml’ - basically it prevents possible attacks.
Be warned though that you could theoretically lock yourself out if you mess with wrong login password too much, that’s why a good threshold must be set (not, say only 2 or 3 attempts…)… then you must either ssh into HA or login from another IP, delete ip _bans.yaml contents and restart HA.
@Protoncek : I added the IPs to the trusted_proxies. I still have this error and Home Assistant is not able to start.
After completely shutdown of the virtual machine, It needed more than 1 hour and I saw several times this error message. Could it be that the virtual machine is not able to start, while the configuration.yaml is not ready or not accessible?
Well, if VM doesn’t start at all then you have another problem… i’d reinstall HA and import backup in that case. VM not starting can be anything…
Normal HA Restart works without problem after the trusted_proxies entry. It only takes such a long time and shows me this error, when I completely shutddown the virtual machine in virutal machine manager. But now with trusted_proxies entry the VM is able to start after more than an hour. Before this trusted_proxies entry the VM couldn’t start.
When I make a new VM, I can install the tar backup after that and everything is there like before?
With the core version 2023.11.3 everything works without problems. I only have this starting problems with the newer versions.
I have a question about synology restart and home assistant. How often do you restart your Synology (only when updated available)? And whats about the virtual Home assistant machine?Do you completely shutdown the virtual machine before and whats the autostart settings fir the virtual machine (Yes, last state)?
Correct, only when Syno updates are installled. I have set VM to automatically suspend when syno wants to restart. (VM settings, last setting). You can set it to shutdown, too.
Ive installed it on a DS920+ with 8gb of ram, after some lights setups 5 adons a few hacs integrations and like 15 devices. I have a ram consumption of 6-6.5gb and that from the second it turns on. When the vm is offline i have like 200mb ram usage, the vm chrashed one time while installing a template.
How many RAM did you assign for HA?
And… where do you read 6-6,5GB occupied? IN VM manager? There system always shows ram ASSIGNED to VM, not how much VM actually uses it, so that’s not very usable info. For actual info how much HA consumer it go to HA’s settings - Hardware. However, if assigned ram is too small i guess it can happen that VM crashes…or, for that matter, if assigned ram is too big and too little is left for syno’s system to operate.
HA should have 4GB asigned (or more if you have it). It does run with 2GB, though. I have normally under 2GB occupied RAM, looking inside HA.
BTW… you can extend RAM beyond “max allowed” (and i think it’s a good idea). I have 20GB of ram installed (original 4 and additional 16GB module).
1 Like
So i checked in Ha Hardware and im unsing 0.6gb of 4 assigned.
So Thanks for the info with the VM Manager graph.
I strongly doubt that HA crashed because ram. It must be something else (bad addon… ?)
I have latest Home Assistant image on Synology NAS virtual machine manager, basic setup, and now I’m getting 400: Bad request, what could it be?