Lms container uses host networking, so you won’t see much there.
Could you please run
netstat -tanp |grep LISTEN
On HA
➜ / netstat -tanp |grep LISTEN
tcp 0 0 0.0.0.0:1337 0.0.0.0:* LISTEN 489/node
tcp 0 0 127.0.0.11:45801 0.0.0.0:* LISTEN -
On the container via portainer/sh:
root@fc57b866-lms:/$ ➜ / netstat -tanp |grep LISTEN
tcp 0 0 0.0.0.0:1337 0.0.0.0:* LISTEN 489/node
tcp 0 0 127.0.0.11:45801 0.0.0.0:* LISTEN - sh: 3: tcp: not found
root@fc57b866-lms:/$ sh: 4: tcp: not found
Well on that basis even ha is not running (port 8123 is missing)
If portainer is running that is contrary to what you said earlier, and is a reason why lms is not working. Please, stop wasting our time.
Btw, lms doesn’t fail to start or generate an error even port 9000 is used by portainer in my case, probably because of host networking???
I was accessing it via http://ip:9001 because i set 9001 as new port number for lms but ingress link doesn’t work
1 Like
This comment doesn’t add anything
I do appreciate the help.
I tried:
- Without Portainer.
- Without Portainer and LMS on 6 different ports.
- Portainer at 9001, and LMS at 9099
- I tried Portainer at 9099 and LMS 9001.
Seems to me, that it isnt portainers fault.
@anon63427907, I tried that before and didn’t pay attention. So I didn’t get a 404 but a SSL error, which result in chrome more or less same page. So that works! Thanks :).
So it is ingress that is still not working.
1 Like
For ingress, reach out to LMS add-on owner to make the ingress link dynamic rather than fixed on 9000
Get portainer off your system. Run lms with no changes to the config.
Another thought - make sure slimproto integration is not running
How is this relevant?
-
It is unsupported and on fact not allowed from HAOS and supervised installs.
-
It uses port 9000 which will interfere with LMS.
Both are unrelated to the issue here, there can be another addon interfering with 9000 port and you don’t have any knowledge about how the user is using the portainer.
Lastly, there is a portainer addon too ( Home Assistant Community Add-on: Portainer )
I prefer to have portainer in my setup independent of supervisor because it gives better control to my supervised installation, if home assistant is having issues and not working.
1 Like
Well, having an add-on does not automatically mean it is OK.
It is OK only when you know what you are doing, and know how to clean up the messes if something goes wrong.
The add-on you listed is not an official one, after all… plus you most certainly would find an error message saying you have an “unhealthy” image.
Plus AFAIK the Supervisor would block updates also, if/when the system becomes unhealthy.
So, can you use it? Sure.
But if anyone runs into any issues and doesn’t know what is going on, Nick’s recommendation to get rid of Portainer is a perfectly logical one.
Your recommendation for @3zkc9fyf to reach out to the owner of LMS add-on is also a logical one.
Is was fine recommendation to tried it without portainer, so I did. Didn’t change a bit. I dont see how it could mess up, since I wouldn’t change any config/containers. But its a bit useless to continue debate on this I would think.
@pssc Phill already in on this thread. So maybe you can shine a light.
I understand what you are saying but it is irrelevant to the problem.
With the current status; there is an X add-on and ports are contradicting with each other, which could happen with any add-on, removing the add-on is kike burying your problems underground.
Why not give the reasoning and way to fix it? We don’t have any data points how important portainer for the user.
Please run the netstat command in the advanced ssh terminal. The results should show ha on port 8123, etc.
I got mixed up in Advanced SSH & Web Terminal and Terminal & SSH.
This does make more sense, lms runs now on 9001 Otherwise it was not working for me.
Portainer is uninstalled.
So it is working now?
Well I can browse it via my ip:9001 combi, but not via ingress. That shows still a 502.
I can not do ip:9000. Even without portainer.
Why are you using 9001? As I said, get it working with no changes to config.